Navigation

esezako · #41 28th February 2011, 10:31

But, why some sites processed correctly the stats and other no?

esezako · #42 1st March 2011, 14:09

Quote:

Looks ok. My guess is that for some reason, cron uses a wrong PATH and therefore cannot find webalizer.

Can you add this as the first line to your crontab (by running
Code:
crontab -e
)?

Code:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

The problem is not solved

falko · #43 1st March 2011, 16:03

Do the sites where it doesn't work have an access log in the logs directory? Maybe noone visited the sites; in this case there's no access log to process.

esezako · #44 1st March 2011, 16:47

Quote:

Do the sites where it doesn't work have an access log in the logs directory? Maybe noone visited the sites; in this case there's no access log to process.

Like I say before, yes.
All logs correct, but various websites suddenly stoped of create stats. ¿?

esezako · #45 1st March 2011, 19:17

Think i find the problem. I have enormous log files or my sites (Many big sites make with Drupal CMS). I think the problem is a php time limit to execute the webalizer.php script.

I change this limit but, how can i reduce the filesize of logs in ispconfig?

esezako · #46 2nd March 2011, 09:57

How can i recalculate all stats of a particular month?

anubix · #47 8th March 2011, 18:16

esezako!!!!!!!!!!!

You are 'da man'

it works now after adding
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

to the first line of the cron tab.

but i have 1 question, isnt there a better place to add the path?

anubix · #48 8th March 2011, 18:38

it seems that the stats dont work for all of my sites.
is this because i need to visit the site from different ip addresses if there are no visits yet?

(the files are not created in the stats folder)