check_log3.exe giving a response code 255

[hbouma]

We have a single Windows 2012 server where the check_log3.exe plugin is returning a 255 response code:

Code: Select all

File returned contained:
{
    "returncode": 255,
    "stdout": ""
}

The check worked great for months, then stopped today. We have replaced the plugin incase it was corrupt, but it still is broken.

Check command is

Code: Select all

check_ncpa.py -H SERVERNAME  -t TOKEN-M 'plugins/check_log3.exe' -q 'args=-l LOGFILE,args=-s TEMPFILE,args=-p "CONDITIONS",args=-w 1,args=-c 1'

All other checks on the box work fine. Has anyone else experienced this?

[lmiltchev]

I haven't been able to recreate the issue. I tried running the plugin against a simple fake log:

Code: Select all

line 1
line 2
line 3: ERROR
line 4: ERROR
line 5: ERROR

NCPA and check_log3.exe plugin worked as expected. On the first run:

example-01.jpg

On the second run:

Code: Select all

{
    "returncode": 0,
    "stdout": "OK: Found 0 lines (limit=1/1): No matches found.|lines=0"
}

Can you run your check from the command line with increased verbosity, and show the output?

Code: Select all

./check_ncpa.py -H SERVERNAME  -t TOKEN-M 'plugins/check_log3.exe' -q 'args=-l LOGFILE,args=-s TEMPFILE,args=-p "CONDITIONS",args=-w 1,args=-c 1' -v

What is the NCPA version that you are currently using?

Code: Select all

./check_ncpa.py -H SERVERNAME  -t 'TOKEN' -M 'system/agent_version'

What is the version of the "check_log3.exe" plugin?

Code: Select all

/check_ncpa.py -H SERVERNAME -t 'TOKEN' -M 'plugins/check_log3.exe' -q 'args=-v'

Haven you made any changes on the server, prior to noticing the issue? Have you looked into the ncpa_listener.log for clues?

[hbouma]

NCPA agent 2.1.5

I am still working internally to get access to the server so that I can get the logs and troubleshoot. I will reply with more info once I have it.

[lmiltchev]

Sure thing.

FYI, I tested this with NCPA v2.1.8 and check_log3.exe version 3.11d.

Let us know when you have some more info.

[hbouma]

Ok, before I could get on the server and do anything, it just started working again.

I did notice that the plugin version 3.14 has fixes for this error. I am applying that version now as we were on the old 3.11d version.

Go ahead and close this thread.

[lmiltchev]

I am glad your issues has been resolved! I am closing this thread. Thank you!