Nagios Support Forum

hello, for changes made to the server 10.10.10.68 we had to restart it, and when restarting it, the "spooler consumption and number of processes" was unknown and the "number of processes" of server 10.10.10.69 was added to unknown. After a few minutes the problem of 10.10.10.68 was solved and the problem started on the server 10.10.10.69


__

Hello, a few minutes ago we had the fall of the service spoolsv.exe when uploading I am also working the count of processes in the same server 10.10.10.69 that during the morning had happened to be like "unknown" ... I hope it was operative for siemrpe and not for the moment

Service Notification[02-22-2018 18:32:23] SERVICE NOTIFICATION: nagiosadmin;01-Sv-10.69;Spooler;OK;notify-service-by-email;spoolsv.exe: Running
Service Ok[02-22-2018 18:32:23] SERVICE ALERT: 01-Sv-10.69;Spooler;OK;HARD;1;spoolsv.exe: Running
Service Notification[02-22-2018 18:31:23] SERVICE NOTIFICATION: nagiosadmin;01-Sv-10.69;Spooler;CRITICAL;notify-service-by-email;spoolsv.exe: not running
Service Critical[02-22-2018 18:31:23] SERVICE ALERT: 01-Sv-10.69;Spooler;CRITICAL;HARD;1;spoolsv.exe: not running
Service Ok[02-22-2018 18:30:50] SERVICE ALERT: 01-Sv-10.69;Numero Procesos;OK;HARD;1;OK: Process count was 549

Hello, today I arrived at the office and the "unknown" status was reactivated on the server 10.10.10.69

another fact is that through the web interface of ncpa you can see the processes without problems, but when going to nagios is not able to show it and throws unknown

Hello, I attach other information to see the ip in the web interface of NCPA in the server that generates conflict I see another ip "10.10.10.22 and 10.10.10.100 the 10.100 corresponds to the server where nagios is, but the 10.22 is not because it appears. and in the other servers only the ip of nagios 10.10.10.100 appears



__

the ip 10.10.10.22 is the ip of the proxy server, but why does it appear in the NCPA interface?

h4doukeeN wrote:the ip 10.10.10.22 is the ip of the proxy server, but why does it appear in the NCPA interface?

Because that is what NCPA would see remotely executed checks as.

Hello, after seeing possibilities of the "unknown" state, I realized that when the processes go up from approximately 750 (between 750 or a little more) the count stops working and goes into an unknown state. How could I solve this problem?

In the server 10.71 that never goes up of the 500 processes, I have never had the problem of unknown status. in 69 and 68 especially about the 750 the problem starts


now in the server 68 with a load of processes variant between 750 and 800 I find myself with unknown status


always in the mornings when I arrive it is all well operative, but as the processes begin to go up with the use for the arrival of the workers it begins to fail and it goes to unknown status ... yesterday afternoon shortly before the departure the processes went down and the state was fine again


today in the morning it was fine until the workers started to connect and the state went to unknown



all the mentioned will have some solution with the same NCPA ?? or if you could help me with another plugin that achieves the objective of enumerating the processes and alerting in X number of processes.

Can you confirm what version of NCPA you are running? Does it show a proper value in the NCPA interface when this happens?

Also when it is in this state, can you run the command from the command line adding the --verbose flag

Thanks