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#34361 - [apache] default config file points to nonexistant tmpfs dir

Attached to Project: Arch Linux
Opened by Tim (tajudd) - Monday, 18 March 2013, 18:44 GMT
Last edited by Jan de Groot (JGC) - Monday, 18 March 2013, 20:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
/etc/httpd/conf/httpd.conf directive Scriptsock (to /var/run/httpd) and systemd's httpd.service directive PIDFile (to /run/httpd) points to nonexistant dir /run/httpd (which is a tmpfs) and since tmpfs won't have the previous dir structure, apache fails to start. Adding a systemd.service ExecStartPre to create this missing directory /run/httpd can fix the issue, or readdress the lacking dir.

Additional info:
* package version(s) 2.2.23-1
* config and/or log files etc.
default httpd.conf and systemd's httpd.service files - not attached

Steps to reproduce:
Install apache after this news article here (dated 2012-06-07)
https://www.archlinux.org/news/filesystem-upgrade-manual-intervention-required-1/
attempt to start apache without modifying PID file
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 18 March 2013, 20:17 GMT
Reason for closing:  Fixed
Comment by Daniel Wallace (gtmanfred) - Monday, 18 March 2013, 18:52 GMT
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/apache.tmpfiles.conf?h=packages/apache

it is made by the tmpfile.d file
Comment by Tim (tajudd) - Monday, 18 March 2013, 18:57 GMT
I'm afraid I don't understand the relavance of tmpfile.d; if /run is a tmpfs, /run/httpd will not be there when the system is restarted. Can you please advise on how tmpfile.d is to resolve this issue? Please further elaborate on how to use tmpfile.d so I don't keep bugging you. apache's package list doesn't create /run/httpd. When is /run/httpd supposed to be created the first time?
Comment by Daniel Wallace (gtmanfred) - Monday, 18 March 2013, 19:09 GMT
systemd-tmpfiles --create /usr/lib/tmpfiles.d/apache.conf
Comment by Jan de Groot (JGC) - Monday, 18 March 2013, 19:14 GMT
systemd-tmpfiles is called by either systemd or initscripts on bootup (and apache's post_install/upgrade call it). This creates the /run/httpd directory. Did you actually test this before reporting?
Comment by Tim (tajudd) - Monday, 18 March 2013, 19:18 GMT
I'm still learning systemd; and during the same running boot of arch, installing Apache and trying to start Apache did not create /run/httpd - hence the report. I was unaware of tmpfiles.d and it didn't seem to call it during Apache install. How can I test it farther? I had done this install by running 'pacman -S php-apache' which pulled in php, the mod for apache, and apache itself. How can I qualify this bug report, since programatically it seems to have worked, but I didn't have success.
Comment by Jan de Groot (JGC) - Monday, 18 March 2013, 19:24 GMT
You're reporting against an outdated version of apache anyways, I updated apache to 2.2.24 today and fixed the calls in post_install/post_upgrade today which fixed a duplicate of this bugreport.
Comment by Tim (tajudd) - Monday, 18 March 2013, 19:27 GMT
Oh darn, I had just installed this yesterday, and hadn't begun working on it. I will do another VM and report.
Comment by Tim (tajudd) - Monday, 18 March 2013, 19:52 GMT
did a sys upgrade, reboot, then installed apache (v2.2.24-1)
/run/httpd appeared after installing. Please close this report.

Loading...