SSIM Failover Configuration
Hi,
I tested our SSIM failover configuration and had the following error in the sesa-agent.log. I tested what happens when I turn off the main appliance. After the third attempt the agent stopped working and nothing happen. If I change the failover retry attempt to 1 everything works fine.
2009-11-10 13:20:57,046 INFO [Logging] >>ForwardingProvider.sendEvents() - Exception: java.io.IOException: connection to manager failed, retry later (30) seconds.
2009-11-10 13:20:57,046 ERROR [Logging] java.io.IOException: connection to manager failed, retry later (30) seconds.
at com.symantec.management.providers.config.ConfigProvider.getMgmtServerConnectionEx(ConfigProvider.java:2231)
at com.symantec.management.providers.config.ConfigProvider.getMgmtServerConnection(ConfigProvider.java:2046)
at com.symantec.management.providers.forwarder.SESAEventForwardingProvider.sendEvents(SESAEventForwardingProvider.java:386)
at com.symantec.management.providers.forwarder.SESAEventForwardingProvider.forwardEvents(SESAEventForwardingProvider.java:234)
at com.symantec.cas.agent.queue.PersistentAgentQueue.sendEvents(PersistentAgentQueue.java:986)
at com.symantec.cas.agent.queue.PersistentAgentQueue.sendEvents(PersistentAgentQueue.java:958)
at com.symantec.cas.agent.queue.PersistentAgentQueue.run(PersistentAgentQueue.java:874)
at java.lang.Thread.run(Unknown Source)
2009-11-10 13:21:07,062 INFO [Logging] Response code = 500, URL = https://192.168.1.100:443/sesa/servlet/eventlogger
2009-11-10 13:21:07,062 INFO [Logging] >>ForwardingProvider.sendEvents() - Exception: java.io.IOException: connection to manager failed, retry later (30) seconds.
2009-11-10 13:21:07,062 ERROR [Logging] java.io.IOException: connection to manager failed, retry later (30) seconds.
at com.symantec.management.providers.config.ConfigProvider.getMgmtServerConnectionEx(ConfigProvider.java:2231)
at com.symantec.management.providers.config.ConfigProvider.getMgmtServerConnection(ConfigProvider.java:2046)
at com.symantec.management.providers.forwarder.SESAEventForwardingProvider.sendEvents(SESAEventForwardingProvider.java:386)
at com.symantec.management.providers.forwarder.SESAEventForwardingProvider.forwardEvents(SESAEventForwardingProvider.java:234)
at com.symantec.cas.agent.queue.PersistentAgentQueue.sendEvents(PersistentAgentQueue.java:986)
at com.symantec.cas.agent.queue.PersistentAgentQueue.sendEvents(PersistentAgentQueue.java:958)
at com.symantec.cas.agent.queue.PersistentAgentQueue.run(PersistentAgentQueue.java:874)
at java.lang.Thread.run(Unknown Source)
2009-11-10 13:21:17,078 INFO [Logging] Response code = 500, URL = https://192.168.1.100:443/sesa/servlet/eventlogger
2009-11-10 13:21:17,078 INFO [Logging] >>ForwardingProvider.sendEvents() - Exception: java.io.IOException: connection to manager failed, retry later (30) seconds.
2009-11-10 13:21:17,078 ERROR [Logging] java.io.IOException: connection to manager failed, retry later (30) seconds.
at com.symantec.management.providers.config.ConfigProvider.getMgmtServerConnectionEx(ConfigProvider.java:2231)
at com.symantec.management.providers.config.ConfigProvider.getMgmtServerConnection(ConfigProvider.java:2046)
at com.symantec.management.providers.forwarder.SESAEventForwardingProvider.sendEvents(SESAEventForwardingProvider.java:386)
at com.symantec.management.providers.forwarder.SESAEventForwardingProvider.forwardEvents(SESAEventForwardingProvider.java:234)
at com.symantec.cas.agent.queue.PersistentAgentQueue.sendEvents(PersistentAgentQueue.java:986)
at com.symantec.cas.agent.queue.PersistentAgentQueue.sendEvents(PersistentAgentQueue.java:958)
at com.symantec.cas.agent.queue.PersistentAgentQueue.run(PersistentAgentQueue.java:874)
at java.lang.Thread.run(Unknown Source)
2009-11-10 13:21:27,078 INFO [Logging] Response code = 500, URL = https://192.168.1.100:443/sesa/servlet/eventlogger
2009-11-10 13:21:27,078 INFO [Logging] Attempt (1) - Retrying failed connection: https://192.168.1.100:443/sesa/servlet/
2009-11-10 13:24:36,093 INFO [Logging] >>ForwardingProvider.sendEvents() - Exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
2009-11-10 13:24:36,093 ERROR [Logging] javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.symantec.management.util.SSL_Socket.createSocket(SSL_Socket.java:245)
at com.symantec.management.util.SESAHttpConnection.connect(SESAHttpConnection.java:209)
at com.symantec.management.util.SESAHttpConnection.connect(SESAHttpConnection.java:142)
at com.symantec.management.providers.forwarder.SESAEventForwardingProvider$Connector.run(SESAEventForwardingProvider.java:1039)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
... 8 more
Comments
Can you give some more
Can you give some more details about your setup?
Which agent version are you using (4.5 or 4.7)?
If it is the the 4.7 version, is the Symantec Event Agent Manager Service running?
What version of SSIM are you using (exact patch level)?
Is LDAP replication in place?
All the appliance configuration settings? (System->Appliance Configuration)
Complete sesa-agent.log and mgmserverinfo.dat from an agent where the failover fails.
Complete logs from all the appliances which are part of the configuration.
I would recommend that you open a case with technical support as you probably don't ewnat to post al;l of the information to this forum.
Thank you Olaf. I collect
Thank you Olaf.
I collect the information that you request and open a case on the technical site
Would you like to reply?
Login or Register to post your comment.