Litespeed has stopped logging

Discussion in 'Bug Reports' started by priestjim, Aug 16, 2010.

  1. priestjim

    priestjim Well-Known Member


    Well the subject says it all. After upgrading to LSWS 4.0.16 on the 9th of August, litespeed just stopped logging everything. All access logs are empty (even Litespeed's own /usr/local/lsws/logs/access.log) and no new visits are logged. Please note that the server is using Plesk's pipelog feature to log the data and up until 4.0.15 it was operating fine.

    Access to the server to verify the issue is available upon PM.

    System information:
    OS: RHEL4
    LSWS Version: 4.0.16 Enterprise
    Last edited: Aug 16, 2010
  2. mistwang

    mistwang LiteSpeed Staff

    Is the piped logger process running?
    We made some change on piped logger, the logger process run as root now.
    Please try a force reinstall first, if you use Cloud Linux, piped logger may not work properly.
    If the problem still there, just send us a temp root login. We will check.
  3. priestjim

    priestjim Well-Known Member

    Yes the piped logger is running "fine":

    [root@server2:/root]> ps aux| grep [p]ipelog
    root 3957 0.0 0.0 5376 1072 ? S 08:02 0:00 pipelog
    root 3978 0.0 0.0 5376 1076 ? S 08:02 0:00 pipelog
    root 3979 0.0 0.0 5376 1072 ? S 08:02 0:00 pipelog

    It's not configured though through Litespeed, its configuration is taken from the Apache conf file. Reinstalling unfortunately did nothing. I'll PM you the connection details to take a peek.

Share This Page