Hello all,
I have got the same symptoms on beacon after teledistribution.
Context : Red Hat 7.x, Oracle, Upgrade from 15.7.0 to 15.9.0, cluster of 3 servers, multicast on IP 239.0.0.1
- Server 1 : CSA running, upgrade is done. beacon start correctly after upgrade
- Server 2 : Code teledistributed. Error beacon : may have failed to start.
- Server 3 : Code teledistributed. Error beacon : may have failed to start.
Note that nothing changed on the network level : multicast on same IP / ports.
Logs beacon-system on servers 2 and 3 :
Launching a JVM...
WrapperManager: Initializing...
Failed to communicate: 239.0.0.1 : 9090
on_exit trigger matched. Restarting the JVM. (Exit code: 1)
Launching a JVM...
WrapperManager: Initializing...
Failed to communicate: 239.0.0.1 : 9090
on_exit trigger matched. Restarting the JVM. (Exit code: 1)
Launching a JVM...
WrapperManager: Initializing...
Failed to communicate: 239.0.0.1 : 9090
on_exit trigger matched. Restarting the JVM. (Exit code: 1)
Launching a JVM...
WrapperManager: Initializing...
Failed to communicate: 239.0.0.1 : 9090
on_exit trigger matched. Restarting the JVM. (Exit code: 1)
Launching a JVM...
WrapperManager: Initializing...
Failed to communicate: 239.0.0.1 : 9090
on_exit trigger matched. Restarting the JVM. (Exit code: 1)
There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
There may be a configuration problem: please check the logs.
I will try the following actions :
- Restart the servers
- Copy-paste the folder $NIKU_HOME as mentioned above
Regards,
David
------------------------------
Consultant
CoPrime
------------------------------
Original Message:
Sent: 10-17-2016 05:24 PM
From: Anon Anon
Subject: Re: Beacons can't communicate after NSA upgrade
Hi,
No – I got the same behaviour in each of three environments. But after copying $NIKU_HOME from the NSA box to the others and editing properties.xml, everything works correctly.
Thanks
Chris