Description of problem: When hhtpd is started via systemd it dies with the following showing up in the error_log: [Wed Apr 15 16:48:58.903019 2015] [mpm_prefork:notice] [pid 5357] AH00170: caught SIGWINCH, shutting down gracefully I don't see why a window size change shuold trigger a shutdown. This doesn't happen when I run httpd directly as root in a terminal window. Version-Release number of selected component (if applicable): httpd-2.4.12-1.fc23.i686
I need to clarify my last comment. When I just run httpd from the command line and let it detach from the terminal, it runs normally. When I run httpd -DFOREGROUND, then it will stop after I change the terminal window size.
By starting httpd via systemd, you mean "systemctl start httpd"?
http is failing to start both at initial boot and when I manually to to start it using "systemctl restart httpd".
per https://bz.apache.org/bugzilla/show_bug.cgi?id=50669 , Apache uses the SIGWINCH kill signal as a 'graceful shutdown' trigger. Note that Apache's systemd service actually *uses* this - see from httpd.service: # Send SIGWINCH for graceful stop KillSignal=SIGWINCH KillMode=mixed so I suspect what's happening here is not that the SIGWINCH signal is some sort of stray or mistake, but that what you're seeing is systemd doing an orderly, intentional stopping of the service. In other words, the question isn't 'why does httpd shut down on a SIGWINCH?' or 'why does systemd send httpd a SIGWINCH?' but 'why does systemd want to stop the service right after it's started?' A full log would help us tell for sure.
In https://bz.apache.org/bugzilla/show_bug.cgi?id=50669 a change request to ignore SIGWINCH is closed won't fix. SIGWINCH might be used for doing clean shutdowns of httpd. So there might be a systemd bug or maybe some unexpected configuration is triggering systemd to do a shutdown right away.
Created attachment 1044408 [details] Out from a restart attempt
Well, this looks like the problem to me: Jun 29 10:36:39 bruno.wolff.to systemd[1]: httpd.service: Start operation timed out. Terminating. basically, systemd doesn't believe httpd has fully started up; it waits a minute and half for the start operation to complete, then times out. When it hits the time out it stops the unit - that's where the SIGWINCH comes from, it is (as I suspected) systemd shutting down the unit on purpose. So what we need to figure out is why systemd decides httpd hasn't fully started. Do you have any server certificates which require password entry?
/lib/systemd/system/httpd.service hasn't changed between f22 and f23. And things work on f22.
Sure, but clearly something different is happening in terms of Apache itself. there may be some clues in the Apache logs (/var/log/httpd ).
No, no certs requiring a pass phrase. It doesn't take a minute and a half to background when I run it from the terminal. Perhaps I should see if selinux is blocking something? Also there may be other log info that I can find.
Nothing obvious in the error_log, but it does have a 1.5 minute gap from when it starts to when the timeout is enforced. [Mon Jun 29 10:51:27.485386 2015] [core:notice] [pid 26051] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0 [Mon Jun 29 10:51:27.488054 2015] [suexec:notice] [pid 26051] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Mon Jun 29 10:51:27.511507 2015] [auth_digest:notice] [pid 26051] AH01757: generating secret for digest authentication ... [Mon Jun 29 10:51:27.523004 2015] [mpm_prefork:notice] [pid 26051] AH00163: Apache/2.4.12 (Fedora) configured -- resuming normal operations [Mon Jun 29 10:51:27.523196 2015] [core:notice] [pid 26051] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND' [Mon Jun 29 10:52:57.416631 2015] [mpm_prefork:notice] [pid 26051] AH00170: caught SIGWINCH, shutting down gracefully
Created attachment 1044409 [details] Sample working start up from f22, but config is different The config is different. So they may not be directly comparable.
This is what I get when I just start it from the command line: [Mon Jun 29 11:04:16.827213 2015] [core:notice] [pid 29933] SELinux policy enabled; httpd running as context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 [Mon Jun 29 11:04:16.831342 2015] [suexec:notice] [pid 29933] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Mon Jun 29 11:04:16.859943 2015] [auth_digest:notice] [pid 29934] AH01757: generating secret for digest authentication ... [Mon Jun 29 11:04:16.873835 2015] [mpm_prefork:notice] [pid 29934] AH00163: Apache/2.4.12 (Fedora) configured -- resuming normal operations [Mon Jun 29 11:04:16.874094 2015] [core:notice] [pid 29934] AH00094: Command line: 'httpd'
-DFOREGROUND doesn't seem to cause a problem with startup when running from a terminal.
I have found this is configuration dependent. I'll report back the specifics when I narrow this down and will probably close it at that time.
It looks like you need to run 00-systemd.conf if you want systemd to recognize that httpd has started successfully.
*** Bug 2073286 has been marked as a duplicate of this bug. ***