• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Awstats: Error: SiteDomain parameter not defined in your config/domain file

Alban Staehli

Regular Pleskian
Hi,
When I try to access the web statistics via /webstat URL of any of my domains, the following error appears :

Error: SiteDomain parameter not defined in your config/domain file. You must edit it for using this version of AWStats.

Setup ('/usr/local/psa/etc/awstats/awstats.xn-DOMAINNAME-http.conf' file, web server or permissions) may be wrong.
Check config file, permissions and AWStats documentation (in 'docs' directory).


(replace DOMAINNAME with the domain name, for example plesk.com)

Any idea on how to solve this annoying and general issue?

Thanks for your help.
Regards,
 
Try to run daily script manually and check that the following errors happen:

# /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php

statistics: Mysql server has gone away. Trying to reconnect [new_unode] Warning: String exceeds storage size (252) [new_unode] Warning: String exceeds storage size (251) [new_unode] Warning: String exceeds storage size (250)
statistics: Mysql server has gone away. Trying to reconnect
statistics: Mysql server has gone away. Trying to reconnect

In this case just increase wait_timeout value in my.cnf and restart mysql.
I hope it will help.
 
Hi, thanks for your fast reply.
I've the following messages appearing when running manually "/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php" :

find: `/var/qmail/mailnames/domain1.tld/MailName1/Maildir': No such file or directory
find: `/var/qmail/mailnames/domain1.tld/MailName1/Maildir': No such file or directory
xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option
find: `/var/qmail/mailnames/domain2.tld/MailName2/Maildir/.Boite/cur': No such file or directory


Thanks for your help.
Regards,
 
But whether statistics calculated correctly after that?
 
Try to reconfigure domain xn-DOMAINNAME from your example with httpdmng utility (--help option for details). I hope that it will recover AWStats configuration for this domain.
 
I tried the following:
1. execute: /usr/local/psa/admin/bin/httpdmng --reconfigure-domain domain.tld
2. execute: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php

Result: /webstat/ still shows the same error message.

Then, I tried the following:
1. Edit /usr/local/psa/etc/awstats/awstats.xn-DOMAIN.TLD-http.conf
2. The line SiteDomain="" was here. I replaced the line with SiteDomain="domain.tld", and saved the file.
3. execute: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php

Result: /webstat/ don't show the error anymore for the current month (but the previous months pages still show the error messages)

Conclusion: I think that the "/usr/local/psa/admin/bin/httpdmng --reconfigure-domain domain.tld" command should define this SiteDomain line... but it doesn't... Any idea?

I tried then to execute again "/usr/local/psa/admin/bin/httpdmng --reconfigure-domain domain.tld", and edited again the file /usr/local/psa/etc/awstats/awstats.xn-DOMAIN.TLD-http.conf.
Guess what: the SiteDomain="domain.tld" line is still there... so it seems that /usr/local/psa/admin/bin/httpdmng doesn't modifiy the awstats config files. I also checked the last update dates of the files in /usr/local/psa/etc/awstats/ directory, and none has been modified since 4 months => it definitely confirms that httpdmng doesn't touch those files!

Thanks for your help.
Regards,
 
Last edited:
Sorry, I have no idea what is wrong there with AWstats configuration. I suggest you contact Support Team. They will check and fix this issue directly on your server.
 
Thx for information. I already opened a ticket about this bug and I had no feedback from parallels.
By the way, this issue is a BUG, so support should be free of charge.
Can you help me to get an answer from the support team?
Regards,
 
Last edited:
Thx for information. I already opened a ticket about this bug and I had no feedback from parallels.
By the way, this issue is a BUG, so support should be free of charge.
Can you help me to get an answer from the support team?
Regards,

Please send me ticket ID in PM. I will check it.
 
When I try to create ticket support, I receive this message:
"Our records indicate that the license key you have entered is not attached to any valid support package and is not eligible for any of the new Support Options for Parallels Plesk Panel. See details in the following Knowledgebase article: http://kb.parallels.com/en/114130."

So, I've to pay for support for a BUG fix?
 
Could you please provide me step-by-step instruction (full bugreport) how this "bug" can be reproduced on fresh Plesk installation?
 
1) go to /webstat/ of one of the domain hosted on the server
2) figure out the error message about misconfiguration of awstats

Note I've 2 installations of Plesk, and only one get this problem.
 
Sorry, but I can't reproduce it on my test Plesk servers. Need more details.
 
Alright, thanks for your help.
Will try to understand by myself what to do in order to get support from Parallels...
I'm disappointed by this issue, as well as the complexity to get support from your company.
Regards,
 
If you report a problem to Support team it means that you wish that your problem should be fixed on your server. In that case you pay for support, but not for bug report.

Also if you pay $75 for incident and support confirm that it is really bug of our product - you will receive one free incident bonus.

I think that is reasonable and fair.
 
Back
Top