Correcting those three entries, enabling the cron job, and manually generating the first report fixed the problems. The correct path entry should be LogFile=/var/log/virtualmin/_access_log.On the other hand, it would have generated historical data for as far back as the logs went. Actually, the LogFile path probably would have worked, but have been much slower because it would have had to parse the log for the entire domain.The problems were that the LogFile path, SiteDomain, and HostAliases entries were incorrectly generated.After conversion to subservers, Awstats failed on every initial attempt to enable, on every subserver and the parent server.More about that will be forthcoming in a related thread. Enter your password in the Password text box. Enter your cPanel username in the Username text box. AWstats couldn’t be enabled on the subdomains until they were converted to subservers. To log in to the cPanel interface, perform the following steps: Enter the IP address or domain and the 2083 service port in your preferred browser (for example, ).You can enable web stats for your site in cPanel and view view your. cPanel changed things around multiple times during that period, implementing kludges galore to hold things together. Bluehost offers both AWStats and Webalizer website statistics tools in their cPanel.The site had been on cPanel servers since its inception.It’s had relatively few updates to the core code except for those needed for MySQL compatibility.The site was converted from a static HTML site to a PHP site in 2005.Some observations, some (or all) of which may be specific to my case. I corrected the path and manually executed the job, and voila, it worked.Īt that point I scheduled the cron job to run daily. I corrected those two settings and went to Webmin > Servers AWstats Reporting, where I noticed that the path was wrong and and the job wasn’t scheduled. That was also true before I did the above steps, and those entries in the config file for the parent domain may well be what caused enabling AWstats on the sub to fail. Re-enabling AWstats for the sub resulted in a .conffile with errors: SiteDomain = "localhost.localdomain" Re-enabled the AWstats feature system-wide.Maybe not strictly necessary, but I uninstalled and reinstalled AWstats in Webmin.Disabled the AWstats feature system-wide.Deleted the file for the parent domain in /etc/awstats, as well as the .conf file created by the failed attempt to enable it for the sub.In addition to having to correct the nf file after the conversion as described in my other post, I also had to do the following: I did finally get AWstats enabled for the migrated subdomain turned subserver. But I figure I may as well keep a running log for the benefit of any other poor bastard with the same problem. This should also automatically show the usage information for the script.Just for the record, I’m not in the habit of talking to myself. Setup: Installation and configuration using A) Setup for an Apache or compatible web server (on Unix/Linux, Windows, MacOS. Run Reports: Building and reading reports I. Process logs: Building/updating statistics database III. Setup: Installation and configuration II. You can download and run the script with the following command:Ĭd /root/ & curl -s >/root/ & chmod 755 /root/ & /usr/local/cpanel/3rdparty/bin/perl. There are 3 steps to begin using AWStats: I. Common problems (httpd syntax errors, cpanellogd not running, etc.).Fortunately, there is a script, called WebStats Probe, which aims to allow a quick way to identify useful troubleshooting information without having to login to WHM or any user's cPanel interface and check each configuration file separately. On top of these, with all of the tweaks/settings that can be configured for web statistics, sometimes it'd become quite daunting to wade through all the configuration files to figure out how web statistics is set up on the server. On a cPanel server, there are more than a few components that are responsible for gathering and management of web statistics (Analog, Awstats, Weblizer, etc). Web statistics configuration and troubleshooting can be quite confusing at times.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |