• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Webalizer problem

D

dvotion

Guest
Hello,

I'm have problems with Webalizer not generating reports for 1 hosting account anymore. On all the other hostingaccounts Webalizer works fine but on this one not. How can I solve this problem? I've searched all over the net and read about 2 big logfiles and dns_cache.db. I've tried to change my logrotation and also tried to delete the dns_cache.db (only renamed) but nothing helps.

Thank you for helping me out!

gr. Dennis
 
Any luck?

Have you had any luck fixing your issue? I have a number of customers that aren't getting data from Webalizer, and they have 'broken' on multiple days.

From what I can tell, the webalizer.hist and webalizer.current files have become corrupt and are causing the issue. I'm poking around now to see what my options are, but I feel like those customers aren't going to have history now.

What really bugs me is that I can't find a rhyme or reason to the break. If it happened on a bunch of customers now, what says it won't happen again tomorrow?
 
Back
Top