The websub pod is throwing the error below,

Support
1

The websub pod is throwing the error below,

unused configuration value ‘kafkaHub.config.HUB_SECRET_ENCRYPTION_KEY’

unused configuration value ‘kafkaHub.config.HUB_SECRET_ENCRYPTION_KEY_FORMAT’

how can this be resolved?

git branch
v1.2.0.1-B2

2

Hi @Abhishek_Thakur

Thanks for sharing your concern, let our team look into this but can you provide more context on this and let us know a little bit more details on the config setup?

Best regards,
Team MOSIP

3

@syed.salman , please can you help on this query as well?

4

@Abhishek_Thakur Can you confirm the mosip-config version that you are using ?

If you are using the code or docker image of websub 1.2.0.1-B2, it is expected to use the same version of the mosip-config to be compatible.

5

Thank you for your quick response, we are trying to deploy this setup on Microsoft Azure AKS.

Dependencies setup is deployed

But, when we try to deploy MOSIP Modules this Websub pod throws the error we need your little assistance to resolve this issue.

6

Can you share the result of below commands:

  1. kubectl get pods -n config-server – >(to check if config server is deployed).
  2. kubectl get secrets -n conf-secrets
  3. also can you confirm websub chart version used.
  4. config server branch version.
7

I appreciate your support. As per your given solution, I made some changes in the config-server and changed that branch “version: v1.2.0.1-B2” and it worked for a websub. but now it through me on Error “keymanager” as below:

“{”@timestamp":“2024-07-25T06:10:28.672Z”,“@version”:“1”,“message”:“Initialized JPA EntityManagerFactory for persistence unit ‘hibernate’”,“logger_name”:“org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean”,“thread_name”:“localhost-startStop-1”,“level”:“INFO”,“level_value”:20000,“appName”:“keys-generator”}
{“@timestamp”:“2024-07-25T06:10:29.160Z”,“@version”:“1”,“message”:“Error starting Tomcat context. Exception: org.springframework.beans.factory.BeanCreationException. Message: Error creating bean with name ‘servletEndpointRegistrar’ defined in class path resource [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]: Factory method ‘servletEndpointRegistrar’ threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘healthEndpoint’ defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthEndpoint]: Factory method ‘healthEndpoint’ threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘HSMHealth’: Unsatisfied dependency expressed through field ‘dbHelper’; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘keymanagerDBHelper’: Unsatisfied dependency expressed through field ‘keyStore’; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘keyStoreImpl’: Injection of autowired dependencies failed; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder ‘softhsm.security.pin’ in value "${softhsm.security.pin}"”,“logger_name”:“org.springframework.boot.web.embedded.tomcat.TomcatStarter”,“thread_name”:“localhost-startStop-1”,“level”:“ERROR”,“level_value”:40000,“appName”:“keys-generator”}
"
########As you ask for some information that is given below########

kubectl get pods -n config-server
NAME READY STATUS RESTARTS AGE
config-server-7bd865688b-jkf4r 2/2 Running 0 5d4h

kubectl get secrets -n conf-secrets
NAME TYPE DATA AGE
conf-secrets-various Opaque 17 5d19h
sh.helm.release.v1.conf-secrets.v1 helm.sh/release.v1 1 5d19h

kubectl get po -n websub
NAME READY STATUS RESTARTS AGE
websub-9d69687c6-m4g79 2/2 Running 1 (76m ago) 78m
websub-consolidator-6698dd75fd-h6fv5 2/2 Running 1 (78m ago) 79m

8

Can you crosscheck if DB is deployed sucessfully.

  1. Check if postgres pod is up and running.
  2. Check if all the postgres-init jobs passed.
  3. Also which version of MOSIP are you deploying?
  4. If postgres is up and all the jobs finished sucessfully can you confirm if you are able to establist connectivity to the Database using:
  • hostname: private IP of the nginx server.
  • get the postgres user password from postgres namespace secrets.
9

Hi @Abhishek_Thakur ,

Thank you for reaching out to us.

Can you confirm whether you are facing this issue yet. If the issue is resolved appreciate your feedback on the same.

Regards,
Varaniya S
On behalf of MOSIP

10

Thank you for your response, I apologize for the late reply, I am still facing that same issue. we are here to deploy the Mosip setup on Azure. If you have any guide related to Microsoft Azure please share it with us.

As an alternative please guide us as what would be the adapter name for mino object storage in application_default. property or we can use the AZURE blob service instead of S3.

Thanks and regards
Abhishek