Hi,
Â
We are experiencing an issue in our new up.time installation in our data centers, using a modified version of the File and Directory Monitor plug-in.
We get the following stacktrace when running “Test Service Monitor”:
2015-02-24 11:15:30,316 | DEBUG | uau4rs | ServiceThread-1 started@2015-02-24T11:15:30 | [z7vxpv] Failed to run script.
java.lang.NullPointerException
              at com.uptimesoftware.uptime.erdc.MonitorCustomScriptRunner.parseOutput(MonitorCustomScriptRunner.java:91)
              at com.uptimesoftware.uptime.erdc.MonitorCustomScriptRunner.monitor(MonitorCustomScriptRunner.java:59)
              at com.uptimesoftware.uptime.erdc.baseclass.Monitor.run(Monitor.java:163)
              at com.uptimesoftware.uptime.erdc.helper.ERDCRunner.runErdc(ERDCRunner.java:64)
              at com.uptimesoftware.uptime.base.event.erdc.ErdcEventRunner.runEvent(ErdcEventRunner.java:23)
              at com.uptimesoftware.uptime.base.event.erdc.ERDCEventProcessor.runServiceMonitor(ERDCEventProcessor.java:358)
              at com.uptimesoftware.uptime.base.event.erdc.ERDCEventProcessor.process(ERDCEventProcessor.java:151)
              at com.uptimesoftware.uptime.base.RunnableERDCEvent.run(RunnableERDCEvent.java:19)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
              at java.lang.Thread.run(Unknown Source)
The alert mail that we receive contains the following:
Host: itsusragtsqn1.jnj.com (OK)
Service: sschols test
Service State: CRIT
Output: Failed to run script: null
Some time ago, we modified that custom script on a trial version of up.time, and everything worked perfectly on our test system.
Can you indicate what the problem might be and what we have to be looking for?
Â
Kind regards.