Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31651 - [systemd] Unable to start the Apache's daemon after upgrade to version 191-1

Attached to Project: Arch Linux
Opened by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 20:04 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 24 December 2013, 21:07 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
I use systemd as my init daemon. After upgrade systemd from version 189-4 to version 191-1, the Apache daemon fails to start.

Downgrading systemd back to version 189-4 let the daemon starts normally again.

Additional info:
* package version(s)
- systemd 191-1
- apache 2.2.23-1

* config and/or log files etc.
- None

Steps to reproduce:
1. Upgrade systemd to version 191-1
2. Try starting the Apache daemon/service.
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 24 December 2013, 21:07 GMT
Reason for closing:  None
Additional comments about closing:  Not a systemd bug. Apache's unit file needs fixing if this still "doesn't work".
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 20:08 GMT
The error message I got is:

Sep 23 02:44:54 Atlas systemd[1]: PID file /run/httpd/httpd.pid not readable (yet?) after start.
Sep 23 02:44:54 Atlas systemd[1]: Failed to start Apache Web Server.
Sep 23 02:44:54 Atlas systemd[1]: Unit httpd.service entered failed state.
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 20:25 GMT
I have attached the relevant section from journalctl -o verbose
   snipped_journal_verbose_log (0.8 KiB)
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 20:39 GMT
Today's everything.log file.
   everything.log (629.6 KiB)
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 20:48 GMT
Full journal export.
   journal_export (722.8 KiB)
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 21:13 GMT
Full journal log with debug log level.
   journal_debug_log (1.3 MiB)
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 21:32 GMT
Full everything.log with debug log level.
   everything.log (368 KiB)
Comment by Smith Dhumbumroong (zodmaner) - Saturday, 22 September 2012, 21:45 GMT
Only section related to httpd.service.
   journal_debug_log_default (2.8 KiB)
Comment by Tom Gundersen (tomegun) - Monday, 01 October 2012, 14:38 GMT
Could you try adding RemainAfterExit=true to the service file? It might be that the service forks too early, before the pid file is created. Systemd will then consider it stopped, and will kill all remaining processes.
Comment by Harley Laue (losinggeneration) - Friday, 04 January 2013, 09:40 GMT
  • Field changed: Percent Complete (100% → 0%)
I get the same error.
RemainAfterExit=true
partially fixes the issue, but causes the same issue for systemctl restart httpd
Comment by Simon Wilper (sxw) - Tuesday, 20 August 2013, 10:58 GMT
Now with version 204-3 of systemd I get other symptoms:

systemctl start httpd hangs for a couple of minutes and the process "/usr/bin/systemd-tty-ask-password-agent --watch" waits for a password.

Since I did not configure SSL with a passworded certificate and apachectl start/stop/restart works fine I don't know why systemctl spawns ask-password.

Do I need to disable this somewhere?

Loading...