mosip / mosip-infra

MOSIP deployment Infrastructure repo

MOSIP Infra

This repository contains various scripts and procedures to deploy MOSIP in sandbox and production environments.

License

This project is licensed under the terms of Mozilla Public License 2.0.

mosip-infra's Issues

Dev Installer: Monitor for services' logs

Write a simple monitor to check if all services have come up fine. If not, flag the error. Depending on error restart the service(s).

Install SSL Certificate

Hello,

Where can I install the SSL certificate?
Every time I install SSL certificate in nginx, the page's language turns to Spanish
https://mosip.fixed.ninja/pre-registration-ui/#/
And also error pessage appears like this
Une erreur technique s'est produite et l'opération ne peut pas être terminée. Aucune donnée fournie ne peut être sauvegardée
Translation
A technical error has occurred and the operation cannot be completed. No data provided can be saved
And then page keeps loading.

please help with sizing guideliness for arriving at CPU cores, Memory (RAM), Storage requirement for a given volume of concurrency for enrolment and verification along with total number of registrations

please help with sizing guideliness for arriving at CPU cores, Memory (RAM), Storage requirement for a given volume of concurrency for enrolment and verification along with total number of registrations

Registration client issue

Hello, i launched the file run.bat, when the jars are downloaded, and the client is prepared to be launched, it suddenly return an error message then crash.
the version i have installed is 1.1.5, bellow you can find the logs generated:

.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Checking for jars Completed
2022-04-07T14:19:37Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Found all the required jars
2022-04-07T14:19:37Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Started tpm availability check
2022-04-07T14:19:37Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Decrypting mosip-client
2022-04-07T14:19:37Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Decryption Started
2022-04-07T14:19:37Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Decrypting mosip-services
2022-04-07T14:19:37Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Decryption Started
2022-04-07T14:19:37Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Decrypting mosip jars completed
2022-04-07T14:19:43Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Preparing command to launch the reg-client
2022-04-07T14:19:43Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Proccess Initiated
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,531 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,533 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,534 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-idgenerator-rid-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,537 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/7890b98a-3730-431b-8851-263c5a4a073f.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-dataaccess-hibernate-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-idvalidator-rid-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/khazana-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-idvalidator-prid-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-idgenerator-rid-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-virusscanner-clamav-1.1.3.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-idvalidator-uin-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-idobjectvalidator-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-qrcodegenerator-zxing-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-templatemanager-velocity-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-keymanager-service-1.1.5-lib.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,538 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-pdfgenerator-itext-1.1.5.jar!/logback.xml]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,582 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@21d85187 - URL [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-idgenerator-rid-1.1.5.jar!/logback.xml] is not of type file
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,817 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,821 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,849 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:05,869 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:06,021 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:06,022 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:06,023 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 14:20:06,024 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@4194e3aa - Registering current configuration as safe fallback point
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG -
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:06,440 [main] INFO [o.s.c.SpringProperties]..64 : Found 'spring.properties' file in local classpath
2022-04-07T14:20:06Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:06,908 [main] INFO [o.s.c.s.AbstractApplicationContext].prepareRefresh.590 : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@6ebc05a6: startup date [Thu Apr 07 14:20:06 UTC 2022]; root of context hierarchy
2022-04-07T14:20:12Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:12,620 [main] INFO [o.s.b.f.s.DefaultListableBeanFactory].registerBeanDefinition.824 : Overriding bean definition for bean 'restTemplateInterceptor' with a different definition: replacing [Generic bean: class [io.mosip.kernel.auth.defaultadapter.config.RestTemplateInterceptor]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [jar:file:/C:/Users/g524542/AppData/Local/Temp/b02dc6c9-7e13-48a2-8fa0-ac9387c94211/kernel-auth-adapter-1.1.5.jar!/io/mosip/kernel/auth/defaultadapter/config/RestTemplateInterceptor.class]] with [Root bean: class [null]; scope=; abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=restTemplatePostProcessor; factoryMethodName=restTemplateInterceptor; initMethodName=null; destroyMethodName=(inferred); defined in class path resource [io/mosip/kernel/auth/defaultadapter/config/RestTemplatePostProcessor.class]]
2022-04-07T14:20:18Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:18,066 [main] INFO [o.s.c.c.s.GenericScope].setSerializationId.294 : BeanFactory id=e8380dea-9b57-31ab-806a-951c3d1d05f5
2022-04-07T14:20:18Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:18,887 [main] INFO [o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker].postProcessAfterInitialization.328 : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$963b3484] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-04-07T14:20:19Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:19,218 [main] INFO [o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker].postProcessAfterInitialization.328 : Bean 'org.springframework.cache.annotation.ProxyCachingConfiguration' of type [org.springframework.cache.annotation.ProxyCachingConfiguration$$EnhancerBySpringCGLIB$$df4d6aa2] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-04-07T14:20:19Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:19,468 [main] INFO [o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker].postProcessAfterInitialization.328 : Bean 'org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration' of type [org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration$$EnhancerBySpringCGLIB$$2ee8fcbe] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-04-07T14:20:19Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:19,527 [main] INFO [o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker].postProcessAfterInitialization.328 : Bean 'objectPostProcessor' of type [org.springframework.security.config.annotation.configuration.AutowireBeanFactoryObjectPostProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-04-07T14:20:19Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:19,538 [main] INFO [o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker].postProcessAfterInitialization.328 : Bean 'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@5535e9' of type [org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-04-07T14:20:19Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:19,567 [main] INFO [o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker].postProcessAfterInitialization.328 : Bean 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration' of type [org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration$$EnhancerBySpringCGLIB$$53bd9f70] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-04-07T14:20:19Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:19,623 [main] INFO [o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker].postProcessAfterInitialization.328 : Bean 'methodSecurityMetadataSource' of type [org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-04-07T14:20:20Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - 2022-04-07 14:20:20,292 [main] WARN [o.s.c.s.AbstractApplicationContext].refresh.558 : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in io.mosip.registration.config.DaoConfig: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean]: Factory method 'entityManagerFactory' threw exception; nested exception is io.mosip.registration.exception.RegBaseCheckedException: REG-INIT-001 --> Application found in invalid state, tampering detected !
2022-04-07T14:20:20Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Terminating the application
2022-04-07T14:20:20Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Started Destroying proccess of reg-client and force deleting the decrypted jars
2022-04-07T14:20:22Z - [io.mosip.registration.cipher.ClientJarDecryption] - INFO - REGISTRATION - CLIENT_JAR_DECRYPTION - - REGISTRATION - REG - Completed Destroying proccess of reg-client and force deleting the decrypted jars

Dev Installer: Given ssh keys don't work

Ssh keys need to be created by the script instead of using pre-created ones.

OTP Entered Is Not Valid

I am running MSOIP Sandbox-v2 v1.1.2 on-premise using self-signed certificates. All the mz and dmz pods are running properly but when I try to enter the default OTP of 111111 in the pre-registration-ui. I am getting the below error.

Gracefully shutdown MOSIP

Hello community,

Actually, after rebooting MOSIP was not running and preenrolment was not
accessible.
Could you please share the procedure for gracefully shutdown MOSIP platform and start it after reboot ?

Regards,

could you please share the installation script/procedure for dev environment ?

Actually the repository https://github.com/mosip/mosip-platform.git doesn't exist anymore so the procedure under "mosip-infra" is no more valid.
Could you please share the installation script/procedure for dev environment ?
Regards,

Error while creating HDFS user directory

Steps

1. downloaded mosip-infra under /opt

2. run # sh install-mosip-kernel.sh
   Everything went fine well until the script reaches this task:
   - name: Creating HDFS user directories shell: . /root/.bashrc && hdfs dfs -mkdir -p /user/"{{ item }}" loop: - regprocessor-qa - prereg - idrepo-qa

   - name: Giving user permission for directories created in previous step shell: . /root/.bashrc && hdfs dfs -chown -R "{{ item }}":"{{ item }}" /user/"{{ item }}" loop: - regprocessor-qa - prereg - idrepo-qa

This is the last task in ansible file located in sandbox/playbooks/install-configure-hdfs.yml

Error
TASK [Creating HDFS user directories]
********************************************************************************************************
failed: [46.4.122.85] (item=regprocessor-qa) => {"ansible_loop_var": "item", "changed": true, "cmd": ". /root/.bashrc && hdfs dfs -mkdir -p /user/ \"regprocessor-qa\"", "delta": "0:00:00.005478", "end": "2020-03-23 15:24:46.171031", "item": "regprocessor-qa", "msg": "non-zero return code", "rc": 2, "start": "2020-03-23 15:24:46.165553", "stderr": "/bin/sh: 13: /root/.bashrc: shopt: not found\n/bin/sh: 21: /root/.bashrc: shopt: not found\n/bin/sh: 51: /root/.bashrc: Syntax error: Bad fd number", "stderr_lines": ["/bin/sh: 13: /root/.bashrc: shopt: not found", "/bin/sh: 21: /root/.bashrc: shopt: not found", "/bin/sh: 51: /root/.bashrc: Syntax error: Bad fd number"], "stdout": "", "stdout_lines": []} failed: [46.4.122.85] (item=prereg) => {"ansible_loop_var": "item", "changed": true, "cmd": ". /root/.bashrc && hdfs dfs -mkdir -p /user/ \"prereg\"", "delta": "0:00:00.005445", "end": "2020-03-23 15:24:46.341043", "item": "prereg", "msg": "non-zero return code", "rc": 2, "start": "2020-03-23 15:24:46.335598", "stderr": "/bin/sh: 13: /root/.bashrc: shopt: not found\n/bin/sh: 21: /root/.bashrc: shopt: not found\n/bin/sh: 51: /root/.bashrc: Syntax error: Bad fd number", "stderr_lines": ["/bin/sh: 13: /root/.bashrc: shopt: not found", "/bin/sh: 21: /root/.bashrc: shopt: not found", "/bin/sh: 51: /root/.bashrc: Syntax error: Bad fd number"], "stdout": "", "stdout_lines": []} failed: [46.4.122.85] (item=idrepo-qa) => {"ansible_loop_var": "item", "changed": true, "cmd": ". /root/.bashrc && hdfs dfs -mkdir -p /user/ \"idrepo-qa\"", "delta": "0:00:00.005433", "end": "2020-03-23 15:24:46.517143", "item": "idrepo-qa", "msg": "non-zero return code", "rc": 2, "start": "2020-03-23 15:24:46.511710", "stderr": "/bin/sh: 13: /root/.bashrc: shopt: not found\n/bin/sh: 21: /root/.bashrc: shopt: not found\n/bin/sh: 51: /root/.bashrc: Syntax error: Bad fd number", "stderr_lines": ["/bin/sh: 13: /root/.bashrc: shopt: not found", "/bin/sh: 21: /root/.bashrc: shopt: not found", "/bin/sh: 51: /root/.bashrc: Syntax error: Bad fd number"], "stdout": "", "stdout_lines": []}

PLAY RECAP *********************************************************************************************************************************** 46.4.122.85 : ok=208 changed=46 unreachable=0 failed=1 skipped=6 rescued=0 ignored=0

I noted that the part of the script started from
loop: - regprocessor-qa - prereg - idrepo-qa

  `- name: Giving user permission for directories created in previous step
    shell: . /root/.bashrc && hdfs dfs -chown -R "{{ item }}":"{{ item }}" /user/"{{ item }}"
    loop:
      - regprocessor-qa
      - prereg
      - idrepo-qa`

Is effected from the double quotes "" in the previous line.

Please would you check.

TASK [postgres-init : mosip_pmp: Update ip address in postgres init files] ************************************************************************************************* fatal: [console]: FAILED! => {"changed": false, "msg": "Destination /tmp/mosip/partner-management-services/db_scripts/mosip_pmp/mosip_pmp_deploy.properties does not exist !", "rc": 257}

I am running into the above error when running the ansible installation script (ansible-playbook -i hosts.ini site.yml)

I am running the sandbox deployment under the master branch.

mosip installation issue

Hi Team,

I am trying to install mosip version 1.1.2 on AZURE platform.

Hardware: centos 8
Number of machines: 7

Currently we are facing issue while installing mosip.

The playbooks regarding the kubernets cluster installation and non-mosip modules are successfully ran. However while running the ansible playbooks regarding the mosip modules are throwing below error.

Yamlfile: playbooks/config-server.yml
error: TASK [helm : Convert values template to values file] *****************************************************************************************
fatal: [console.internal.cloudapp.net]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: dict_keys object has no element 0"}

Please suggest any solutions regarding the issue.

Thank you.

Dev Installer: ssh key procedure fails as .ssh dir does not exist

Need to create .ssh directory before transferring the sftpkeys.

"Error: timed out wating for the condition" when installing grafana helm chart

Possibly related to issue #483

I am attempting to deploy the sandbox on azure. The terraform deployment works fine, and I believe mimics the AWS setup closely, but I am stuck on installing the helm charts. I get the same error on both 1.1.2 and 1.1.3 sandbox versions:

Debugging attempts

You can see that two previous charts installed by playbooks/mzmonitoring.yml were installed successfully using helm list --all --kubeconfig $kc -n monitoring

Running the install again manually with the --debug option shows the problem is due to the Persistent Volume claim not binding before timing out:

My understanding is that the persistence info for grafana is stored in the template file, referring to the storage class named nfs-provisioner which is created in the playbook playbooks/mz-nfs-provisioner.yml, with the details on the volume provision given in the template file within helm/charts/nfs-client-provisioner.

The storage class exists as expected:

So do the persistence volume claims:

Yet for some reason the grafana PVC is not binding to the storageclasses.

Also, I was able to follow the instructions on this blog and manually mount the nfs server to mzmaster, so it appears to be correctly configured.

Is this an issue anyone has encountered before? Any advice appreciated.

Thanks.

Error during TASK [postgres-init : Run mosip_kernel shell script]

Hi,

I am getting below error during the task TASK [postgres-init : Run mosip_kernel shell script]

TASK [postgres-init : Run mosip_kernel shell script] *******************************************************************************************************************
fatal: [console.sb]: FAILED! => {"changed": true, "cmd": "bash mosip_kernel_db_deploy.sh mosip_kernel_deploy.properties", "delta": "0:00:00.079061", "end": "2020-10-01 14:59:24.538886", "msg": "non-zero return code", "rc": 2, "start": "2020-10-01 14:59:24.459825", "stderr": "psql: /lib64/libpq.so.5: no version information available (required by psql)\npsql: /lib64/libpq.so.5: no version information available (required by psql)\npsql: could not connect to server: Connection refused\n\tIs the server running on host "mzworker0.sb" (192.168.10.186) and accepting\n\tTCP/IP connections on port 30090?", "stderr_lines": ["psql: /lib64/libpq.so.5: no version information available (required by psql)", "psql: /lib64/libpq.so.5: no version information available (required by psql)", "psql: could not connect to server: Connection refused", "\tIs the server running on host "mzworker0.sb" (192.168.10.186) and accepting", "\tTCP/IP connections on port 30090?"], "stdout": "10/01/2020 14:59:24 : mosip_kernel_deploy.properties\n10/01/2020 14:59:24 : Property file "mosip_kernel_deploy.properties" found.\n10/01/2020 14:59:24 : ------------------ Database server and service status check for mosip_kernel------------------------", "stdout_lines": ["10/01/2020 14:59:24 : mosip_kernel_deploy.properties", "10/01/2020 14:59:24 : Property file "mosip_kernel_deploy.properties" found.", "10/01/2020 14:59:24 : ------------------ Database server and service status check for mosip_kernel------------------------"]}

PLAY RECAP *************************************************************************************************************************************************************
console.sb : ok=172 changed=35 unreachable=0 failed=1 skipped=40 rescued=0 ignored=2
dmzmaster.sb : ok=11 changed=2 unreachable=0 failed=0 skipped=12 rescued=0 ignored=0
dmzworker0.sb : ok=23 changed=3 unreachable=0 failed=0 skipped=28 rescued=0 ignored=0
mzmaster.sb : ok=11 changed=2 unreachable=0 failed=0 skipped=12 rescued=0 ignored=0
mzworker0.sb : ok=23 changed=3 unreachable=0 failed=0 skipped=28 rescued=0 ignored=0
mzworker1.sb : ok=23 changed=3 unreachable=0 failed=0 skipped=28 rescued=0 ignored=0
mzworker2.sb : ok=23 changed=3 unreachable=0 failed=0 skipped=28 rescued=0 ignored=0

I am running this on our on-premise VMs (Total 7 Nos. 1 - Console, 1- MZ Master, 3 - MZ Workers, 1- DMZ Master, 1- DMZ Worker)

Please find below the ip mapping details

console.sb -> 192.168.10.184
mzmaster.sb -> 192.168.10.185
mzworker0.sb -> 192.168.10.186
mzworker1.sb -> 192.168.10.187
mzworker2.sb -> 192.168.10.188
dmzmaster.sb -> 192.168.10.189
dmzworker0.sb ->192.168.10.190

Port 30090 is opened on Console and also mzworker0
what might be the issue which is causing this error?

PKTGNR - 001 : Api Access Exception : registrationprocessor/v1/registrationstatus/sync

I have followed the instruction for the sandbox https://github.com/mosip/mosip-infra/blob/master/deployment/sandbox/README.md

The setup for all blocks (kernerl + pre-reg + reg-proc + id auth) went well and the setup logs showed failure=0

The issue I have is with the test to upload a packet as in the above guide.

In the MOSIP Registration Processor > Steps to upload a packet into Reg Proc, if we follow the recommended steps, and we try the url in the browser :

http://<public_ip_address>/v1/utility/packetgenerator/createAndUpload

The error returned is some error of type : "Api Access Exception"

{
"id": "io.mosip.packetgenerator.uploader",
"version": "version",
"responsetime": "2020-05-12T13:30:26.102Z",
"metadata": null,
"errors": [
{
"errorCode": "PKTGNR - 001",
"message": "Api Access Exception {"timestamp":"2020-05-12T13:30:26.017+0000","status":500,"error":"Internal Server Error","message":"No message available","path":"/registrationprocessor/v1/registrationstatus/sync"}"
}
],
"response": null

Please advise

ingress-nginx Helm Chart Installation Fails

I am getting the below error when I run the installation script : an site.yml .

MOSIP Version: 1.1.4

TASK [helm : Install chart ingress-nginx] ******************************************************************************************************************
fatal: [console.sb]: FAILED! => {"changed": true, "cmd": "/home/mosipuser/bin/helm --kubeconfig /home/mosipuser/.kube/mzcluster.config install ingress-nginx /home/mosipuser/mosip-infra/deployment/sandbox-v2/helm/charts/ingress-nginx -f /home/mosipuser/mosip-infra/deployment/sandbox-v2/helm/charts/ingress-nginx/values.yaml -n ingress-nginx --create-namespace --set-string dummy=value, --wait --timeout 20m0s --debug > /home/mosipuser/mosip-infra/deployment/sandbox-v2/tmp//yaml/ingress-nginx.yaml", "delta": "2:00:00.518503", "end": "2021-04-27 22:43:54.032629", "msg": "non-zero return code", "rc": 1, "start": "2021-04-27 20:43:53.514126", "stderr": "install.go:159: [debug] Original chart version: \"\"\ninstall.go:176: [debug] CHART PATH: /home/mosipuser/mosip-infra/deployment/sandbox-v2/helm/charts/ingress-nginx\n\nclient.go:108: [debug] creating 1 resource(s)\nclient.go:108: [debug] creating 10 resource(s)\nwait.go:53: [debug] beginning wait for 10 resources with timeout of 2h0m0s\nwait.go:225: [debug] Deployment is not ready: ingress-nginx/nginx-ingress-controller. 0 out of 1 expected pods are ready\nwait.go:225: 

mosip pre-registration automatic log out due to inactivity after vm restart

Hi,

I'm running the 1.1.3 sandbox on azure, and after restarting the vms (I stopped the vms to avoid billing when not using) I can view the pre-registration ui but whenever I attempt to login it automatically logs me out due to 'inactivity'.

Has anyone encountered this before?

Thanks.

Several pods failing after the installation of sandbox-v2

These are the pods that are failing after the installation:
prereg-booking-service
prereg-demographic-service
prereg-document-service
prereg-notification-service

I am attaching the logs of these. I have cloned the sandbox-v2-4

I need your advice about them.

Regards

prereg-notification-service.log
prereg-document-service.log
prereg-demographic-service.log
prereg-booking-service.log

'404' 'Not Found' 'No Message Available' Error in MOSIP's AuthN, AuthZ, and PMS APIs

I am getting the below error on multiple endpoints under AuthN, AuthZ, and PMS APIs.

 "status": 404,
    "error": "Not Found",
    "message": "No message available",

Here is an example request and response to the https://{base_url}/v1/authmanager/authenticate/internal/useridPwd endpoint:

Request:

{
  "id": "string",
  "metadata": {},
  "request": {
    "appId": "admin",
    "clientId": "mosip-admin-client",
    "clientSecret": "xyz123",
    "password": "mosip",
    "userName": "110006"
  }
}

Response:

{
    "timestamp": "2021-07-21T12:56:13.585+0000",
    "status": 404,
    "error": "Not Found",
    "message": "No message available",
    "path": "/partnermanagement/v1/misps/"
}

'Failed: No Internet Connection' on Reglient

I am getting the below error when I try to login to the regclient using the user 110011 and password MOSIP.

I have set the mosip.hostname's environment variable value to console.sb which is the hostname of my console VM.

MOSIP Registration UI

Hello,

I follow the procedure of installation of MOSIP (kernel, pre-registration and registration module) for Sandbox but I cannot access the Registration UI. For the Pre-registration it's working fine.
Also what about the others modules ? is there a procedure to install them in Sandbox ?

Regards,

Helm admin module installation timed out / failed

I have installed MOSIP 1.1.2 on-prem, only accessible over the Internal network/VPN, and using self-signed SSL certs.

When I try to access the pre-reg-ui, I am greeted with the below error:

When I run helm1 list and helm2 list to check if all modules were correctly installed, it shows that the admin module's installation failed.

I tried deleting the module, re-running it, and starting the admin playbook using these commands:
helm1 delete admin
an playbooks/admin.yml

But it times out by throwing the error: Error: timed out waiting for the condition

I tried increasing the timeout duration from 20 to 120 as suggested here #503 but this only makes it wait longer before it eventually throws the same error.

Dev Installer: Error in key manager service if keys are already present

Following exception occurs. We should not be needed to clear key alias table:

2019-09-16 10:36:34,689 [main] WARN [o.h.e.j.s.SqlExceptionHelper].logExceptions.129 : SQL Error: 0, SQLState: 23505
2019-09-16 10:36:34,690 [main] ERROR [o.h.e.j.s.SqlExceptionHelper].logExceptions.131 : ERROR: duplicate key value violates unique constraint "idx_keymals_id"
  Detail: Key (app_id, ref_id, key_gen_dtimes)=(KERNEL, SIGN, 2019-05-09 05:51:41) already exists.
2019-09-16 10:36:34,717 [main] ERROR [o.h.i.ExceptionMapperStandardImpl].mapManagedFlushFailure.39 : HHH000346: Error during managed flush [org.hibernate.exception.ConstraintViolationException: could not execute statement]
2019-09-16 10:36:34,800 [main] WARN [o.s.c.s.AbstractApplicationContext].refresh.558 : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'keymanagerController': Unsatisfied dependency expressed through field 'keymanagerService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'keymanagerServiceImpl': Invocation of init method failed; nested exception is org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint [idx_keymals_id]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement
2019-09-16 10:36:34,801 [main] INFO [o.s.o.j.AbstractEntityManagerFactoryBean].destroy.597 : Closing 

Installing chart elasticsearch fails

TASK [helm : Install chart elasticsearch] *******************************************************************************************************************************
fatal: [console.sb]: FAILED! => {"changed": true, "cmd": ["/home/mosipuser/bin/helm", "--kubeconfig",
"/home/mosipuser/.kube/mzcluster.config", "install", "elasticsearch", 
/home/mosipuser/mosip-infra/deployment/sandbox-v2/helm/charts/elasticsearch", "-f",
 "/home/mosipuser/mosip-infra/deployment/sandbox-v2/helm/charts/elasticsearch/values.yaml", "-n", "monitoring", 
"--create-namespace", "--set-string", "dummy=value,", "--wait", "--timeout", "20m0s"], "delta": "0:20:00.895887", 
"end": "2020-12-28 16:27:08.408529", "msg": "non-zero return code", "rc": 1, "start": "2020-12-28 16:07:07.512642", 
"stderr": "Error: timed out waiting for the condition", "stderr_lines": ["Error: timed out waiting for the condition"], "stdout": "",
"stdout_lines": []}

PLAY RECAP ***************************************************************************************************************
console.sb                 : ok=150  changed=85   unreachable=0    failed=1    skipped=23   rescued=0    ignored=0   
dmzmaster.sb               : ok=12   changed=9    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
dmzworker0.sb              : ok=12   changed=9    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
mzmaster.sb                : ok=50   changed=37   unreachable=0    failed=0    skipped=28   rescued=0    ignored=1   
mzworker0.sb               : ok=36   changed=26   unreachable=0    failed=0    skipped=27   rescued=0    ignored=0   
mzworker1.sb               : ok=36   changed=26   unreachable=0    failed=0    skipped=27   rescued=0    ignored=0   
mzworker2.sb               : ok=37   changed=27   unreachable=0    failed=0    skipped=27   rescued=0    ignored=0

ida-* pods failing in 1.1.4

I'm trying to deploy the current 1.1.4, but the pods:

ida-auth-service
ida-internal-service
ida-kyc-service
ida-otp-service

are failing, and the log says for the containers:

2021-01-08T18:40:26Z - [io.mosip.authentication.common.service.helper.RestHelper] - DEBUG - sessionId - RestHelper - requestSync - Response sent at : 2021-01-08T18:40:26.645898
2021-01-08T18:40:26Z - [io.mosip.authentication.common.service.helper.RestHelper] - DEBUG - sessionId - RestHelper - requestSync - Time difference between request and response in millis:3266.  Time difference between request and response in Seconds: 3.266
2021-01-08T18:40:26Z - [io.mosip.authentication.common.service.helper.RestHelper] - DEBUG - sessionId - RestHelper - requestSync - Request received at : 2021-01-08T18:40:26.675843
2021-01-08T18:40:26Z - [io.mosip.authentication.common.service.helper.RestHelper] - DEBUG - sessionId - RestHelper - generateAuthToken - Auth token generated successfully and set
2021-01-08T18:40:27Z - [io.mosip.authentication.common.service.helper.RestHelper] - ERROR - sessionId - RestHelper - checkErrorResponse - Throwing RestServiceException- CLIENT_ERROR
2021-01-08T18:40:27Z - [io.mosip.authentication.common.service.helper.RestHelper] - DEBUG - sessionId - RestHelper - checkErrorResponse - Throwing RestServiceException- CLIENT_ERROR
{"id":null,"version":null,"responsetime":"2021-01-08T18:40:26.996Z","metadata":null,"response":null,"errors":[{"errorCode":"KER-MSD-046","message":"Template not found."}]}
2021-01-08T18:40:27Z - [io.mosip.authentication.common.service.helper.RestHelper] - DEBUG - sessionId - RestHelper - requestSync - Response sent at : 2021-01-08T18:40:27.054333
2021-01-08T18:40:27Z - [io.mosip.authentication.common.service.helper.RestHelper] - DEBUG - sessionId - RestHelper - requestSync - Time difference between request and response in millis:378.  Time difference between request and response in Seconds: 0.378
2021-01-08T18:40:27Z - [io.mosip.authentication.common.service.cache.MasterDataCache] - ERROR - sessionId - io.mosip.authentication.common.service.cache.MasterDataCache - IDA-RST-006 - 4XX - Client Error occurred

Getting error on join kubernets workers

fatal: [mzworker0.sb]: FAILED! => {"changed": true, "cmd": "kubeadm join --token b0f7b8.8d1767876297d85c --discovery-token-unsafe-skip-ca-verification 10.10.10.86:6443\n", "delta": "0:05:00.323697", "end": "2021-11-27 10:16:17.469091", "msg": "non-zero return code", "rc": 1, "start": "2021-11-27 10:11:17.145394", "stderr": "error execution phase preflight: couldn't validate the identity of the API Server: Get "https://xx.xx.xx.xx:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s\": dial tcp xx.xx.xx.xx:6443: connect: connection refused\nTo see the stack trace of this error execute with --v=5 or higher", "stderr_lines": ["error execution phase preflight: couldn't validate the identity of the API Server: Get "https://xx.xx.xx.xx:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": dial tcp xx.xx.xx.xx:6443: connect: connection refused", "To see the stack trace of this error execute with --v=5 or higher"], "stdout": "[preflight] Running pre-flight checks", "stdout_lines": ["[preflight] Running pre-flight checks"]}

Dev Installer: Change default password hash algo in LDAP to SSHA-256

By default, if you insert a uid (people) in LDAP, it hashes password with SSHA. Make the default hash to SSHA-256.

Issues getting started with single VM deployment instructions

Hi there! 👋 I'm walking through the deployment steps documented in the developer readme and I'm documenting in this issue problems I had during the process.

Step 9

Clone mosip-platform repo:
$ git clone https://github.com/mosip/mosip-platform.git

This repo doesn't exist 😕

$ git clone https://github.com/mosip/mosip-platform.git
Cloning into 'mosip-platform'...
remote: Repository not found.
fatal: repository 'https://github.com/mosip/mosip-platform.git/' not found

I found this one instead and proceeded with that: https://github.com/mohbadar/mosip-platform
I assume this is a fork by someone trustworthy! 😉I've also noticed this same mistake in the Getting Started Guide.

Then this checkout doesn't work probably because it's not present on the substitute repo: $ git checkout 0.10.0_10232019_a I ran from master instead.

In the end, we did not successfully complete this deployment setup. Can you recommend another way to get started?

Thanks so much for your help! 🎉 ✨ 👾

Allow Github issue tracker specific regexes as valid data in githooks

As more open source contributors come in to the project, the issue tracker / bug tracker would be scattered across various Jira instances identified with the MOS-XXXX format (which is private currently) and across github issues for each corresponding project. The accepted means to automatically resolve and close issues on github which uses specific keywords.

Additionally commits and code changes can also be referenced using GH-X formats for a specific repository and can also be used to reference other repositories which would be useful for dependency bump ups, linking to remote security vulnerabilities etc..,

Enabling these regex changes to be allowed for github users to make commits and contribute would be a great start. Ideally it'd also be nice to have a single bug/issue tracker than have multiple of them.