Bug#800087: closed by Michael Biebl (Re: Bug#800087: systemd lists running daemons as failed after reboot)
Am 05.10.2015 um 10:41 schrieb Michael Biebl: > Am 05.10.2015 um 01:48 schrieb James Bottomley: >> On Sun, 2015-10-04 at 23:06 +, Debian Bug Tracking System wrote: >>> Well, this is apparently an apache configuration problem, causing the >>> service to return a non-zero exit code. >>> >>> Once you fix that, the service should not be marked as failed. >> >> That's pretty obviously an incorrect deduction, isn't it? If it were a >> config file problem leading to the control process erroring out then the >> manual systemctl start apache would also fail; but, as you can see from >> the description in the original report, it doesn't. > > You might need to have give apache more time to start up. Maybe 20 secs > is not enough since during boot there is a lot of other I/O going on and > the apache control process kills itself prematurely: > let me rephrase that: try to find out why apache does not start up properly within 20 secs (e.g. due to missing ressources) and then fix that or increase the limit. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#800087: closed by Michael Biebl (Re: Bug#800087: systemd lists running daemons as failed after reboot)
Am 05.10.2015 um 01:48 schrieb James Bottomley: > On Sun, 2015-10-04 at 23:06 +, Debian Bug Tracking System wrote: >> Well, this is apparently an apache configuration problem, causing the >> service to return a non-zero exit code. >> >> Once you fix that, the service should not be marked as failed. > > That's pretty obviously an incorrect deduction, isn't it? If it were a > config file problem leading to the control process erroring out then the > manual systemctl start apache would also fail; but, as you can see from > the description in the original report, it doesn't. You might need to have give apache more time to start up. Maybe 20 secs is not enough since during boot there is a lot of other I/O going on and the apache control process kills itself prematurely: > Oct 03 10:45:06 bedivere apache2[693]: Starting web server: apache2AH00180: > WARNING: MaxRequestWorkers of 20 exceeds ServerLimit value of > Oct 03 10:45:06 bedivere apache2[693]: 5 servers, decreasing > MaxRequestWorkers to 5. > Oct 03 10:45:06 bedivere apache2[693]: To increase, please see the > ServerLimit directive. > Oct 03 10:45:42 bedivere apache2[693]: failed! > Oct 03 10:45:42 bedivere apache2[693]: The apache2 instance did not start > within 20 seconds. Please read the log files to discover problems ... > (warning). > Oct 03 10:45:42 bedivere systemd[1]: apache2.service: Control process exited, > code=exited status=1 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#800087: closed by Michael Biebl (Re: Bug#800087: systemd lists running daemons as failed after reboot)
On Sun, 2015-10-04 at 23:06 +, Debian Bug Tracking System wrote: > Well, this is apparently an apache configuration problem, causing the > service to return a non-zero exit code. > > Once you fix that, the service should not be marked as failed. That's pretty obviously an incorrect deduction, isn't it? If it were a config file problem leading to the control process erroring out then the manual systemctl start apache would also fail; but, as you can see from the description in the original report, it doesn't. The logs have this in them: [ 2015-10-03 10:41:55.6129 1309/b5cfeb40 age/Hel/Main.cpp:455 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown) [ 2015-10-03 10:41:55.6160 1319/b6960b40 age/Log/Main.cpp:349 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown) [ 2015-10-03 10:45:21.1489 1353/b5dfeb40 age/Hel/Main.cpp:455 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown) [ 2015-10-03 10:45:21.1521 1374/b68fab40 age/Log/Main.cpp:349 ]: Signal received. Gracefully shutting down... (send signal 2 more time(s) to force shutdown) So apache dies because something external kills it during boot up. Hm, I wonder what that could be ... James
Bug#800087: systemd lists running daemons as failed after reboot
On Wed, 2015-09-30 at 15:20 +0200, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Am 26.09.2015 um 18:08 schrieb James Bottomley: > > Package: systemd > > Version: 226-3 > > Severity: normal > > > > rebooting the current system often causes listed init system failures. > > in addition to failing to start spamd (listed under separate bug). > > Systemd thinks units have failed when, in fact, they're running. The > > most common units for this are apache2 and mysql. > > > > This is the state of a recent reboot, where apache2 is listed as failed > > > > bedivere:~# systemctl --failed > > UNITLOAD ACTIVE SUBDESCRIPTION > > ● apache2.service loaded failed failed LSB: Apache2 web server > > > > LOAD = Reflects whether the unit definition was properly loaded. > > ACTIVE = The high-level unit activation state, i.e. generalization of SUB. > > SUB= The low-level unit activation state, values depend on unit type. > > > > 1 loaded units listed. Pass --all to see loaded but inactive units, too. > > To show all installed unit files use 'systemctl list-unit-files'. > > > > Whereas ps shows it to be running > > What's the output of > systemctl status apache2.service ? OK, so the machine only has a maintenance window on saturday. I rebooted and asked this and this is the result: bedivere:~# systemctl status -l apache2.service ● apache2.service - LSB: Apache2 web server Loaded: loaded (/etc/init.d/apache2) Active: failed (Result: exit-code) since Sat 2015-10-03 10:45:42 PDT; 1min 53s ago Docs: man:systemd-sysv-generator(8) Process: 693 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE) CGroup: /system.slice/apache2.service ├─1407 /usr/sbin/apache2 -k start ├─1410 PassengerAgent watchdog ├─1417 PassengerAgent server ├─1422 PassengerAgent logger ├─1699 /usr/sbin/apache2 -k start ├─1701 /usr/sbin/apache2 -k start ├─1702 /usr/sbin/apache2 -k start ├─1704 /usr/sbin/apache2 -k start └─1706 /usr/sbin/apache2 -k start Oct 03 10:44:38 bedivere systemd[1]: Starting LSB: Apache2 web server... Oct 03 10:45:06 bedivere apache2[693]: Starting web server: apache2AH00180: WARNING: MaxRequestWorkers of 20 exceeds ServerLimit value of Oct 03 10:45:06 bedivere apache2[693]: 5 servers, decreasing MaxRequestWorkers to 5. Oct 03 10:45:06 bedivere apache2[693]: To increase, please see the ServerLimit directive. Oct 03 10:45:42 bedivere apache2[693]: failed! Oct 03 10:45:42 bedivere apache2[693]: The apache2 instance did not start within 20 seconds. Please read the log files to discover problems ... (warning). Oct 03 10:45:42 bedivere systemd[1]: apache2.service: Control process exited, code=exited status=1 Oct 03 10:45:42 bedivere systemd[1]: Failed to start LSB: Apache2 web server. Oct 03 10:45:42 bedivere systemd[1]: apache2.service: Unit entered failed state. Oct 03 10:45:42 bedivere systemd[1]: apache2.service: Failed with result 'exit-code'. James
Bug#800087: systemd lists running daemons as failed after reboot
Control: tags -1 + moreinfo Am 26.09.2015 um 18:08 schrieb James Bottomley: > Package: systemd > Version: 226-3 > Severity: normal > > rebooting the current system often causes listed init system failures. > in addition to failing to start spamd (listed under separate bug). > Systemd thinks units have failed when, in fact, they're running. The > most common units for this are apache2 and mysql. > > This is the state of a recent reboot, where apache2 is listed as failed > > bedivere:~# systemctl --failed > UNITLOAD ACTIVE SUBDESCRIPTION > ● apache2.service loaded failed failed LSB: Apache2 web server > > LOAD = Reflects whether the unit definition was properly loaded. > ACTIVE = The high-level unit activation state, i.e. generalization of SUB. > SUB= The low-level unit activation state, values depend on unit type. > > 1 loaded units listed. Pass --all to see loaded but inactive units, too. > To show all installed unit files use 'systemctl list-unit-files'. > > Whereas ps shows it to be running What's the output of systemctl status apache2.service ? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
