Force the creation of Webalizer stats?

Hi, is there a way to force the creation of the webalizer stats so I can test it out?

I dont leave the server running over night at the moment so they never get created but I wouldnt mind making sure that they work.

At the moment the http://domain/stats/ causes a 404

Cheers
Anim

 

Worked a treat, thankyou.

Anim

 

Hi guys - just tried running the above command to "force" the web stats and received the error below:

Code:

ws0:~# /root/ispconfig/php/php -q /root/ispconfig/scripts/shell/logs.php

Warning: asort() expects parameter 1 to be array, null given in /root/ispconfig/scripts/shell/logs.php on line 172

Warning: Invalid argument supplied for foreach() in /root/ispconfig/scripts/shell/logs.php on line 173

I too received a 404 error when navigating to domain.xx/stats; /stats isnt a folder in this domains web space as far as I can see, so I cant check permissions?

I'm reluctant to run the second command as I don't know if i have broke anything, I'm not a DBA and have limited MySQL knowledge. This box is in production and if it needs downtime, I will need to do this off-peak.

Spec:

ISPConfig2 - Debian 5 - 2.6.26-2-amd64 -MySQL 5.0.51a-24+lenny4 |

 

bump, would really appreciate some help on this.

 

What's the output of

Code:

ls -la /var/www/

?

 

Thanks for getting back to me falko.

Code:

ws0:/proc/sys/kernel# ls -la /var/www/
total 32
drwxr-xr-x  7 root         root 4096 2011-01-12 00:30 .
drwxr-xr-x 14 root         root 4096 2011-01-11 15:13 ..
-rw-r--r--  1 root         root   45 2011-01-11 15:13 index.html
drwxr-xr-x  3 root         root 4096 2011-01-12 00:30 localhost
drwxr-xr-x  2 root         root 4096 2011-01-11 15:26 sharedip
drwxr-xr-x  8 web1_xx web1 4096 2011-01-14 11:39 web1
drwxr-xr-x  2 root         root 4096 2011-01-16 06:25 webalizer
drwxr-xr-x  3 root         root 4096 2011-01-12 00:30 ws0.xxx.xx
lrwxrwxrwx  1 www-data     web1   13 2011-01-11 15:57 www.xx.xx -> /var/www/web1

 

Looks ok. You can ignore the warnings - I've taken a look at the code, and the warnings come from the part where the script tries to delete old access logs. It is safe to run the second command as well (make sure you run the first one before).

 

I know this is an old thread, but it's exactly my question.
So, what is the "modern way" (v3.0.5.2) to do this?
Thanks!