Page 1 of 1

httpd shuts down with SIGWINCH

Posted: Mon Jan 06, 2020 11:05 am
by nicholashadaway
My httpd service keeps shutting down randomly. Please see the output of access and error logs for httpd below.
This is a fresh installation of nagios network analyzer. No customizations, just a stock install.

[root@monp0013 ~]# tail -f /var/log/httpd/*_log
==> /var/log/httpd/access_log <==
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "POST /nagiosna/api/views/get_views HTTP/1.1" 200 2 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "POST /nagiosna/api/reports/read HTTP/1.1" 200 189 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "POST /nagiosna/api/views/get_views HTTP/1.1" 200 2 "http://monp0013.pr.mgicint.net/nagiosna ... /queries/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "POST /nagiosna/api/system/source_status HTTP/1.1" 200 170 "http://monp0013.pr.mgicint.net/nagiosna ... /queries/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "POST /nagiosna/api/reports/read HTTP/1.1" 200 189 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "POST /nagiosna/api/reports/execute HTTP/1.1" 200 48 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "POST /nagiosna/reports/reportviz HTTP/1.1" 200 11666 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "GET /nagiosna/api/graphs/queryviz?sid=2&agg1=srcip&sortby=bytes&q[begindate]=-24%20hours&q[rawquery]=&token=fcae249cac95bfe4bebedbaa18e8c2b034810d35&agg2=dstport HTTP/1.1" 200 65 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "GET /nagiosna/api/graphs/queryviz?sid=2&agg1=srcip&sortby=bytes&q[begindate]=-24%20hours&q[rawquery]=&token=fcae249cac95bfe4bebedbaa18e8c2b034810d35&agg2=srcport HTTP/1.1" 200 65 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"
172.22.80.227 - - [06/Jan/2020:10:00:13 -0600] "GET /nagiosna/api/graphs/queryviz?sid=2&agg1=srcip&sortby=bytes&q[begindate]=-24%20hours&q[rawquery]=&token=fcae249cac95bfe4bebedbaa18e8c2b034810d35&agg2=dstip HTTP/1.1" 200 65 "http://monp0013.pr.mgicint.net/nagiosna ... /reports/2" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0"

==> /var/log/httpd/error_log <==
[Mon Jan 06 08:49:33.547975 2020] [core:notice] [pid 89033] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
FirewallD is not running
FirewallD is not running
[Mon Jan 06 09:03:02.668884 2020] [mpm_prefork:notice] [pid 89033] AH00170: caught SIGWINCH, shutting down gracefully
[Mon Jan 06 09:42:29.681260 2020] [suexec:notice] [pid 95287] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Jan 06 09:42:29.726575 2020] [lbmethod_heartbeat:notice] [pid 95287] AH02282: No slotmem from mod_heartmonitor
[Mon Jan 06 09:42:29.785902 2020] [mpm_prefork:notice] [pid 95287] AH00163: Apache/2.4.6 (Red Hat Enterprise Linux) PHP/5.4.16 configured -- resuming normal operations
[Mon Jan 06 09:42:29.785947 2020] [core:notice] [pid 95287] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
FirewallD is not running
FirewallD is not running
[Mon Jan 06 10:02:53.659301 2020] [mpm_prefork:notice] [pid 95287] AH00170: caught SIGWINCH, shutting down gracefully

Re: httpd shuts down with SIGWINCH

Posted: Mon Jan 06, 2020 11:07 am
by nicholashadaway
[root@monp0013 conf.d]# systemctl status nagiosna
● nagiosna.service - NagiosNA Daemon
Loaded: loaded (/usr/lib/systemd/system/nagiosna.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Mon 2020-01-06 10:06:29 CST; 1s ago
Process: 98329 ExecStop=/etc/rc.d/init.d/nagiosna stop (code=exited, status=0/SUCCESS)
Process: 98310 ExecStart=/etc/rc.d/init.d/nagiosna start (code=exited, status=0/SUCCESS)
Main PID: 98327 (code=exited, status=0/SUCCESS)

Jan 06 10:06:29 monp0013 nfcapd[98328]: Total ignored packets: 0
Jan 06 10:06:29 monp0013 nfcapd[98328]: Signal launcher[98330] to terminate.
Jan 06 10:06:29 monp0013 nfcapd[98330]: Launcher: fork child.
Jan 06 10:06:29 monp0013 nagiosna[98329]: NagiosNA backend stopped.
Jan 06 10:06:29 monp0013 nfcapd[98330]: Launcher: child exec done.
Jan 06 10:06:29 monp0013 nfcapd[98330]: Run expire on '/usr/local/nagiosna/var/rdcmx2/flows'
Jan 06 10:06:29 monp0013 nfcapd[98330]: Limits: Filesize <none>, Lifetime 86400 = 1.0 days, Watermark: 95%
Jan 06 10:06:29 monp0013 nfcapd[98330]: Current size: 65536 = 64.0 KB, Current lifetime: 4800 = 1.3 hours, Number of files: 16
Jan 06 10:06:29 monp0013 nfcapd[98330]: expire completed - nothing to expire.
Jan 06 10:06:29 monp0013 nfcapd[98330]: Launcher: Terminating.

Re: httpd shuts down with SIGWINCH

Posted: Mon Jan 06, 2020 2:30 pm
by mbellerue
Can you send me a copy of your /var/log/messages or /var/log/syslog file?

Also, is this a Linux machine that you spun up and then installed Network Analyzer, or is this one of our virtual machine images?

Re: httpd shuts down with SIGWINCH

Posted: Thu Jan 09, 2020 12:03 pm
by nicholashadaway
Please go ahead and close this issue. It appears that there was an automation process that would shut down httpd from my side. I'd say delete this post even as it may be confusing.

Re: httpd shuts down with SIGWINCH

Posted: Thu Jan 09, 2020 12:08 pm
by mbellerue
Okay, thank you for posting the root issue back here. It can be helpful to people down the road if, in the process of troubleshooting, they forget about automated processes on the server. That's got to be a pretty common issue with automation. Set it and forget it.