The command runs successfully if command line given in the Foglight rule is executed from the cmd prompt.
ie: D:\FoglightToZenoss\Python27\python D:\FoglightToZenoss\zenpublish\zenoss-event.py -z 192.168.0.1 -u robot -p r0b0t -n -s 5 -d "Unknown" -c "Credential Management Event" -m "Cannot establish connection to myhost.corp.mycompany.com: received HTTP/401 - credentials rejected"
Yet this does not work when Foglight issues the cmd from the Alarm Forwarding rule when configured as shown in the attached document.
Turning on debug 2 and review the FMS log when the rule triggers we see this error message:
=== End dumping string list
2014-11-19 16:31:09.502 DEBUG [Action-4-thread-2173] com.quest.common.launcher.runner.ProcessNativeImpl - Creating socket connection to process runner on 127.0.0.1 port 49219
2014-11-19 16:31:09.502 ECHO WARN [Thread-49240] Launcher\src\process_runner - stderr: 2014-11-19 16:31:09.000 ERROR [native] Failed to start process: (null)
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center