# MOSIP services v3 1.2.0.1 installation issues - kernel (notifier) , keymanager **URL:** \ **Category:** Support\ **Tags:** keymanager\ **Created:** [September 7, 2022, 8:51am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138 "2022-09-07T08:51:22Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\ **Post date:** [September 7, 2022, 8:51am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/1 "2022-09-07T08:51:22Z")
Hello! I would like to ask for help in solving the issues encountered during installation of MOSIP services v3 1.2.0.1, particularly: kernel (notifier) , keymanager ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/1b7c5ce119c6733e7f1035d5959af54f65b6f328.png) Events: Type Reason Age From Message * * * Warning Unhealthy 10m (x217 over 164m) kubelet Startup probe failed: HTTP probe failed with statuscode: 500 Normal Pulling 5m14s (x30 over 165m) kubelet Pulling image “[docker.io/mosipqa/kernel-notification-service:1.2.0.1](http://docker.io/mosipqa/kernel-notification-service:1.2.0.1)” Warning Unhealthy 24s (x669 over 163m) kubelet Startup probe failed: Get “[http://10.42.3.69:15020/app-health/notifier/startupz](http://10.42.3.69:15020/app-health/notifier/startupz)”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/53ed9ff59426fcf74cf725ceea66d0a559218cce.png) {“@timestamp”:“2022-09-07T06:06:15.676Z”,“@version”:“1”,“message”:“Could not locate PropertySource: I/O error on GET request for "[http://config-server.config-server/config/kernel/default/develop3-v3\](http://config-server.config-server/config/kernel/default/develop3-v3%5C)”: Connection refused (Connection refused); nested exception is java.net.ConnectException: Connection refused (Connection refused)",“logger\_name”:“org.springframework.cloud.config.client.ConfigServicePropertySourceLocator”,“thread\_name”:“main”,“level”:“WARN”,“level\_value”:30000,“appName”:“keys-generator”} Sorry. I don’t know how to attach log files that may be useful without making a very long post. Thank you. ---
**Author:** ![gsasikumar](https://avatars.discourse-cdn.com/v4/letter/g/b782af/32.png) [@gsasikumar](https://community.mosip.io/u/gsasikumar)\ **Post date:** [September 7, 2022, 10:48am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/2 "2022-09-07T10:48:03Z")
@rcsampang Yes, we see this problem in our environment as well. This seems to be a little specific to the V3 setup, We are investigating this problem, and will soon come back to you. For a workaround we moved the timeout to 300 ---
**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\ **Post date:** [September 14, 2022, 3:41am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/3 "2022-09-14T03:41:39Z")
@gsasikumar Thank you. It looks like changing the timeout to 300 did not fix it for me. Here is an excerpt of the log file: _2022-09-14 03:32:39,999 [http-nio-8083-exec-7] WARN [o.s.b.a.h.AbstractHealthIndicator].health.89 : Mail health check failed_ _javax.mail.MessagingException: Could not connect to SMTP host: [smtp.gmail.com](http://smtp.gmail.com), port: 587, response: 421_ _at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2197)_ _at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:740)_ _at javax.mail.Service.connect(Service.java:366)_ _at java.base/java.lang.Thread.run(Thread.java:829_) Further reading led me to changing the application-default.properties, is this the correct version to use? [mosip-config/application-default.properties at 1.2.0.1-v3 · mosip/mosip-config · GitHub](https://github.com/mosip/mosip-config/blob/1.2.0.1-v3/application-default.properties). Also in activemq, what is the password? I read that i should " Password: Run `get_pwd.sh`", but I can’t find the script/file? Could you point/send me the script/file? Best regards! ---
**Author:** ![gsasikumar](https://avatars.discourse-cdn.com/v4/letter/g/b782af/32.png) [@gsasikumar](https://community.mosip.io/u/gsasikumar)\ **Post date:** [September 19, 2022, 7:23am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/5 "2022-09-19T07:23:56Z")
Looks like the SMTP port is not accessible. Can you check if you are able to connect to the SMTP port? Gmail also has limitations in the number of emails that can be sent. ---
**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\ **Post date:** [September 21, 2022, 1:51am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/6 "2022-09-21T01:51:30Z")
I tested using telnet and ncat . Telnet results to SMTP service while ncat connects to UDP. The same results for Yahoo SMTP rke@dcsmosip:~$ telnet [smtp.gmail.com](http://smtp.gmail.com) 587 Trying 74.125.23.109… Connected to [smtp.gmail.com](http://smtp.gmail.com). Escape character is ‘^]’. 421 No SMTP service here Connection closed by foreign host. rke@dcsmosip:~$ nc -v -u [smtp.gmail.com](http://smtp.gmail.com) 587 Connection to [smtp.gmail.com](http://smtp.gmail.com) 587 port [udp/\*] succeeded! ^C rke@dcsmosip:~$ telnet [smtp.mail.yahoo.com](http://smtp.mail.yahoo.com) 587 Trying 66.218.88.167… Connected to [smtp.mail.us.am0.yahoodns.net](http://smtp.mail.us.am0.yahoodns.net). Escape character is ‘^]’. 421 No SMTP service here Connection closed by foreign host. rke@dcsmosip:~$ nc -v -u [smtp.mail.yahoo.com](http://smtp.mail.yahoo.com) 587 Connection to [smtp.mail.yahoo.com](http://smtp.mail.yahoo.com) 587 port [udp/\*] succeeded! ^C How do I proceed from here? Can i setup a local SMTP server using Posix and use that instead? I also did kubectl describe pod notifier-8459f88bc8-4krdx -n kernel … Events: Type Reason Age From Message * * * Warning Unhealthy 54m (x9158 over 5d2h) kubelet Startup probe failed: HTTP probe failed with statuscode: 500 Normal Pulling 49m (x1343 over 5d2h) kubelet Pulling image “[docker.io/mosipqa/kernel-notification-service:1.2.0.1](http://docker.io/mosipqa/kernel-notification-service:1.2.0.1)” Warning BackOff 14m (x2214 over 5d2h) kubelet Back-off restarting failed container Warning Unhealthy 4m29s (x28381 over 5d2h) kubelet Startup probe failed: Get “[http://10.42.3.110:15020/app-health/notifier/startupz](http://10.42.3.110:15020/app-health/notifier/startupz)”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) AND kubectl logs notifier-8459f88bc8-4krdx -n kernel … {“@timestamp”:“2022-09-21T05:34:49.422Z”,“level”:“ACCESS”,“level\_value”:70000,“traceId”:“ed0d462536d3677e”,“statusCode”:503,“req.requestURI”:“/v1/notifier/actuator/health”,“bytesSent”:353,“timeTaken”:10.010,“appName”:“kernel-notification-service”,“req.userAgent”:“kube-probe/1.23”,“req.xForwardedFor”:“-”,“req.referer”:“-”,“req.method”:“GET”,“req.remoteHost”:“127.0.0.6”} {“@timestamp”:“2022-09-21T05:34:57.317Z”,“level”:“ACCESS”,“level\_value”:70000,“traceId”:“b09c1978b9983691016575de6c188cc3”,“statusCode”:200,“req.requestURI”:“/v1/notifier/actuator/prometheus”,“bytesSent”:10952,“timeTaken”:0.008,“appName”:“kernel-notification-service”,“req.userAgent”:“Prometheus/2.28.1”,“req.xForwardedFor”:“-”,“req.referer”:“-”,“req.method”:“GET”,“req.remoteHost”:“127.0.0.6”} ---
**Author:** ![gsasikumar](https://avatars.discourse-cdn.com/v4/letter/g/b782af/32.png) [@gsasikumar](https://community.mosip.io/u/gsasikumar)\ **Post date:** [September 22, 2022, 9:20am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/7 "2022-09-22T09:20:58Z")
This is a little strange. Because the first error that you pointed out is with the SMTP response code 421. The 421 in Gmail means a server-side error or something about your IP address is unusual. Refer to the error code here [Gmail SMTP errors and codes - Google Workspace Admin Help](https://support.google.com/a/answer/3726730?hl=en) Have you tried with any other SMTP server? We just recently completed the development of a mock SMTP server to avoid these limitations. Please refer here. [GitHub - mosip/mock-smtp](https://github.com/mosip/mock-smtp/) We are in the process of testing this better. But you can run the docker or node version of this on a VM and point your SMTP to that SMTP server & port (8025). This could help overcome this problem. ---
**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\ **Post date:** [September 22, 2022, 2:44pm UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/8 "2022-09-22T14:44:35Z")
I also tried using Yahoo. No improvement. I will try it using the mock SMTP server you have just set up and report back the results. Is there a default username and password ? How do I add/configure users and passwords? Thanks! ---
**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\ **Post date:** [September 23, 2022, 5:15am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/9 "2022-09-23T05:15:19Z")
Thank you. Using the mock SMTP worked. I deleted and then re-installed the MOSIP modules. I used the new credentials in the msg-gateway installation Please enter the SMTP host x.x.x.x (IP of VM) Please enter the SMTP user [sasi@yazhi.io](mailto:sasi@yazhi.io) (user that worked in the test mail) Please enter the SMTP secret key (blank, no pasword) \*\*\* I don’t know yet how to add users and passwords in the mock SMTP server Then edited kernel-default.properties (1.2.0.1-v3) before re-instaling MOSIP modules [mosip.kernel.notification.email.from=sasi@yazhi.io](mailto:mosip.kernel.notification.email.from=sasi@yazhi.io) … spring.mail.port=8025 Successful! There is no longer error in kernel notifier installation. While for keymanager I increased the idle timeout from 0 to 60s at deployment/v3/mosip/keymanager/idle\_timeout\_envoyfilter.yaml … name: envoy.filters.network.tcp\_proxy typed\_config: ‘@type’: [type.googleapis.com/envoy.config.filter.network.tcp\_proxy.v2.TcpProxy](http://type.googleapis.com/envoy.config.filter.network.tcp_proxy.v2.TcpProxy) idle\_timeout: 60s **Thus kernel and keymanager successfully installed.** I have also managed to get the ActiveMQ password after deleting and reinstalling the module. Unfortunately, now I am encountering issues in installing Registration Processor - I will create a new topic for that since the issues in kernel notifier and keymanager are resolved. ---
**Author:** ![slimab](https://avatars.discourse-cdn.com/v4/letter/s/8dc957/32.png) [@slimab](https://community.mosip.io/u/slimab)\ **Post date:** [March 29, 2023, 10:52am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/10 "2023-03-29T10:52:56Z")
Hello, We are installing the platform mosip behind a proxy, when installing the SMTP we put it the host value [gmail.com](http://gmail.com) we get this error: WARN [o.s.b.a.h.AbstractHealthIndicator].health.89 : Mail health check failed javax.mail.MessagingException: Could not connect to SMTP host: [gmail.com](http://gmail.com), port: 8025, response: -1 Any recommendation to resolve the problem or do we have to deploy a local SMTP server to avoid connecting to outside thanks ---
**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\ **Post date:** [March 29, 2023, 11:29am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/11 "2023-03-29T11:29:51Z")
What version of MOSIP are you using? I have just upgraded to v1.2.0.1-B2 because my previous installation crashed due to ungraceful shutdown of the cluster caused by a power failure. In this version mock-smtp is fully integrated, although you have to include it in the install-all.sh script at mosip-infra/deployment/v3/mosip/all. In my case I placed it after artifactory. In v1.2.0.1-B2, the new mock-stmp is deployed as an application in the MOSIP K8s cluster, so it is easier to manage and monitor. Also in this version, while installing msg-gateway you will be prompted with a question if you will use mock-smtp? If you answer Yes, everything will be configured for you. You just have to install/deploy mock-smtp by going to the mock-smtp directory and run the install.sh script or include it in the install-all.sh as I have stated above. In version 1.2.0.1, I was not able to make it run on Gmail, so I installed the MOSIP mock-smtp and run it in a separate VM, in my case the Nginx VM. That worked but it means I have to monitor it separately from the cluster. I hope that helps. ---
**Author:** ![gsasikumar](https://avatars.discourse-cdn.com/v4/letter/g/b782af/32.png) [@gsasikumar](https://community.mosip.io/u/gsasikumar)\ **Post date:** [April 3, 2023, 7:23am UTC](https://community.mosip.io/t/mosip-services-v3-1-2-0-1-installation-issues-kernel-notifier-keymanager/138/12 "2023-04-03T07:23:49Z")
@slimab I think Gmail has blocked all SMTP access until it comes through a secure channel. I would recommend using [mockSMTP](https://github.com/mosip/mock-smtp/) for development or QA needs.