Results 1 to 6 of 6
  1. #1
    Join Date
    Apr 2008

    no listening sockets available, shutting down, Unable to open logs


    We are unable to get apache working on cpanel server.

    It show this error:

    service httpd start
    no listening sockets available, shutting down
    Unable to open logs

    We check port 80 with netstat, lsof, and there are no processes using that port.
    Firewall is stoped
    Also we recompiled with easy apache, reboot the server but the error persist.
    We ran /scripts/upcp and /scripts/upcp --force but the problem persist.

    Any idea please?

    Thank you.-

  2. #2
    Join Date
    Feb 2004
    Toronto, ON, Canada
    If you telnet to port 80 what does it say ?
    VimHost█ Providing Web Hosting since 2003: 13 Years of Dedication to our customers
    Email Hosting | RTMP Hosting | FFMPEG Hosting

  3. #3
    Join Date
    Apr 2008

    telnet localhost 80
    Trying ::1...
    telnet: connect to address ::1: Connection refused
    telnet: connect to address Connection refused


  4. #4
    Join Date
    Jul 2005
    Huh... where am I again?
    Check error logs and they'll probably say could not bind to ip / port. So next you have to find what is running either by checking ps aux to see if there is a rogue httpd or check netstat -tap to see if something is bound to *:http . If you find either one, use kill to kill the process and then start http.
    Last edited by steven99; 10-01-2013 at 11:01 PM.
    -Steven | u2-web, LLC - Clustered Shared Hosting
    "It is the mark of an educated mind to be able to entertain a thought without accepting it" -Aristotle

  5. #5
    Its probably semaphores.
    Can you check the semaphore usage by executing -
    ipcs -l | grep nobody

    If you see a lot of semaphore usage, then clear the semaphore usage for nobody user by executing this command -

    for i in $(sudo ipcs -s | grep nagios | awk '{print $2}'); do sudo ipcrm sem $i; done

    then try to restart apache


    another reason can be - no permission to create or access the log files for apache.
    This is normally in the path - /usr/local/apache/logs or /etc/httpd/logs
    Make sure that those directories are there and is accessible by apache user.
    Last edited by intcom; 10-02-2013 at 04:31 AM.

  6. #6
    You may have the Listen directive in your conf files twice.

    grep -R "Listen " /path/to/apache/conf/*

    Also, check your CustomLog and ErrorLog directives - you're missing out on additional troubleshooting information either because Apache lacks permission to write logs, or it's being told to write to the wrong place.
    Last edited by NathanHawks; 10-05-2013 at 04:25 PM. Reason: Logs.

Similar Threads

  1. Unable to open logs Apache / Fedora 14
    By Jumballaya in forum Hosting Security and Technology
    Replies: 5
    Last Post: 08-28-2011, 06:08 PM
  2. Replies: 10
    Last Post: 09-17-2010, 08:12 AM
  3. allow PHP to open sockets on server. Any danger ?
    By ramystyle in forum Hosting Security and Technology
    Replies: 2
    Last Post: 11-19-2008, 02:40 PM
  4. how to limit sockets to prevent hack (logs provided)
    By kwanun88 in forum Hosting Security and Technology
    Replies: 11
    Last Post: 04-24-2008, 05:47 PM
  5. open sockets
    By DenRomano in forum Programming Discussion
    Replies: 5
    Last Post: 06-29-2005, 02:08 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts