Hi. Tried today to access some statistics on my server and I get this with awstats:
Warning: Can't find language files for "en". English will be used.
Warning: Can't read file "status_http.pm" (status http detection will not work correctly).
Check if file is in "/usr/share/awstats/wwwroot/cgi-bin/lib" directory and is readable.
Warning: Can't read file "search_engines.pm" (search engines detection will not work correctly).
Check if file is in "/usr/share/awstats/wwwroot/cgi-bin/lib" directory and is readable.
Warning: Can't read file "domains.pm" (domains detection will not work correctly).
Check if file is in "/usr/share/awstats/wwwroot/cgi-bin/lib" directory and is readable.
Warning: Can't read file "operating_systems.pm" (operating systems detection will not work correctly).
Check if file is in "/usr/share/awstats/wwwroot/cgi-bin/lib" directory and is readable.
Warning: Can't read file "robots.pm" (robots detection will not work correctly).
Check if file is in "/usr/share/awstats/wwwroot/cgi-bin/lib" directory and is readable.
Warning: Can't read file "browsers.pm" (browsers detection will not work correctly).
Check if file is in "/usr/share/awstats/wwwroot/cgi-bin/lib" directory and is readable.
Warning: Can't read file "mime.pm" (mime detection will not work correctly).
Check if file is in "/usr/share/awstats/wwwroot/cgi-bin/lib" directory and is readable.
I didn't check this in a while but never had issues with awstats before; all I did was updating, it worked fine aprox 2 months ago. Now the directory mentioned above doesn't exist /usr/share/awstats/wwwroot/cgi-bin/lib, so I created it. But as for the files I checked with locate and none of those files are on my sistem.
So:
How can I solve this without blowing the virtualmin-base (it will be removed as a dep)
If it worked I guess I once had the files - now why and how can I found out how did those dissapear?
Any insight?
Is it OK to force remove awstats, with nodeps? Because I reinstalled it and I still get the error.
Don't take the name of root in vain...Run this, and post the output here in code tags. This will verify all of the files from the awstats package to see if there were any changes.
rpm -V awstatsAlso run this and post the output
rpm -qi awstatsIt works now - had to restart the server after the reinstall, that is weird. But I am still very curious about what happened in the first place... Anyway here is the output, after the reinstall (no other repos BTW, only epel, deactivated by default, needed for fail2ban):
> rpm -V awstats
S.5....T. c /etc/httpd/conf.d/awstats.conf
> rpm -qi awstats
Name : awstats Relocations: (not relocatable)
Version : 7.0 Vendor: Fedora Project
Release : 1.el6 Build Date: Mon Mar 28 15:10:03 2011
Install Date: Thu Feb 13 00:26:44 2014 Build Host: ppc09.phx2.fedoraproject.org
Group : Applications/Internet Source RPM: awstats-7.0-1.el6.src.rpm
Size : 3650574 License: GPLv2
Signature : DSA/SHA1, Thu Jun 2 06:38:10 2011, Key ID e8dd3fa0a0bdbcf9
Packager : Fedora Project
URL : http://awstats.sourceforge.net
Summary : Advanced Web Statistics
Description :
Advanced Web Statistics is a powerful and featureful tool that generates
advanced web server graphic statistics. This server log analyzer works
from command line or as a CGI and shows you all information your log contains,
in graphical web pages. It can analyze a lot of web/wap/proxy servers like
Apache, IIS, Weblogic, Webstar, Squid, ... but also mail or ftp servers.
This program can measure visits, unique vistors, authenticated users, pages,
domains/countries, OS busiest times, robot visits, type of files, search
engines/keywords used, visits duration, HTTP errors and more...
Statistics can be updated from a browser or your scheduler.
The program also supports virtual servers, plugins and a lot of features.
With the default configuration, the statistics are available:
http://localhost/awstats/awstats.pl
Don't take the name of root in vain...Both of those look good, perfect match to my test servers. I suspected your awstats package might have been upgraded from EPEL, I have seen it cause some issues when people leave it enabled.
Maybe apache needed to be restarted after you reinstalled the package, that could possibly explain those errors.
Nope it wasn't apache, was the first thing I restarted. Any ideea how can I track what happened, how did those files fly away?
Don't take the name of root in vain...