The Server group is not working properly, the server group logs show that connection times out. arsrvgrp.log .................. Unable to send message to remote peer. Message was: Connection refused to host: {IP Address}; nested exception is: java.net.ConnectException: Connection timed out: connect java.rmi.ConnectException: Connection refused to host: {IP Address}; nested exception is: java.net.ConnectException: Connection timed out: connect at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source) ~[na:1.8.0_91] at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source) ~[na:1.8.0_91] at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source) ~[na:1.8.0_91] at sun.rmi.server.UnicastRef.invoke(Unknown Source) ~[na:1.8.0_91] at net.sf.ehcache.distribution.RMICachePeer_Stub.send(Unknown Source) ~[ehcache-core-2.6.9.jar:na] at net.sf.ehcache.distribution.RMIAsynchronousCacheReplicator.writeReplicationQueue(RMIAsynchronousCacheReplicator.java:314) [ehcache-core-2.6.9.jar:na] at net.sf.ehcache.distribution.RMIAsynchronousCacheReplicator.replicationThreadMain(RMIAsynchronousCacheReplicator.java:127) [ehcache-core-2.6.9.jar:na] at net.sf.ehcache.distribution.RMIAsynchronousCacheReplicator.access$000(RMIAsynchronousCacheReplicator.java:58) [ehcache-core-2.6.9.jar:na] at net.sf.ehcache.distribution.RMIAsynchronousCacheReplicator$ReplicationThread.run(RMIAsynchronousCacheReplicator.java:389) [ehcache-core-2.6.9.jar:na] Caused by: java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.connect0(Native Method) ~[na:1.8.0_91] at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) ~[na:1.8.0_91] .................. |
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. This behavior has been reported as a defect. First check this article in case it helps in case the defect is not the root cause, otherwise apply the Hot Fix: Remedy - Server - Escalation failover is not working with error:"Unable to send message to remote peer. Message was: Connection refused to host..." v9.1.00: ....................... SW00523566 - Server Group Errors - Unable to send message to remote peer ....................... v9.1.02: ....................... SW00524394 - Server Group Errors - Unable to send message to remote peer ....................... For version 9.1.00: apply the latest available Hot Fix located in the below FTP: ftp://ftp.bmc.com/pub/ARRecommendedFixes/Server/9.1/ For version 9.1.02: It has been addressed in 9.1.03 (SP3) If for some reason, being on 9.1.02 (SP2) and SP3 cannot be implemented, the latest available Hot Fix for SP2 addresses this behavior. It can be found in the below public FTP location: ftp://ftp.bmc.com/pub/ARRecommendedFixes/Server/9.1SP2/ |