This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.
Summary
Error
[ThreadID:41] INFO: com.hp.ov.nms.admin.nnmcluster.NodeStateTransition setState: Transitioning NodeState from ACTIVE_DB_BACKUP to ACTIVE_DB_FAILED
[ThreadID:20] SEVERE: com.hp.ov.nms.admin.nnmcluster.ClusterDBSyncerImpl : Failed to created database backup : java.io.IOException: Unable to find the last log within the timeout
at com.hp.ov.nms.admin.nnmcluster.ClusterDBSyncerImpl.waitForBackupComplete(ClusterDBSyncerImpl.java:1279)
at com.hp.ov.nms.admin.nnmcluster.ClusterDBSyncerImpl.doBackup(ClusterDBSyncerImpl.java:1234)
at com.hp.ov.nms.admin.nnmcluster.ClusterDBSyncerImpl.backupIfRequired(ClusterDBSyncerImpl.java:445)
at com.hp.ov.nms.admin.nnmcluster.ClusterDBSyncerImpl.run(ClusterDBSyncerImpl.java:557)
[ThreadID:41] WARNING: com.hp.ov.nms.admin.nnmcluster.NnmCluster : DB backup on active node failed, trying potential remedies and then trying again...
[ThreadID:56] INFO: com.hp.ov.nms.admin.nnmcluster.DirectoryScanner run: Identified 3 files (0 txlogs) to send on this iteration.
[ThreadID:56] WARNING: com.hp.ov.nms.admin.nnmcluster.utils.ExecProc call: Command ("/opt/OV/nonOV/Postgres/bin/psql" "-d" "nnm" "-p" "5432" "-U" "postgres" "-c" "select pg_current_wal_lsn();" ) returned non-zero exit status: 2
Cause
Active server was upgrade from 10.10, Standby server is new installed
nnm-server-crypto-config.xml is different between active and standby server.
Fix
1.re-configure application failover.
2.Sync the nnm-server-crypto-config.xml from active server to standby server.
Related Documents:
KM03046631 NNMi and accessing the database