Nagios Support Forum

Posted: **Mon May 16, 2016 12:22 pm**

I think the defunct processes are workers that timed out and are trying to shut down.
If you have some checks that are failing, fixing them would help out in this.
Let us know how it works.

Posted: **Tue May 17, 2016 6:10 am**

Unfortunately the "<defunct>" processes are no workers which timed out.

Code: Select all

root@cs-monitor-brem-t:~# ps -ef | grep nagios
  nagios 22196 22175   0        - ?           0:00 <defunct>
  nagios 22202 22175   0        - ?           0:00 <defunct>
  nagios 22181 22175   0        - ?           0:00 <defunct>
  nagios 22176 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22206 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22182 22175   0        - ?           0:00 <defunct>
  nagios 22205 22175   0        - ?           0:00 <defunct>
  nagios 22211 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22212 22175   0 12:58:43 ?           0:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg
  nagios 22201 22175   0        - ?           0:00 <defunct>
  nagios 22188 22175   0        - ?           0:00 <defunct>
  nagios 22178 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22210 22175   0        - ?           0:00 <defunct>
  nagios 22185 22175   0        - ?           0:00 <defunct>
  nagios 22183 22175   0        - ?           0:00 <defunct>
  nagios 22191 22175   0        - ?           0:00 <defunct>
  nagios 22194 22175   0        - ?           0:00 <defunct>
  nagios 22180 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22186 22175   0        - ?           0:00 <defunct>
  nagios 22203 22175   0        - ?           0:00 <defunct>
  nagios 22193 22175   0        - ?           0:00 <defunct>
  nagios 22204 22175   0        - ?           0:00 <defunct>
  nagios 22184 22175   0        - ?           0:00 <defunct>
  nagios 22209 22175   0        - ?           0:00 <defunct>
  nagios 22192 22175   0        - ?           0:00 <defunct>
  nagios 22189 22175   0        - ?           0:00 <defunct>
  nagios 22175 19328   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg
  nagios 22198 22175   0        - ?           0:00 <defunct>
  nagios 22179 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22177 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22195 22175   0        - ?           0:00 <defunct>
  nagios 22208 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22187 22175   0        - ?           0:00 <defunct>
  nagios 22207 22175   0 12:58:40 ?           0:00 /opt/nagios/bin/nagios --worker /opt/nagios/var/rw/nagios.qh
  nagios 22200 22175   0        - ?           0:00 <defunct>
  nagios 22199 22175   0        - ?           0:00 <defunct>
  nagios 22197 22175   0        - ?           0:00 <defunct>
  nagios 22190 22175   0        - ?           0:00 <defunct>

Attached is an overview of the service page. Also the log file shows no errors:

Code: Select all

[1463482719] Nagios 4.1.1 starting... (PID=22175)
[1463482719] Local time is Tue May 17 12:58:39 CEST 2016
[1463482719] LOG VERSION: 2.0
[1463482719] qh: Socket '/opt/nagios/var/rw/nagios.qh' successfully initialized
[1463482719] qh: core query handler registered
[1463482719] nerd: Channel hostchecks registered successfully
[1463482719] nerd: Channel servicechecks registered successfully
[1463482719] nerd: Channel opathchecks registered successfully
[1463482719] nerd: Fully initialized and ready to rock!
[1463482719] wproc: Successfully registered manager as @wproc with query handler
[1463482719] wproc: Registry request: name=Core Worker 22176;pid=22176
[1463482719] wproc: Registry request: name=Core Worker 22177;pid=22177
[1463482719] wproc: Registry request: name=Core Worker 22178;pid=22178
[1463482719] wproc: Registry request: name=Core Worker 22179;pid=22179
[1463482719] wproc: Registry request: name=Core Worker 22180;pid=22180
[1463482719] wproc: Registry request: name=Core Worker 22206;pid=22206
[1463482719] wproc: Registry request: name=Core Worker 22207;pid=22207
[1463482719] wproc: Registry request: name=Core Worker 22208;pid=22208
[1463482719] wproc: Registry request: name=Core Worker 22211;pid=22211
[1463482723] Successfully launched command file worker with pid 22212

Posted: **Tue May 17, 2016 10:33 am**

Ok, thanks for the output. Let us know if you have any other problems.

Posted: **Fri Jun 17, 2016 3:07 am**

I would say this topic can be marked as resolved and closed as the "<defunct>" processes don't influence the overall working of Nagios

Posted: **Fri Jun 17, 2016 10:54 am**

Thanks for reporting back, I'll close and lock up this post then.

Nagios Support Forum

Nagios 4.1.1 on Solaris 11 - Can't connect to query socket

Re: Nagios 4.1.1 on Solaris 11 - Can't connect to query sock

Re: Nagios 4.1.1 on Solaris 11 - Can't connect to query sock

Re: Nagios 4.1.1 on Solaris 11 - Can't connect to query sock

Re: Nagios 4.1.1 on Solaris 11 - Can't connect to query sock

Re: Nagios 4.1.1 on Solaris 11 - Can't connect to query sock