The log will not be truncated because of errors above: /var/www/vhosts/system//logs/xferlog_regular. The log will not be truncated because of errors above: /var/Skip log `proxy_access_log' because it has parent `access_log' The log will not be truncated because of errors above: /var/Processing the log /var//usr/share/awstats/-LogFile=/var/Execution of /usr/share/awstats/-LogFile=/var/failed with return code 1. Skip log/var/because it is empty or does not existĮrror: Unable to execute /usr/share/awstats/tools/awstats_ -awstatsprog=/usr/share/awstats/ awstats]# /usr/local/psa/admin/sbin/statistics -calculate-one -domain-name= Skip log `proxy_access_ssl_log' because it has parent `access_ssl_log' Skip log `proxy_access_log' because it has parent `access_log' The URL must not specify a specific file name. Popen_exec: command failed code: 127, error: noneĮrror: Unable to execute /usr/share/awstats/tools/awstats_ -awstatsprog=/usr/share/awstats/-dir=/var/-awstatsprog=/usr/share/awstats/-dir=/var/www/vhosts/system//statistics//webstat-ssl/current The stats are automatically updated when you visit the correct URL. The log will not be truncated because of errors above: /var/sh: /usr/share/awstats/tools/awstats_: No such file or directory You can enable manual updates in cPanel, this will sometimes solve the problem of AWStats not updating in a specific user account. System error 2: No such file or directory Processing the log /var//usr/share/awstats/-LogFile=/var/Execution of /usr/share/awstats/-LogFile=/var/failed with return code 1.įorkExecvPipes: execv() failed: No such file or directory Then, AWStats continues its work (if configured as cron job) and updates the statistics from the formerly offending point on.~]# /usr/local/psa/admin/sbin/statistics -calculate-one -domain-name= Before you should stop the webserver (e.g., service apache2 stop) and afterwards start it again ( service apache2 start). However, if more than 50 of that kind happen to occur without a break, AWStats stops working completely from this point on and for the future (exactly: until the log file is exchanged).Īs a remedy, one can delete the lines in question from the log file (at least so many that less that 50 remain consecutively). Such entries are appearing from time to time in webserver log files and are no problem normally. I tried crontab -e but I couldn't locate anything related to statistics. ![]() 2, Change the directory to: /home/user/tmp/awstats There are the conf files for domains under that particular cPanel account. You have to check the following this via shell as root user. (where stands for a concrete IP address) as invalid. I believe the path to the cronjob is not set correctly. Why AWStats is not updating automatically There are a lot of reasons behind this. Now it seems that it is a routine - and they. ![]() "-" 408 1447 "-" "-"Īpparently, AWStats evaluates log-file entries with blank fields as On my server, Awstats have been playing games with me: not updating and missing data on several occasions. ![]() "GET / HTTP/1.1" 200 1234 "" "Mozilla/4.0 (compatible MSIE 5.01 Windows NT 5.0)"Īnd this is an example of records AWStats found in your log file (the record number 50 in your log): I do not know what cpanel does differently, but I have the same version, and nearly same config file and my external awstats works better. So I installed external and found out the hard way. This means each line in your web server log file need to have "combined log format" like this: AWStats i found to be having wrong statistics too as well, too low compared to the log file I perused. Your log file /var/log/apache2/ssl_access.log must have a bad format or LogFormat parameter setup does not match this format. Where stands for the configuration in question, results in an error message likeĪWStats did not find any valid log lines that match your LogFormat parameter, in the 50th first non commented lines read of your log. The following situation arises (for me the first time after years of usage): AWStats runs by crontab, but all of a sudden no statistics are generated anymore an error related to the execution of crontab can be ruled out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |