[Solved] Listeners reporting 'Errors' 'Restart Required'

Discussion in 'General' started by EvoIX_MR2006, Nov 28, 2010.

  1. EvoIX_MR2006

    EvoIX_MR2006 New Member

    I've got 4 Listeners that are all reporting errors and 4 virtual hosts claiming that a restart is required, however after restarting, the status remains the same. The sites all still work, but the logging facilities appear not to.

    The server error log doesn't show anything at all, no errors, just information about the restarts I've been doing and the expiration of my License key.

    Any ideas?
  2. webizen

    webizen New Member

    Is there anything logged in stderr.log?

    Also, please post your logging level at server and vhost level here:
    Admin Console-> Server-> Log -> Server Log
    File Name:
    Log Level:
    Debug Level:
    Enable stderr Log:
    Admin Console-> Virutal Hosts -> vhost1,2.. -> Log -> Virtual Host Log
    Use Server's Log:
    Log Level:
  3. EvoIX_MR2006

    EvoIX_MR2006 New Member

    Log Level is Debug for server, All vHosts are ERROR only.

    Nothing in stderr.log out of the ordinary.
  4. webizen

    webizen New Member

    What about Debug Level at Server Log?
  5. EvoIX_MR2006

    EvoIX_MR2006 New Member

    I don't quite understand what you're asking, server log level is already set to debug?
  6. webizen

    webizen New Member

    Even the Server log level is set to DEBUG, the debug level could be set to NONE (default) which disables debug logging. Please double check. Change to something like MEDIUM or HIGH if it is NONE.
  7. EvoIX_MR2006

    EvoIX_MR2006 New Member

    I've changed this to Medium. I'm assuming this should populate immediately if there is an issue?
  8. webizen

    webizen New Member

    Yes, the change is instant and no server restart is needed.
  9. EvoIX_MR2006

    EvoIX_MR2006 New Member

    I'm not seeing anything new in either stderror.log or the server log in the Litespeed console. Somewhere else I should be looking?
  10. webizen

    webizen New Member

    shell into the server (via ssh or terminal console) and check /path/to/lsws/logs/[error|stderr].log
  11. EvoIX_MR2006

    EvoIX_MR2006 New Member

    The stderr.log file doesn't have anything in it since November 25th, the error.log is now storing debug info and has too many standard notices in it to make it readable. Am I looking for something specific that might cause this or are there a number of reasons?
  12. webizen

    webizen New Member

    If the errors about the listeners persist, you should see entries in error.log like '2010-12-01 02:34:56 [ERROR] err_about_the_listener ...' and more entires around that with '[NOTICE|INFO|DEBUG]' to give more details. Are you still seeing listener errors? Can you paste a few lines around the error entry here (or via pm) if so?
  13. EvoIX_MR2006

    EvoIX_MR2006 New Member

    I'm not seeing anything in the logs related to this. Can I PM you login information so you can take a look?
  14. webizen

    webizen New Member

    Yes, please.
  15. webizen

    webizen New Member

    Here are the errors that may give a clue.

    Code:
    [STDERR] PHP Warning: filemtime() [<a href='function.filemtime'>function.filemtime</a>]: Stat failed for /tmp/lshttpd/.status (errno=13 - Permission denied) in /usr/local/lsws/admin/html.4.0.17/classes/ws/Service.php on line 33
    [STDERR] PHP Warning: fopen(/tmp/lshttpd/lshttpd.pid) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Permission denied in /usr/local/lsws/admin/html.4.0.17/classes/ws/Service.php on line 70
    
    Basically lsws is unable to open files (.status and lshttpd.pid) in /tmp/lshttpd/. Therefore, web admin console still showing the old server status (no matter how many graceful restarts are done) and real-time stats is empty as well.

    Please reference the following post and see if the fix applies to your case:

    http://www.litespeedtech.com/support/forum/showthread.php?t=3718
    Last edited: Dec 10, 2010
  16. webizen

    webizen New Member

    Looks like the issue is resolved.

Share This Page