# Regproc some group(1,2,3,6) pod failure

**URL:** <https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792>\
**Category:** Support\
**Tags:** regclient\
**Created:** [September 20, 2023, 12:07pm UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792 "2023-09-20T12:07:46Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![bal\_sam](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bal\_sam](https://community.mosip.io/u/bal_sam)\
**Post date:** [September 20, 2023, 12:07pm UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/1 "2023-09-20T12:07:46Z")

</div>

Dear Team,  
We configured the registration process group (1, 2, 3, 6). Please let me know what changes need to be made on my side. Please see the below error screenshot.

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/4f0bbe490eb0800250c1b98204a4c12833bb5201.png)

---

<div class="post-metadata">

**Author:** ![sanchi-singh24](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/sanchi-singh24/32/538_2.png) [@sanchi-singh24](https://community.mosip.io/u/sanchi-singh24)\
**Post date:** [September 20, 2023, 1:42pm UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/2 "2023-09-20T13:42:07Z")

</div>

Hi @bal_sam

As I can see you have configured the registration process group and you need guidance on changes to be made based on the error logs provided in the screenshot @Monobikash will look into this and guide you through the process.

Best Regards,  
Team MOSIP

---

<div class="post-metadata">

**Author:** ![Monobikash](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/monobikash/32/372_2.png) [@Monobikash](https://community.mosip.io/u/Monobikash)\
**Post date:** [September 21, 2023, 4:33am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/3 "2023-09-21T04:33:49Z")

</div>

HI @bal_sam ,

Thanks for sharing stacktrace. Its saying below configuration is not resolved -  
mosip.regproc.abis.handler.biometric-modalities-segments-mapping.INFANT

Did you change any of our default config? By default our configuration files will have this config. You can check in “registration-processor-default.properties” and verify if the configuration is present.

The default value in MOSIP is -  
mosip.regproc.abis.handler.biometric-modalities-segments-mapping.INFANT={‘Face’:{‘Face’}}

Please reach out if this doesn’t solve your issue.  
CC @sanchi-singh24

---

<div class="post-metadata">

**Author:** ![bal\_sam](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bal\_sam](https://community.mosip.io/u/bal_sam)\
**Post date:** [September 21, 2023, 7:45am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/4 "2023-09-21T07:45:52Z")

</div>

Hi @Monobikash,

We don’t change any defaults. propertics in the value. helm installation, we follow on-prem setup in the Mosip public repo. so directly run./install.sh

repo version: v1.2.0.1-B3  
CHART\_VERSION=12.0.1-B3

---

<div class="post-metadata">

**Author:** ![bal\_sam](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bal\_sam](https://community.mosip.io/u/bal_sam)\
**Post date:** [September 21, 2023, 8:03am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/5 "2023-09-21T08:03:03Z")

</div>

@Monobikash  
in my config-server repo values.yml file pointing to mosip config  
gitRepo:  
uri: [GitHub - mosip/mosip-config: This repository contains MOSIP configuration templates](https://github.com/mosip/mosip-config)  
version: 1.2.0.1-v3

version correct, do we need to change version: v1.2.0.1-B3?

---

<div class="post-metadata">

**Author:** ![Monobikash](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/monobikash/32/372_2.png) [@Monobikash](https://community.mosip.io/u/Monobikash)\
**Post date:** [September 21, 2023, 8:53am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/6 "2023-09-21T08:53:39Z")

</div>

Yes @bal_sam , you have to change to correct version which is v1.2.0.1-B3.  
Please don’t point to untagged versions which are not tested and released.  
If you point to tagged version v1.2.0.1-B3, your problem will be fixed.

CC @sanchi-singh24

---

<div class="post-metadata">

**Author:** ![bal\_sam](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bal\_sam](https://community.mosip.io/u/bal_sam)\
**Post date:** [September 21, 2023, 9:57am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/7 "2023-09-21T09:57:49Z")

</div>

Hi @Monobikash  
after change tagged version group 2 and 3 error fixed. still facing error group 1 and 6. kindly help on this

1. please find the group 1 error  
 ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/a2ed9cdf5c1bf9ee7fc3130a9d78b49e253cf1cf.png)
2. please find the group 6 error  
 ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/7744747cddea06a3f75ffc34a97ddb03e03be5ee.png)

---

<div class="post-metadata">

**Author:** ![Monobikash](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/monobikash/32/372_2.png) [@Monobikash](https://community.mosip.io/u/Monobikash)\
**Post date:** [September 21, 2023, 11:14am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/8 "2023-09-21T11:14:26Z")

</div>

I see health check is failing here and dont see any other error. To understand more, please hit the health check urls and provide response.  
/registrationprocessor/v1/packetreceiver/actuator/health

---

<div class="post-metadata">

**Author:** ![bal\_sam](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bal\_sam](https://community.mosip.io/u/bal_sam)\
**Post date:** [September 21, 2023, 11:51am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/9 "2023-09-21T11:51:08Z")

</div>

![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/8b1ffb04bbc413f02050d5b8da276fefd735ee11.png)

---

<div class="post-metadata">

**Author:** ![bal\_sam](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bal\_sam](https://community.mosip.io/u/bal_sam)\
**Post date:** [September 21, 2023, 2:16pm UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/10 "2023-09-21T14:16:43Z")

</div>

![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/d48634e69b19b3c3a69fec855a702547d3312114.png)

---

<div class="post-metadata">

**Author:** ![bal\_sam](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@bal\_sam](https://community.mosip.io/u/bal_sam)\
**Post date:** [September 22, 2023, 5:04am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/11 "2023-09-22T05:04:21Z")

</div>

Hi @Monobikash ,

issue on Clamav. Once fixed, clamav automatically passed groups 1 and 6 service health checks.

---

<div class="post-metadata">

**Author:** ![sanchi-singh24](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/sanchi-singh24/32/538_2.png) [@sanchi-singh24](https://community.mosip.io/u/sanchi-singh24)\
**Post date:** [September 22, 2023, 7:47am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/12 "2023-09-22T07:47:53Z")

</div>

It’s good to know @bal_sam that your issue got resolved if there is any thing else please do reach out to us.

Best Regards,  
Team MOSIP

---

<div class="post-metadata">

**Author:** ![sanchi-singh24](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/sanchi-singh24/32/538_2.png) [@sanchi-singh24](https://community.mosip.io/u/sanchi-singh24)\
**Post date:** [September 22, 2023, 7:47am UTC](https://community.mosip.io/t/regproc-some-group-1-2-3-6-pod-failure/792/13 "2023-09-22T07:47:59Z")

</div>


