3.2.2 Ent changed logging settings, needs fixing

Discussion in 'General' started by jrmarino, Sep 22, 2007.

  1. jrmarino

    jrmarino Well-Known Member

    Ever since I updated to 3.2.2 enterprise, my access logs are gone.

    They used to show like this:

    Now I all I have is this:
    which seems to contain just very recent access items

    The most important question is:
    How can I make 3.2.2 log like it was before? I changed a config item and did a graceful restart, but it's still logging on one file.

    The follow up question is: Why are these upgrades changing the configuration? This isn't the only example I have where a setting was changed after an upgrade.
  2. mistwang

    mistwang LiteSpeed Staff

    looks like awstats is off, if you do not want to turn on awstats, just rotate the log file with a cron job.
  3. jrmarino

    jrmarino Well-Known Member

    awstats is and was running as desired. It was not off.

    I just want it to work like it was before I did the upgrade. That's the only thing I did. I did not have a cron job rotating the files, litespeed did this on its own.
  4. mistwang

    mistwang LiteSpeed Staff

    awstats should be set to do hourly update, daily update will not rotate the log file very hour.
  5. jrmarino

    jrmarino Well-Known Member

    It already is set to hourly. It always has been. And yes, I just checked it again.

  6. jrmarino

    jrmarino Well-Known Member

    It appears that awstats is running, it does clear the access.log file hourly (I guess because it's always small) but it fails to move the previous access.log to a new file.
  7. mistwang

    mistwang LiteSpeed Staff

    It might be a permission issue with the directory containing the log files.
  8. jrmarino

    jrmarino Well-Known Member

    All the files previously were created by "webservd"

    The directory belongs to webservd (755)
    the current log access.log belongs to webservd

    Why would an upgrade change the litespeed user?

    In any case, it doesn't appear to be a permissions thing.
  9. jrmarino

    jrmarino Well-Known Member

    hold on, this looks like a false alarm.

    The files are there. My SFTP program must not be showing all of them.

    120 x 24 files must be too many for it -- they got truncated.
    I see them now that I'm SSH'd into the server and looking at the directory directly.

Share This Page