Skip to main content

Can't process Awstats on new server

Comments

8 comments

  • timg
    So an update on this, I edited the ssl/awstats.*.conf file for the one account and changed logformat to 4. The runweblogs script resets it to 1 but after doing that the script doesn't seem to crash but it sees all the lines in the log as corrupt. Stats are still not updated.
    [2017-04-04 10:55:00 -0400] Direct access to last remembered record has fallen on another record. [2017-04-04 10:55:00 -0400] So searching new records from beginning of log file... [2017-04-04 10:55:00 -0400] Jumped lines in file: 0 [2017-04-04 10:55:00 -0400] Parsed lines in file: 6583 [2017-04-04 10:55:00 -0400] Found 0 dropped records, [2017-04-04 10:55:00 -0400] Found 0 comments, [2017-04-04 10:55:00 -0400] Found 0 blank records, [2017-04-04 10:55:00 -0400] Found 6583 corrupted records, [2017-04-04 10:55:00 -0400] Found 0 old records, [2017-04-04 10:55:00 -0400] Found 0 new qualified records. [2017-04-04 10:55:00 -0400] Complete
    Update: Restarting cpanellogd ends up with the crashing thing again.
    0
  • cPanelMichael
    Hello, It looks like ticket number 8354703 was opened to report this issue. I'll update this thread with the outcome of the support ticket once it's closed. Thank you.
    0
  • timg
    Thanks Michael. Is there anything I can do myself before support looks into it? I submitted the ticket as a plan B in case I can't figure it out myself.
    0
  • cPanelMichael
    Hello, To update, it looks like this issue stemmed from an extra LogFormat entry in the Apache configuration file. Removing the extra entry should address the issue. Thank you.
    0
  • dhultin
    Hello, I had a similar issue today and banged my head on it for about 1.5 hours. This was with EasyApache 4. Turns out Piped Logging being disabled was the issue and luckily a co-worker knew this as I was out of ideas. Once I went to WHM -> Apache Configuration -> Piped Logging Configuration and enabled that, then restarted Apache the awstats were again processing the logs files for Apache properly. I hope that solves your issue if you have the same problem.
    0
  • cPanelMichael
    Hello @dhultin, It's possible that enabling Piped Logging overwrote a custom log configuration entry that was causing the problem with Awstats. If you'd like us to take a closer look, feel free to open a support ticket and we can disable Piped Logging to see what the issue could be. Thank you.
    0
  • dhultin
    From What I could see the issue was being caused by Ajax calls. The response code in the Apache logs showed "0 200 etc etc" with 200 being the response code. The Ajax was adding the 0 before the response codes and causing the issue. However the only resolution was to enable piped logging. The Actually logging configuration did appear to be fine though. Here is an example. 10.20.4.38 - - [25/Apr/2017:14:44:23 -0400] "GET /contact/?_wpcf7_is_ajax_call=1&_wpcf7=260&_wpcf7_request_ver=1493145863672 HTTP/1.1" 0 200 2 "domain URL removed by me" "Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36" After enabling piped logging the '0' from the ajax call went away and awstats worked since now the response code was in the expected location, where the 0 was previously.
    0
  • cPanelMichael
    Hello, Feel free to open a support ticket using the link in my signature if you'd like us to take a closer look at the affected system and see why it's not working as expected when Piped Logging is disabled. You can post the ticket number here and we will update this thread with the outcome. Thank you.
    0

Please sign in to leave a comment.