Webalizer error (Was: Re: cron.daily error)
rix said:
/etc/cron.daily/00webalizer:
Rix, you'd probably get a better response if you called this thread "Webalizer error". cron.daily is running fine; it's starting Webalizer, as we can see from your sample code. It's webalizer that's giving you the error.
Creating output in current directory
Hostname for reports is 'my.domain.net'
When attempting to ping "my.domain.net" I get and unknown host response, so I'm presuming you really just used "my.domain.net" as a placeholder rather than tell us the real domain name.
That's probably not a good idea, since there really is a "domain.net" and the owner, Wayne Correia of Incline Village, NV, may decide to set up a "my" subdomain at any time. If he does, then people attempting to help you will be looking at the wrong site.
The names reserved for just this purpose are "example.net", "example.com", and "example.org"
.
But as a practical matter, by obfuscating the real name of the domain, in many cases you make it harder for anyone to troubleshoot.
The people who read professional help lists used by hosting companies and ISPs generally ignore help requests that don't give the real domain names, though some do write back a terse "We can't help you unless you give us the real domain name" response.
Without a real domain name to reference, it's often hard to help.
History file not found...
No valid records found!
Does anyone knows how to fix this ? I'm not familiar with webalizer.
Presuming a domain name of example.net, and a username of example, check for the existence of:
/home/example/domains/example.net/stats/webalizer.hist
If it doesn't exist, you'll get this error.
Note that if you run webalizer before anyone has visited a new domain this is a normal error.
Have you or anyone else visited this domain? If so, and if there is a history file, and if after 5 am the next morning (server time) you're still seeing the error, then someone (perhaps DirectAdmin Support) needs to take a look at your apache configuration.
Jeff
