Symptom

Alarm Notifications settings are configured under settings. Email notifications are not being seen. Checking the /var/log/nms/vmanage-server.log show the below error: 19-Apr-2022 16:48:02,040 UTC ERROR [] [NotificationsConsumer] (elastic-48) || Sending email notification failed javax.mail.MessagingException: Could not convert socket to TLS at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:2140) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:734) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at javax.mail.Service.connect(Service.java:342) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at javax.mail.Service.connect(Service.java:222) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at javax.mail.Service.connect(Service.java:171) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at javax.mail.Transport.send0(Transport.java:230) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at javax.mail.Transport.send(Transport.java:100) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at com.viptela.vmanage.server.notifications.NotificationsConsumer.sendMail(NotificationsConsumer.java:274) ~[vmanage-99.99.99.jar:?] at com.viptela.vmanage.server.notifications.NotificationsConsumer.onMessage(NotificationsConsumer.java:127) ~[vmanage-99.99.99.jar:?] at com.viptela.vmanage.server.messaging.MessageConsumer.onNext(MessageConsumer.java:89) ~[vmanage-99.99.99.jar:?] at com.viptela.vmanage.server.messaging.MessageConsumer$NamedConsumer.onNext(MessageConsumer.java:47) ~[vmanage-99.99.99.jar:?] at com.viptela.vmanage.server.messaging.MessageConsumer$NamedConsumer.onNext(MessageConsumer.java:26) ~[vmanage-99.99.99.jar:?] at com.viptela.vmanage.server.messaging.nats.NatsMessageBroker.lambda$subscribeMessage$5(NatsMessageBroker.java:308) ~[vmanage-messaging-core-1.0.12.jar:?] at com.viptela.vmanage.server.messaging.nats.ReactiveSubscriber.hookOnNext(ReactiveSubscriber.java:90) [vmanage-messaging-core-1.0.12.jar:?] at com.viptela.vmanage.server.messaging.nats.ReactiveSubscriber.hookOnNext(ReactiveSubscriber.java:22) [vmanage-messaging-core-1.0.12.jar:?] at reactor.core.publisher.BaseSubscriber.onNext(BaseSubscriber.java:160) [reactor-core-3.3.2.RELEASE.jar:3.3.2.RELEASE] at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:203) [reactor-core-3.3.2.RELEASE.jar:3.3.2.RELEASE] at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runAsync(FluxPublishOn.java:398) [reactor-core-3.3.2.RELEASE.jar:3.3.2.RELEASE] at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:484) [reactor-core-3.3.2.RELEASE.jar:3.3.2.RELEASE] at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84) [reactor-core-3.3.2.RELEASE.jar:3.3.2.RELEASE] at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37) [reactor-core-3.3.2.RELEASE.jar:3.3.2.RELEASE] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_162] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_162] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_162] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_162] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_162] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_162] Caused by: javax.net.ssl.SSLHandshakeException: Handshake failed at com.cisco.ciscossl.provider.ciscojce.ssl.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:736) ~[CiscoJCEProvider-6.0.10.jar:?] at com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:602) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:529) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:2135) ~[jakarta.mail-1.6.4.jar!/:1.6.4] ... 26 more Caused by: javax.net.ssl.SSLProtocolException: CiscoJCEJNI/Source/JNI_glue/SSL.cpp:throwSSLExceptionWithSslErrors: SSL handshake aborted: Failure in SSL library, usually a protocol error: error:0506706E:Diffie-Hellman routines:GENERATE_KEY:key size too small (dh_key.c:141 0x7f197216aafe:0x00000000): error:0506706E:Diffie-Hellman routines:GENERATE_KEY:key size too small at com.cisco.ciscossl.provider.ciscojce.CiscoJCENativeCrypto.SSL_do_handshake_Blocking(Native Method) ~[CiscoJCEProvider-6.0.10.jar:?] at com.cisco.ciscossl.provider.ciscojce.ssl.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:555) ~[CiscoJCEProvider-6.0.10.jar:?] at com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:602) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:529) ~[jakarta.mail-1.6.4.jar!/:1.6.4] at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:2135) ~[jakarta.mail-1.6.4.jar!/:1.6.4] ... 26 more

Conditions

seen on vManage version 20.4.2.1 but may affect other versions

Workaround

Further Problem Description