The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

frequently (no listening sockets available, shutting down)

Discussion in 'General Discussion' started by konrath, Oct 8, 2009.

  1. konrath

    konrath Well-Known Member

    Joined:
    May 3, 2005
    Messages:
    367
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Brasil
    Hello

    Frequently apache stops working.

    When I try to run
    ----------------------------
    /scrirpts/restartsrv httpd

    [Thu Oct 08 08:09:14 2009] [warn] NameVirtualHost 74.52.130.124:80 has no VirtualHosts
    (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
    no listening sockets available, shutting down
    ----------------------------

    Then I run

    killall -9 exim
    or
    killall -9 jvsc

    and the apache return the work with /scrirpts/restartsrv httpd

    Any suggestions?

    Thank you
    Konrath
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    What is your full cPanel/WHM version information?
     
  3. konrath

    konrath Well-Known Member

    Joined:
    May 3, 2005
    Messages:
    367
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Brasil
    cPanel 11.24.5-S38506 - WHM 11.24.2 - X 3.9
    REDHAT Enterprise 4 i686 standard on server
    HomeNewsChange Log InsecureLogout (root)Load Averages: 2.01 1.89 1.91

    Thank you
    Konrath
     
  4. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    I know a while back, this was a common issue, but that was a while ago and fixed relatively swiftly. Since you're on 11.24.5, I don't immediately think this is related to that prior issue. I recommend letting our technical analysts take a look at this situation.
     
Loading...

Share This Page