Apache Fails at Boot

[lucid]

This happened absolutely randomly. I've already asked my Infinity buddies but they are busy as am I and I don't want to give them other shit to think about. So here's the problem.

When I startup I see a error message saying Apache failed to start.

Code: [Select]

      Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
      Active: failed (Result: exit-code) since Tue 2013-02-05 11:09:11 UTC; 4h 6min ago
     Process: 402 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

Not really sure exactly what to do there. So I checked the logs at /var/log/httpd/error_logs and this is what I get:

Code: [Select]

[Mon Feb 04 17:16:17 2013] [notice] caught SIGWINCH, shutting down gracefully
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
[Mon Feb 04 17:16:17 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)

Which...also doesn't really let me know what I can do about it. Anyone got any ideas? I've tried reinstalling and I also cleared the logs(somehow fixed it for one boot). Otherwise every time I try to connect firefox just gives me this:

Unable to connect
_____________________________________________________________________
     Firefox can't establish a connection to the server at localhost.

[proxx]

Alright how about starting it manually with some more verbosity?

[techb]

Verbose would help. Other than than nothing really to work on. Are you doing manual installs or going with LAMP?

[lucid]

I'm working with LAMP. Plus I noticed that after the system is started running:

systemctl stop httpd.service
systemctl start httpd.service

Works. So it works fine if I start it manually, but allowing systemd to start it during boot doesn't seem to want to work. I wouldn't call it a fix but at least there's something. Maybe it's a bug?

[techb]

I'm working with LAMP. Plus I noticed that after the system is started running:

systemctl stop httpd.service
systemctl start httpd.service

Works. So it works fine if I start it manually, but allowing systemd to start it during boot doesn't seem to want to work. I wouldn't call it a fix but at least there's something. Maybe it's a bug?

Since systemctl is so FUCKING new with little docs, I would say it's a bug. Not many people want to run apache with Arch.

[lucid]

 

Eh well at least I found a half-fix.

[techb]

 

Eh well at least I found a half-fix.

Half-fix maybe, at least it works. I would suggets going to Arch forums or Apache forums. There may be a bug submission in order. Or maybe there is any eaiser fix, idk.

[fluxdaemon]

You could always run nginx instead
I haven't had any problems with it in Arch

[proxx]

I have a feeling it has to do with run levels.
You can start it as SU right?
Is there any additional information in your bootlog ?

[lucid]

No actually there isn't anything of any use it seems. Btw today when I turned on my compter Apache started fine. It just randomly fails every other time or something. I have no idea why at this point.

[proxx]

*The burden of a bleeding edge lover*

[lucid]

Word