• 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 stopped working

R

rembrandt

Guest
Hello,

I've got two servers (both psa 7.5.4), the first had a shared account of two customers which both had several domains hosted on that server. because one of those customers wanted new hardware i've used the migration manager to move that account to a brand new server.

So far so good. however after i've moved the customer to that other server i noticed that webalizer wasnt working propperly on the first server. It stopped working on march 7th 2007. So that's whren i started looking for oversized logfiles, but there wern't any.

So now i've got two servers on which webalizer doesn't work (= don't update). The logfiles get updated and even the logrotation works like a charm. So my best guess is that it's got something to do with the MySQL tables which store some information on webalizer...

Has anyone experienced this before and if so, knows the solution to this problem?

Best regards.
 
Back
Top