On Mon, Jan 3, 2011 at 08:53, Paul F. Johnson <paul@all-the-johnsons.co.uk> wrote:
 

First is httpd (apache).

I can do /etc/init.d/httpd stop and the server stops, but when I try to
start the server I get

Starting httpd (via systemctl):  Job failed. See system logs and
'systemctl status' for details.

systemctl status httpd.service shows

httpd.service - LSB: start and stop Apache HTTP Server
         Loaded: loaded (/etc/rc.d/init.d/httpd)
         Active: failed since Mon, 03 Jan 2011 16:39:18 +0000; 33s ago
        Process: 3902 (/etc/rc.d/init.d/httpd stop, code=exited,
status=0/SUCCESS)
        Process: 1959 (/etc/rc.d/init.d/httpd start, code=exited,
status=1/FAILURE)
       Main PID: 2054 (code=exited, status=1/FAILURE)
         CGroup: name=systemd:/system/httpd.service
                 └ 2086 /usr/sbin/httpd

cat /var/log/messages | tail is also unhelpful

Jan  3 16:41:34 PB3 systemd[1]: httpd.service: control process exited,
code=exited status=1
Jan  3 16:41:34 PB3 systemd[1]: Unit httpd.service entered failed state.


The stop command leaves one httpd process running. Kill it off first.

httpd fails to start because it is trying to create a file in /var/run/httpd but the directory doesn't exist.

As a temporary workaround I've been

1) stop httpd
2) kill the last remaining httpd
3) create /var/run/httpd
4) start http

There is a outstanding bug that Lennart created. I also expect that the script will be converted sometime to work natively with systemd.

darrell