Error Message

 

Following last messages are seen on the Managed Host in the '/var/opt/VRTSsfmh/logs/mhrun.log' which do not give a clear indication of the problem. No other obvious log or errors are reported on the Managed Host:

Thu Jun  2 09:57:22 2011 [debug] run_discovery: V-0000-0000 json = {"JOB":{"ERROR":"","ISHIDDEN":0,"RETURNCODE":0,"NAME":"run_discovery","OUTPUT":"{\n   \"RESULT\" : {\n      \"UMI\" : null,\n      \"RETURNCODE\" : 0,\n      \"RESULT\" : null\n   }\n}\n\n","STATE":"SUCCESS","PROGRESS":100}}
Thu Jun  2 09:57:22 2011 [debug] run_discovery: V-0000-0000 Triggering appropriate discoveries
Thu Jun  2 09:57:22 2011 [debug] run_discovery: V-0000-0000 Summarizing
Thu Jun  2 09:57:22 2011 [debug] run_discovery: V-0000-0000 Final Packet = {"RESULT":{"UMI":null,"ERROR":"","RETURNCODE":0,"RESULT":null,"NAME":"configure_mh"}}

 

Following repetitive error messages are seen in the '/var/opt/VRTSsfmcs/logs/dbsync.log' on the Managed Server:

Thu Jun  2 09:58:35 2011 [error] Dbsync: V-0000-0000 LOG FILE NAME = /var/opt/VRTSsfmcs/data/{00020014-4fe2-c23c-0000-000084e2c23c}.LDR.diff.sql
Thu Jun  2 09:58:35 2011 [debug] Dbsync: V-0000-0000 [START]::[{00020014-4fe2-c23c-0000-000084e2c23c}] Reporting with Type as [JSON]
Thu Jun  2 09:58:35 2011 [debug] Dbsync: V-0000-0000 File Name = [/var/opt/VRTSsfmcs/data/{00020014-4fe2-c23c-0000-000084e2c23c}.LDR.diff.sql]
Thu Jun  2 09:58:35 2011 [debug] Dbsync: V-0000-0000 LOCALE = [en_US.UTF-8]
Thu Jun  2 09:58:35 2011 [error] Dbsync: V-0000-0000 [END] Service Unavailable
 

 

The following VOM upgrade lock/flag file is not cleared after the completion of the install/upgrade of the VOM Management Server:

-rw-rw-rw-   1 nobody   nobody         0 May 19 13:01 /var/opt/VRTSsfmh/cms_upgrade_in_progress

The solution to the problem will require the VOM Management Server processes and the database to be restarted after removing the stale upgrade lock/flag file which exists in the system.

The following procedure should resolve the problem. Please note, if the VOM Management Server is configured in a VCS Cluster, then you may use the VCS cluster to stop and start the SFM Services. The procedure below is only for VOM Managed Server configured on a standalone VOM CMS.

1.]  Stop the VOM processes on CMS on Unix/Linux:

Stop the xprtld daemon service:
# /opt/VRTSsfmh/adm/xprtldctrl stop

Stop Web console service:
# /opt/VRTSsfmcs/cweb/sfmw  stop

Stop the VOM Database:
# /opt/VRTSsfmcs/config/adm/vxsfmcsdb stop

Stop the Authentication daemon service:
# /opt/VRTSsfmcs/sec/bin/sfmsecdctrl stop
 

 

2.]  Remove the stale upgrade lock/flag file:

# rm -f /opt/VRTSsfmh/cms_upgrade_in_progress

 

3.]  Start the VOM processes on CMS on Unix/Linux:

Start the Authentication daemon service:
# /opt/VRTSsfmcs/sec/bin/sfmsecdctrl start

Start the VOM Database:
# /opt/VRTSsfmcs/config/adm/vxsfmcsdb start

Start the Web console service:
# /opt/VRTSsfmcs/cweb/sfmw  start

Start the xprtld daemon service:
# /opt/VRTSsfmh/adm/xprtldctrl start

 

4.]  Add/Configure the VOM Managed Host using the web interface or using the gendeploy.pl script:

 

 

Please Note: If removing the flag file and restarting the VOM processes does not fix the issue, then it is possible that there may be a problem with the VOM Database. Please contact Veritas Technical Support for further troubleshooting and assistance.
 

Veritas Operations Manager (VOM) Management Server upgrade will be successful with no errors, but even after that, the VOM database will not start correctly and hence it fails to add, configure or monitor any of the VOM Managed Hosts. VOM installation/upgrade process will set a lock/flag in the system to disallow any other operations to the VOM database at the time of the upgrade. This lock/flag is set by creating the following lock/flag file:

-rw-rw-rw-   1 nobody   nobody         0 May 19 13:01 /var/opt/VRTSsfmh/cms_upgrade_in_progress

If the VOM installation binary is executed more than once or if for any reason the flag file was unable to be removed,  the VOM database will not be able to start correctly and all updates to the VOM database will fail.