# Can't run idrepo identity - CrashLoopBackOff (MOSIP version 1.2.0.1-B2)

**URL:** <https://community.mosip.io/t/cant-run-idrepo-identity-crashloopbackoff-mosip-version-1-2-0-1-b2/355>\
**Category:** General\
**Created:** [March 12, 2023, 3:36pm UTC](https://community.mosip.io/t/cant-run-idrepo-identity-crashloopbackoff-mosip-version-1-2-0-1-b2/355 "2023-03-12T15:36:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\
**Post date:** [March 12, 2023, 3:36pm UTC](https://community.mosip.io/t/cant-run-idrepo-identity-crashloopbackoff-mosip-version-1-2-0-1-b2/355/1 "2023-03-12T15:36:05Z")

</div>

I tried for several times making idrepo identity application to run but I failed.

I used different Helm chart versions, even changed Docker images, adjusted liveness/startup probes, increase/decrease resources and other usual fix to this issue, Unfortunately no success in making it run without encountering errors.

I look at the logs and I see errors on them, but I do not know how to fix them.

Here is an extract =

“@timestamp”:“2023-03-12T14:42:00.010Z”,“@version”:“1”,“message”:“\n\nError starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled.”,“logger\_name”:“org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener”,“thread\_name”:“main”,“level”:“INFO”,“level\_value”:20000,“appName”:“id-repository”}  
{“@timestamp”:“2023-03-12T14:42:00.014Z”,“@version”:“1”,“message”:“Application run failed”,“logger\_name”:“org.springframework.boot.SpringApplication”,“thread\_name”:“main”,“level”:“ERROR”,“level\_value”:40000,“stack\_trace”:"org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘idRepoProxyServiceImpl’: Unsatisfied dependency expressed through field ‘objectStoreHelper’; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘objectStoreHelper’: Injection of autowired dependencies failed; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder ‘s3.pretext.value’ in value "${s3.pretext.value}idrepo"\n\tat org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject  
…

---

<div class="post-metadata">

**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\
**Post date:** [March 13, 2023, 3:25am UTC](https://community.mosip.io/t/cant-run-idrepo-identity-crashloopbackoff-mosip-version-1-2-0-1-b2/355/2 "2023-03-13T03:25:11Z")

</div>

I tried fixing this again by overriding the helm chart using values.yaml and pointed to the latest docker image - mosipid/id-repository-identity-service:latest

I did this after reading in the forum about an error with the s3.pretext.value in a docker image fixed with a 1.2.0.1-B2 image.

Now there is a different error -  
Exception in thread “main” java.util.zip.ZipException: zip file is empty

---

<div class="post-metadata">

**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\
**Post date:** [March 13, 2023, 4:28pm UTC](https://community.mosip.io/t/cant-run-idrepo-identity-crashloopbackoff-mosip-version-1-2-0-1-b2/355/3 "2023-03-13T16:28:55Z")

</div>

I had an idea of fixing this by doing the steps I did in fixing the errors in packetmanager.

In the mosip-helm chart repository I downoaded the raw values.yaml of the helm chart to the mosip idrepo module directory

Then I edited the file copy\_cm.sh to add this line to the file

$COPY\_UTIL configmap softhsm-kernel-share softhsm $DST\_NS

In the values.yaml configuration I added the line - _ **softhsm-kernel-share** _

extraEnvVarsCM:

```
global
config-server-share
artifactory-share
softhsm-kernel-share

```

I also edited the docker image to use the latest

image:  
registry: [docker.io](http://docker.io)  
repository: mosipid/id-repository-identity-service  
tag: latest

then, increased the resources

javaOpts: “-Xms4000M -Xmx4000M”

So I deleted and reinstalled idrepo module with a helm chart override using values.yaml. This is to make sure that changes in cm\_copy.sh will be loaded.

Before that I edited the install.sh particularly the line installing idrepo-identity.

helm -n $NS install identity mosip/identity -f values.yaml --version $CHART\_VERSION

I had to do this a few times testing different chart versions.

So that I don’t have to uninstall the other working services I used the following commands:

_ **helm -n idrepo delete identity** _

_ **helm -n idrepo install identity mosip/identity -f values.yaml --version 12.0.1-B2** _

_ **kubectl -n idrepo get deploy -o name | xargs -n1 -t kubectl -n idrepo rollout status** _

Don’t ask me why, I can’t explain, but it is working now.

---

<div class="post-metadata">

**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\
**Post date:** [March 18, 2023, 10:18am UTC](https://community.mosip.io/t/cant-run-idrepo-identity-crashloopbackoff-mosip-version-1-2-0-1-b2/355/4 "2023-03-18T10:18:03Z")

</div>

This issue returned after a while, but Once mosip-config repo is updated with the fix as discussed by @vishwa at my packetmanager post

> [@Packetmanager - CrashLoopBackOffF in MOSIP v1.2.0.1-B2](https://community.mosip.io/t/packetmanager-crashloopbackofff-in-mosip-v1-2-0-1-b2/354):
>
> I am having issues in packetmanager with CrashLoopBackOff status. I tried deleting the pod / module and reinstalling but it does not fix it. I also tried using different Helm chart versions 1.2.0.1-beta and 1.2.0.1-B2, but it makes no difference. Looking at it closely both Helm charts uses the same docker image. Is that intentional? image: registry: [docker.io](http://docker.io) repository: mosipid/commons-packet-service tag: 1.2.0.1-B1 Does anyone have encountered this and/or anyone who has a fix? Thanks! …

I simply restarted the config-server module and after a few minutes the errors were gone. This issue was also fixed along with the issues in packetmanager, idrepo-identity, resident and even regproc-group6.

Thank you so much, please consider this issue closed.

Warm regards,  
rcsampang

---

<div class="post-metadata">

**Author:** ![gsasikumar](https://avatars.discourse-cdn.com/v4/letter/g/b782af/32.png) [@gsasikumar](https://community.mosip.io/u/gsasikumar)\
**Post date:** [March 21, 2023, 5:58am UTC](https://community.mosip.io/t/cant-run-idrepo-identity-crashloopbackoff-mosip-version-1-2-0-1-b2/355/5 "2023-03-21T05:58:45Z")

</div>

Closed on March 21, 2023, 5:58am UTC


