BUG: NCPA Agent doesn't properly report iptables status

[eloyd]

There doesn't seem to be a more specific board for NCPA, so I'm posting this here.

Code: Select all

https://192.168.1.11:5693/api/service/httpd/running

That works fine:

Code: Select all

{
  "value": {
    "returncode": 0, 
    "stdout": "OK: Service httpd is running"
  }
}

But change http to iptables, and it fails, even though iptables is running:

Code: Select all

{
  "value": {
    "returncode": 2, 
    "stdout": "CRITICAL: Service iptables is stopped"
  }
}

I'm pretty sure this has to do with the fact that "service itpables status" does not return a "is running..." string, but instead returns the current results of "itpables --list" So I'm guessing NCPA's parser doesn't see the "is running" and assumes that it "is stopped." So can't check to see that iptables is running that way.

Also can't check via /api/processes, because it doesn't show up in the list!

Would love to switch all our NRPE stuff over to NCPA, but if we can't get accurate process/service information, we can't convert.

[hsmith]

Hey!

Do you think you would be able to post that here? It will be seen quicker by the devs that way

[eloyd]

Okay. Forums are always my goto spot for stuff, since I can never remember what system is tracking what software.

https://github.com/NagiosEnterprises/ncpa/issues/232

[hsmith]

Thanks for posting it there, generally with the open source projects, it's best to post on GitHub, because that's what we'll end up doing anyway

[eloyd]

Since you didn't lock this, I'll add, "but that's what customer support is supposed to do for us!!"

[hsmith]

2016-06-09 15_11_38-BUG_ NCPA Agent doesn't properly report iptables status - View topic • Nagios Su.png (6.99 KiB) Viewed 3317 times

Locking.