another error is being sent


Error: Can't open log file /home/sites/hannibal.infilmbox.com/logs/web.log
Error: Can't open log file /home/sites/tombraider.infilmbox.com/logs/web.log

what does this mean ?

Who is the cronjob being run by? Whoever it is being run by probably does not have rights to read that file ... as it might be chmod 600.

first of all... make sure that the files exists :)

If they do not exists, but everything else does, don't worry, it'll patch itself once the sites are up. if these sites does not exists, you will need to remove their old associated site# in /etc/logrotate.d/

i checked one of them

/home/sites/hannibal.infilmbox.com/logs/web.log

and in /logs

web.log doesn't exist

only

ftp.cache.new
ftp.log
ftp.stats

i recently installed webalizer as well..

Is the site new?

You can always try creating the file and hope their script catches up and fix itself :)
touch /home/sites/hannibal.infilmbox.com/logs/web.log
(make sure you set the right permissions & owner)

it ain't new, but it hasn't had any traffic since it was setup - could that be the problem ?

is

touch a command ?

Eva, that error is coming from webalizer trying to read a log file for a site that doesn't have one. If the site ever got traffic, a log file would be generated and webalizer wouldn't produce the error.

You'll get it if you create dummy domains on the server as well. Nothing to worry about.

nope still getting the errors

it definitely has to do with webalizer and log rotate

i read these threads but don't understand what they are saying

http://qube-users.qube.de/maillists/cobalt-users/2000-July/msg01127.html

http://list.cobalt.com/pipermail/cobalt-users/2000-July/016334.html

http://list.cobalt.com/pipermail/cobalt-users/2000-August/019100.html

Originally posted by eva2000.com
http://list.cobalt.com/pipermail/cobalt-users/2000-July/016334.html

Well this one is saying that although webalizer reads the web.log file, there might be a case where the log files are rotated before webalizer can read them (due to excessive log size), thus you won't get an accurate reading (gap in the report).

Now if the sites are getting many hits, this might happen, but if this isn't the case, then you can rule this out.

the sites don't get any hits well a few.. so i am stumped :(

If you are having a problem with a domain, really the quickest and easiest way to fix it is to delete the domain and re-enter it. This is what I'd recommend you do.