V8.4 Alarm server waiting for initialisation on secondary server.

Question

V8.4 Primary and Secondary server configuration.

Which ever server starts second the alarm server will not start and instead just waits for initialisation. Sometimes overnight it will eventually start. sometimes it will wait a week and not take off.
Im unsure what the error can be as there should have been no fundamental changes and this has worked fine for the last year or so since we got V8.4

Jacky Lang · Answer

Hi Travis Bailey 
 It looks like the alarm synchronization process was stuck until timeout. Do you know what v8.40 update is installed on the system? Below are troubleshooting steps, which hopefully shows some light on the issue. 
 
 Make sure both alarm server nodes have configured the server password correctly 
 Dump kernel of both alarm servers when the problem occurs. 
 Check alarm servers' status in Kernel General when both are up running (the first startup one should be "Main" and the other should be "Standby"). 
 Take a look at syslog of both alarm servers. Some errors may have already logged, something like
 
 "Auth: Login, Failed, \Default server user, Remote, Invalid User" 
 "TranWrite failed before secure login completed"

V8.4 Alarm server waiting for initialisation on secondary server.

Top Replies