-
Title
SNMP actions halt after a period of time; FMS must be recycled to resolve. -
Description
Integration action stops after server is running for a couple of days as we noted our HP/OV was not receiving the Foglight alarms; this was not an issue on the 5.5.0 FMS, only observed after update to 5.5.5
We verified the opcmsg processes were still running.
ps -ef |grep opcmsg------------------------------
$ ps -ef |grep opcmsg
root 19440 19390 0 Mar22 ? 00:00:12 /opt/OV/lbin/eaagt/opcmsga
root 19539 19390 0 Mar22 ? 00:00:02 /opt/OV/lbin/eaagt/opcmsgi
c13122 32354 32287 0 09:41 pts/2 00:00:00 grep opcmsg -
Cause
Software bug.
The process runner did not exist in 5.5.0, and was only added for 5.5.4. Previously, the integration cartridge was just using the Java exec() code. The program flow from the trace file (fms -t) indicates opcmsg runs and then exits, so it looks like the FMS is not getting the notification that the process input stream has been created until after the process has run and exited; causing a deadlock.
-
Resolution
STATUS: COM-1250 is fixed in 5.6.4 release.
WORKAROUND: Set FMS to start with switch -Dfoglight.process.qcnrunner.disabled=true.
Cmd line options can be added in $FGLHOME/config/foglight.config file as documented within the file.
An example is shown below for the option provided and the comment # removed from the beginning of the line..# Additional command line options (up to 10) for fms [or fms.exe if in windows]
# They must be quoted and the lines have to end with a semicolon
#
foglight.cmdline.option0 = "-Dfoglight.process.qcnrunner.disabled=true"; -
Defect ID
COM-1250