Help debugging HTTPD Error - dead but subsys locked

Discussion in 'Apache' started by seismicmike, Jul 19, 2010.

  1. #1
    I could use some help debugging a weird error in Apache HTTPD server

    
    # httpd -v
    Server version: Apache/2.2.14 (Unix)
    Server built:   Mar 17 2010 17:26:13
    
    Code (markup):
    The problem I'm having is that httpd won't stop/restart without throwing an error. I don't why. When the server is running it's "working" properly - IE sites are loading but whenever I try to restart HTTPD due to a vhost change or log rotation or something like that, I get errors. I think the root cause has to do with the following. When the server is loading sites properly and I query the status of httpd, here's what I get:

    
    # sudo service httpd status
    httpd dead but subsys locked
    
    Code (markup):
    So here's a synopsis of what happens when I try to restart.
    
    # sudo service httpd stop
    Stopping https:                                            [FAILED]
    # sudo service httpd status
    httpd is stopped
    # sudo service httpd start
    Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
    (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
    no listening sockets available, shutting down
    Unable to open logs
                                                               [FAILED]
    # netstat -nltp | grep ':80'
    tcp        0      0 :::80                       :::*                        LISTEN      5133/httpd  
    # sudo kill 5133
    # sudo service httpd start
    Starting httpd:                                            [  OK  ]
    # sudo service httpd status
    httpd dead but subsys locked
    
    Code (markup):
    What could cause the dead but subsys locked error? What could cause the error on restart? I assume the same thing is causing both.

    Any help is greatly appreciated. Thanks.
     
    seismicmike, Jul 19, 2010 IP
  2. seismicmike

    seismicmike Peon

    Messages:
    63
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    Nevermind, I fixed my own problem with a little research. I had a problem with mod_ssl... I did a reinstall and it works now.
     
    seismicmike, Jul 19, 2010 IP