Skip to main content

Awstats hourly reports not working

Comments

7 comments

  • cPRex Jurassic Moderator

    Hey there! I wouldn't expect you to ever need to modify perl modules on the machine to get anything working - those will also be overwritten as part of the nightly update on the server.

    Could you submit a ticket so we can do a bit more research on why this isn't working on your machine?

    0
  • alfasoft

    Hi,
    I would love to submit a ticket with you guys but my CPanel license is supported by a third party, I've contacted them 2 months ago but still no feedback... Could you give us a hand ?

    0
  • cPRex Jurassic Moderator

    Can you contact cs@cpanel.net and let them know about your experience with your hosting provider?

    As far as the stats issues - if you remove the customization to the perl module file and execute "runweblogs" does *anything* happen for the associated user?

    0
  • alfasoft

    Yes, I will ask the person in charge of my company to do that, do we need to provide anything in regards to the support ticket that we sent to the third party ?

    I did remove it and executed the script "runweblogs" and not much changed, the daily reports keeps on working, the hourly ones don't and we still have the same error as showed in the prints above

    0
  • cPRex Jurassic Moderator

    We don't need any other details except what you've asked your host and what their reply was.

    Another user reported similar behavior after finding issues with the log format configuration in Apache:

    https://support.cpanel.net/hc/en-us/community/posts/19226074458775-cpanel-awstats-hourly-stats

    Can you check that and see if that could be related?

    If not, I'm not sure what else could be causing this.

    0
  • alfasoft

    Hey, sorry for the late response.

    I just checked and the domlogs are being updated so I don't really think the log format could be related to our issue...  do you have any other idea ? 

    0
  • cPRex Jurassic Moderator

    I don't - you'll likely need to create a ticket at this point so this can be investigated.

    0

Please sign in to leave a comment.