BUG: NCPA Agent doesn't properly report iptables status
Posted: Thu Jun 09, 2016 2:53 pm
There doesn't seem to be a more specific board for NCPA, so I'm posting this here.
That works fine:
But change http to iptables, and it fails, even though iptables is running:
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.
Code: Select all
https://192.168.1.11:5693/api/service/httpd/running
Code: Select all
{
"value": {
"returncode": 0,
"stdout": "OK: Service httpd is running"
}
}
Code: Select all
{
"value": {
"returncode": 2,
"stdout": "CRITICAL: Service iptables is stopped"
}
}
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.
