Hi,
This seems to happen whenever I have to shut down both servers within the cluster. Both nodes cleanly shutdown via the shutdown command in the management/high availability menu.
Bought both nodes back online, however, the slave node comes back with a config error as below.
There is a process that runs at 1.30am BST that appears to clean up the databases and fixes the issue, can I execute this on an ad-hoc basis to resolve this?
2010:05:06-10:01:23 mercury-2 slon[14837]: [32-1] 2010-05-06 10:01:23 BSTFATAL main: Node is not initialized properly - sleep 10s
2010:05:06-10:01:24 mercury-2 slon[5491]: [902-1] 2010-05-06 10:01:24 BSTINFO remoteWorkerThread_1: syncing set 1 with 9 table(s) from provider 1
2010:05:06-10:01:24 mercury-2 slon[5491]: [903-1] 2010-05-06 10:01:24 BSTINFO remoteWorkerThread_1: SYNC 5000000404 done in 0.009 seconds
2010:05:06-10:01:28 mercury-1 slon[5264]: [832-1] 2010-05-06 10:01:28 BSTCONFIG version for "dbname=reporting host=X.X.X.X user=ha_sync password=XX" is 80403
2010:05:06-10:01:28 mercury-1 slon[5264]: [833-1] 2010-05-06 10:01:28 BSTERROR remoteListenThread_2: "select "_asg_cluster".registerNodeConnection(1); " - ERROR: schema
2010:05:06-10:01:28 mercury-1 slon[5264]: [833-2] "_asg_cluster" does not exist
Many thanks,
Darren
