Bug#800087: systemd lists running daemons as failed after reboot

James Bottomley James.Bottomley at HansenPartnership.com
Sat Oct 3 18:48:24 BST 2015


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
> >   UNIT            LOAD   ACTIVE SUB    DESCRIPTION
> > ● 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



More information about the Pkg-systemd-maintainers mailing list