• 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.

Optimized webalizer brings my server to the knees

J

james1940

Guest
Hi all,

I've got plesk 7.5 installed and last weekend i have enabled webalizer with plesk.

Now my servers goes into very high load at 04:00 when i'm asleep but the usa is awake, so my foreign visitors get a really slow server with a lot of database connection errors.

I already commented dnscache and setted dnschildren to 0, but webalizer keeps bringing my server to his knees.

I also tryed running webalizer 2 times a day, to spread to load over 2 points at the day instead of one.

But all of this didn't have the required effect.

I'm only interesting in the unique visitors that webalizer displays. When you know that is there a way to make it faster and more server friendly?

If this is not possible with webalizer is there another free program on the market that does the same thing as webalizer but without bringing the server down? I don't need very detailed stats, the only thing i really need is the unique visitor number.

Thank you.
 
Do you have any very large logfiles? It's a common reason for webalizer having problems.
 
Back
Top