AWStats 6.1 - easy install/remove script here.

Thanks...
So apache only allow the permission 755 for sucurity reason...
Next time if the perl script have 500 error..
I should check the permission first right?

I had update to version 2.0, it's seems ok..
 
If I install awstats this way...
will it be accessable to only the domain's admin? Or is there a way to make it accessible to someone without DA User Access?

(I'd like to install it for people to see that are not DirectAdmin users).

Thanks.
 
Hi ..

I hope to have a new awsetup or awsetupall script, that can add the awstats to user, and add cron job for only admin's cron job or reseller's cron job, not user's, because if you have too many user, they will run awstats at the same time, but if you only add awstats to some sheel script, they will run step by step like these:

awstatsall.sh

/home/homerpub/domains/domain1.com/public_html/cgi-bin/awstats/awstats.pl -config=www.domain1.com/ -update > /home/homerpub/domains/domain1.com//public_html/cgi-bin/awstats/status.log
/home/homerpub/domains/domain2.com/public_html/cgi-bin/awstats/awstats.pl -config=www.domain2.com/ -update > /home/homerpub/domains/domain2.com//public_html/cgi-bin/awstats/status.log

and I needn't to waste time to change the cronjob time of every user.

I think it's not too hard to write a new script, but I hope to use your awsetup for my DA system. And I don't know your awsetup script is in GPL license or not, so I hope you can help me to develop the new version of awsetup that can run all the site no problem.

Thanks..
 
Thanks, it istalled with no problems :)

But there is a problem in how it's working.
I have an average of 56000 unique visitors a day, but awstats is displaying only about 5000, a very small fraction.
I have no idea what might be going on, the server log variable seems to point to the correct log location... any ideas why it's not showing me complete data?

Thanks.
 
> Re : any ideas why it's not showing me complete data?

56000 unique visitors a day seems to be an awfull lot, the only couple of things that i could think of would be .. either your really getting 5000 and whatever stats you were getting were incorrect .. or awstats cant deal with that much data in one go , or maybe the log files are croped to a max size and some data are lost by the time awstats runs.

Have you tried running it 2, 3 or 4 times a day instead of one ? you should anyway on a site getting that much traffic, it would help with the load on the system too.


Miky
 
In reply to : " different "

Yes , the code is GPL, there is not much to it really, anyone is welcome to make something better out of it.

I still think the next level should really be a pluggin, with something a bit more advanced for the cronjobs and reseller/user levels.

There is an other thread in those forums about an awstats pluggin, still betta, I tried it at an early stage and didnt like it because I had something slightly different in mind... but it was a while back and it would be stupid to re-invent the wheel .

If some people can try the betta awstats pluggin and let us know here if it is what they are after or not .

I sure would take a bit of time to write a serverwide awstats pluggin from scratch if it was any usefull... that was the original idea.


Miky
 
i get this error:

- Package downloaded and unpacked.
cp: illegal option -- a
usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src target
cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src1 ... srcN directory
- CGIs installed.
cp: illegal option -- a
usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src target
cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src1 ... srcN directory
cp: illegal option -- a
usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src target
cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src1 ... srcN directory
cp: illegal option -- a
usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src target
cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src1 ... srcN directory
cp: illegal option -- a
usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src target
cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src1 ... srcN directory
- AWStats web directories installed.
- Config file created.
- Processing logs for the first time, this might take a few minutes...../home/admin/domains/elm2.com/public_html/cgi-bin/awstats/awstats.pl: not found
Done.
chown: admin.admin: Invalid argument
chown: admin.admin: Invalid argument
chmod: /home/admin/domains/elm2.com/public_html/cgi-bin/awstats/awstats.pl: No such file or directory
chmod: /home/admin/domains/elm2.com/public_html/cgi-bin/awstats/awredir.pl: No such file or directory
- File permissions updated.
- Cron Job Added in DA User Cron Table.
- Cron Job Added in System User Cron Table.


most likely cause its a freebsd system?
 
Yes the cp command seems different .. i manage to get hold of a freebsd cp man page you can try :

edit the script with pico or other text editor:

# pico -w awsetup.pl

Search for cp -a in the 'install section' i think there are 5 of those, try to change it to
cp -R -p

Search for cp -a -f in the 'upgrade section' i think there are 5 of those, try to change it to
cp -R -p -f

Let us know if that does the trick , if so i'll change the script to handle freebsd as well.

Cheers

Miky
 
- Package downloaded and unpacked.
- CGIs installed.
- AWStats web directories installed.
- Config file created.
- Processing logs for the first time, this might take a few minutes.....Done.
chown: admin.admin: Invalid argument
chown: admin.admin: Invalid argument
- File permissions updated.
- Cron Job Added in DA User Cron Table.
- Cron Job Added in System User Cron Table.

is what I get

see the chown arguement I guess that doesn't work for Freebsd.

Then it works up to a point until you go to the .pl file

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
 
Last edited:
Nice program, made my life that much easier.

I just have a slight problem, all the images in the statistics page show up as broken links. It seems that this script has made all the images password protected or something because i tried to access an image directly (eg. awstats/icon/other/vk.png) it shows up with a "Forbidden 403" error. I've changed all the permissions of the images to 755 and the other folder permission to "777" as well. So i don't know what is wrong.
 
This is a generic reply, but it may be applicable:

Is AWStats operating as from the cgi-bin directory? If so, is it linking to images in a cgi-bin directory?

You may not be allowing that.

In fact you probably aren't.

Jeff
 
Thanks for the script!

Some files are rwxrwxrwx. You could add to the awsetup script (add en upgrade) for some extra security: ;-)

-----

system("chmod 644 /home/$user/domains/$domain/public_html/cgi-bin/$awsdir/awstats.model.conf");
system("chmod -R 644 /home/$user/domains/$domain/public_html/cgi-bin/$awsdir/lang");
system("chmod -R 644 /home/$user/domains/$domain/public_html/cgi-bin/$awsdir/lib");
system("chmod -R 644 /home/$user/domains/$domain/public_html/cgi-bin/$awsdir/plugins");
system("chmod 755 /home/$user/domains/$domain/public_html/cgi-bin/$awsdir/lang");
system("chmod 755 /home/$user/domains/$domain/public_html/cgi-bin/$awsdir/lib");
system("chmod 755 /home/$user/domains/$domain/public_html/cgi-bin/$awsdir/plugins");

-----
 
is this script still ok to use? Has anyone used it recently without errors? thanks.
 
hi a have a problem ....

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@****.info and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.


Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


--------------------------------------------------------------------------------

Apache/1.3.31 Server at www.***** Port 80



---------------

What is wrong ? .... plase help me
 
Make sure the the directory and file that the script is in has the correct permissions and ownter****p. 755 and user:user
 
very nice script, working flawless on a directadmin setup on debian, thanks for the work man !
 
Back
Top