Bug 751591 - httpd should start up after network filesystems
Summary: httpd should start up after network filesystems
Alias: None
Product: Fedora
Classification: Fedora
Component: httpd
Version: 15
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jan Kaluža
QA Contact: Fedora Extras Quality Assurance
: 750595 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2011-11-06 01:01 UTC by Edward Z. Yang
Modified: 2012-04-01 22:56 UTC (History)
7 users (show)

Fixed In Version: httpd-2.2.22-2.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-04-01 22:56:28 UTC
Type: ---

Attachments (Terms of Use)

Description Edward Z. Yang 2011-11-06 01:01:54 UTC
In particular, if you have a non-vhosted DocumentRoot on a network filesystem like NFS or OpenAFS, if Apache starts up too early it will find out that the thing doesn't exist, and refuse to startup.

See also: https://issues.apache.org/bugzilla/show_bug.cgi?id=52139

Comment 1 Edward Z. Yang 2011-11-06 01:03:59 UTC
This is easier to do in the httpd systemd'ified world in the network filesystem packaging. In F15 you have to modify httpd.init because those knobs don't work.

See also: https://scripts.mit.edu:444/trac/ticket/247

Comment 2 Joe Orton 2011-11-07 12:31:36 UTC
Thanks for the report.

It looks like it should be sufficient to add "nfs-service.service" to the After: line for httpd.service, w.r.t. NFS, have you tested that?  What's the name of the OpenAFS service, I don't think that's in Fedora?

Comment 3 Edward Z. Yang 2011-11-07 17:25:17 UTC

Alternatively, you can add Before and WantedBy to NFS's systemd package. It depends on which package you think should manage the dependency.

OpenAFS is not in Fedora, so we have to do it this way.

Comment 4 Joe Orton 2011-11-10 01:24:52 UTC
*** Bug 750595 has been marked as a duplicate of this bug. ***

Comment 5 edwinh 2011-11-16 19:56:58 UTC
I don't see nfs-service.service

Isn't the right thing "After=remote-fs.target" just like user sessions?

Comment 6 Edward Z. Yang 2011-11-18 00:47:11 UTC
Oh, I didn't actually check what NFS's systemd name is. I'm not sure which of these service files corresponds to the client: http://koji.fedoraproject.org/koji/rpminfo?rpmID=2754200

Comment 7 Elliott Forney 2011-11-18 22:18:46 UTC
netfs.service is the NFS client service.  It sounds to me like remote-fs.target is what we want... although I'm not certain.

The problem is that netfs and httpd are both legacy /etc/init.d scripts in Fedora 15.  How do you tell httpd.service to start after remote-fs.target or netfs.service when there is no unit file in /lib/systemd/system?

Let me know if anyone would like me to test potential solutions, we have a machine that is affected by this.

Comment 8 Edward Z. Yang 2011-11-18 22:25:16 UTC
As I mentioned earlier, in F15, pre-systemd world, you need to edit the .init script; they have a special INIT INFO stanza, and you can modify 'Required-Start' in httpd.init to depend on all of the things you may need.

But this isn't so good for the general Fedora environment, because Apache really shouldn't have to know about NFS. Things get better post systemd, so it might be more reasonable just to WONTFIX this for F15.

Comment 9 Elliott Forney 2011-11-18 23:11:11 UTC
Sorry, I didn't see your earlier post.  I guess the mix of systems is what confuses me.  I believe this worked fine in Fedora 14... does it work in Fedora 16?  I presume these are all systemified in Fedora 16?

I respectfully disagree that this should be closed as WONTFIX.  Your argument is equivalent to saying "apache shouldn't have to know about ext4 so it is OK to start it before ext4 filesystems are mounted."  Apache should not be started until ALL filesystems are mounted/mountable.  Otherwise, it should block until they are.  Either way something needs to change.

Comment 10 Elliott Forney 2011-11-18 23:24:29 UTC
My /etc/init.d/httpd already has the following in it:

# Required-Start: $local_fs $remote_fs $network $named

Are you sure systemd honors these?

Comment 11 Edward Z. Yang 2011-11-20 20:43:16 UTC
The problem is that NFS doesn't register itself as a remote_fs. So these don't work. I don't know how to do this using SysV stanzas; if we can find a way to do that, that would be ideal.

Note we can do this for later versions of Fedora, so adding a remote_fs.target dependency is the right way to go.

Comment 12 Edward Z. Yang 2011-11-22 02:28:03 UTC
It looks like NFS in Fedora 17 doesn't register itself as a remote_fs either. Oops!

Comment 13 Edward Z. Yang 2011-11-24 01:33:26 UTC
We tested, and adding remote-fs.target to WantedBy in the Install does the right thing for ~all applications, including SysV scripts. We should do this for all versions of Fedora.

Comment 14 Jan Kaluža 2011-11-29 10:22:16 UTC
Ok, I can't say I fully understood the WantedBy documentation, but it looks to me that with WantedBy=remote-fs.target, you can't run httpd without having remote-fs.target disabled. Even when you have remote-fs.target disabled, it gets enabled because httpd would need it.

I'm not sure if this dependency is valid or not. I checked how other services do it, and it looks they simply define this:

After= .... remote-fs.target

Does it still work properly if you add remote-fs.target into After: definition?

Comment 15 edwinh 2011-11-29 13:11:06 UTC
Yes.  My httpd startup problem in F16 (with nfs+autofs documentroot) is fixed by adding

in the httpd service file.  

In fact I used this for a few other things  with same systemd kind of bug (mythtv, mrtg, ...)

Comment 16 Edward Z. Yang 2011-11-29 16:26:28 UTC
I pinged systemd-devel on this issue. I think the semantics are slightly different depending on whether something is a target or a service.

Comment 17 Jan Kaluža 2011-12-06 07:40:13 UTC
If I understood the systemd-devel thread, we should probably use After. I will commit it to rawhide, so it should be added into F16 on next update.

Comment 18 Rudd-O DragonFear 2011-12-30 11:03:21 UTC
What you want is After, such that httpd starts after remote-fs.target whether remote-fs.target is enabled or not.

Comment 19 Norman Gaywood 2012-01-17 02:00:00 UTC
This is still an issue for me in F16.


There is no update in updates-testing.

Comment 20 Fedora Update System 2012-03-05 11:44:42 UTC
httpd-2.2.22-2.fc16 has been submitted as an update for Fedora 16.

Comment 21 Fedora Update System 2012-03-06 19:25:34 UTC
Package httpd-2.2.22-2.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing httpd-2.2.22-2.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 22 Fedora Update System 2012-04-01 22:56:28 UTC
httpd-2.2.22-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.