• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Incorrect traffic reporting - Plesk Control Panel

N

NicoV

Guest
We are running Plesk8.6 - Centos 5 x64 on a few of our shared hosting servers.

We have an issue where a domain reported 16TB!! of traffic on the control panel for September.
Interresting enough webalizer doesnt reflect the same trafic , rather 2.7gb which on par with previous month's traffic.

Investigating the domains traffic for Sept in the PSA database, the 27th reflects the traffic under http_out.

+--------+------------+---------+----------------+--------+---------+---------+----------+--------------+---------------+
| dom_id | date | http_in | http_out | ftp_in | ftp_out | smtp_in | smtp_out | pop3_imap_in | pop3_imap_out |
+--------+------------+---------+----------------+--------+---------+---------+----------+--------------+---------------+
| 1959 | 2010-09-27 | 0 | 18194750620083 | 0 | 0 | 3476235 | 2972434 | 5652 | 4097980 |
+--------+------------+---------+----------------+--------+---------+---------+----------+--------------+---------------+

Investigating the Apache access log files reflect funny entries, which Plesk seems to interpret as traffic amounts which Sawmill and Webalizer doesnt.

41.133.74.226 - - [27/Sep/2010:13:57:41 +0200] "GET /images/specials.gif HTTP/1.1" 200 1088 "/specials.php" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; InfoPath.2; 9986066903; update/02025; 666604582703; 978806703; 89770703; 979904903; 96690603; 7879067903; 887806903; 896702903; 669601803;

.................

97780903; 979806603; 988708903; 69890786903; 9779019603; 887805903; 877907126803; 9867087803; 888802688603; 996604603; 69890523703; 8799096903; 976904014703; 96790195703; 9799023903;

Has anyone come across anything similar, and is there a way to prevent Plesk/Apache to calculate these log entries as traffic. I dont think there is a way of avoiding similar entires going forward.
 
Back
Top