"service stop; service start" fails with wsgi.py from freeipa-server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
If apache is running, doing 'systemctl stop apache2.service; systemctl start apache2.service' fails with:
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.
Active: failed (Result: exit-code) since to 2015-03-05 20:33:16 EET; 6s ago
Docs: man:systemd-
Process: 27891 ExecStop=
Process: 27943 ExecStart=
maalis 05 20:32:56 ipa02.tyrell apache2[27943]: no listening sockets available, shutting down
maalis 05 20:32:56 ipa02.tyrell apache2[27943]: AH00015: Unable to open logs
maalis 05 20:32:56 ipa02.tyrell apache2[27943]: Action 'start' failed.
maalis 05 20:32:56 ipa02.tyrell apache2[27943]: The Apache error log may have more information.
maalis 05 20:33:16 ipa02.tyrell systemd[1]: apache2.service: control process exited, code=exited status=1
maalis 05 20:33:16 ipa02.tyrell systemd[1]: Failed to start LSB: Apache2 web server.
maalis 05 20:33:16 ipa02.tyrell systemd[1]: Unit apache2.service entered failed state.
maalis 05 20:33:16 ipa02.tyrell systemd[1]: apache2.service failed.
maalis 05 20:33:16 ipa02.tyrell apache2[27943]: *
maalis 05 20:33:16 ipa02.tyrell apache2[27943]: * The apache2 instance did not start within 20 seconds. Please read the log files to discover problems
error.log doesn't have more than this:
[Thu Mar 05 20:32:56.258403 2015] [mpm_event:notice] [pid 27786:tid 139760377153408] AH00491: caught SIGTERM, shutting down
so stopping the service returns too quickly and start gets run too early?
summary: |
- "service stop; service start" fails with systemd + "service stop; service start" fails with wsgi.py from freeipa-server |
tags: | removed: systemd-boot |
this works with upstart and IIRC sysv (debian)