AwStats plugin for DA [Still in BETA]

Wouter said:
Great plugin :).

Only 1 thing: on new domains Awstats isn't turned on automaticly, do you know how I can do this? Thanks!
Automatically nope, manually yeah:
Admin level > awstats plugin > select all new users so that all users that should have access are checked and save :)
 
Awstats LogFile config

I have a problem with the default configuration of the awstat LogFile parameter.
It is set to :
/var/log/httpd/domains/xxxx.log

But for dome of the websites (whitch have big logs) this log file is a temporary log file and the final logs directory are :
home/xxxx/domains/xxxx/logs/

And there is several .tar.gz file per month

Must I use logresolvemerge.pl ?
Must I modify all config files manualy ?
Why is my configuration diferent ?

Thanks
Laurent
 
Hmm... my awstats have seem to have stopped updating by themselves. Whenever I try to do a manual update, I get the following error message (on ALL domains):

Error: An AWStats update process seems to be already running for this config file. Try later. If this is not true, remove manually lock file '/tmp/awstats.mydomain.com.lock'.

OS: FreeBSD 5.3
DA: 1.24.2

Removing the lock file and waiting overnight for the statistics to update by themselves proved to be futile.

This started a week ago, when I noticed my statistics stopped updating. Checking out the log files, there seems to be no indication that the crontab job has failed. If I run the awstats_updateall.pl script on my own, it just stalls (forcing me to CTRL+Break). It looks like it's taking some time to update.

This is what I have in my crontab:
30 0 * * * root /usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats_updateall.pl now -awstatsprog=/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl

Even if I insert the one-line update command (which has been suggested at the top of this thread) it does not change a thing.

Again, all was working well last week. I haven't tampered with anything on my server really. Even manual updates worked when I needed to. Could it be that my log files are simply too big? My site does about 20GB of transfer a day (10,000+ hits daily) so I could see the log files increasing in size rather quick, but I don't think this should be a problem. Any help is appreciated!
 
Problems with install

I run the install just fine and do the alldomains.php. However, it seems that whatever happens to the .htaccess file doesnt allow me to run the awstats.pl from www.mydomain.com/awstats/awstats.pl. But if I copy the awstats.pl to the cgi-bin directory it runs fine but doesnt link the graphics right. Is there something I am doing wrong?

Thanks

Bryan
 
Hi, great plugin here. Installed perfectly through the DA menus and such.

I just get 403 with

"You don't have permission to access /awstats/ on this server.

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

soo yeah... no errors popped up, so i don't know what i've done wrong.
 
awstats & webalizer showing diff data

I have set up awstats and noticed that the stats are completly different than the stats showing in webalizer.
 
Sorry for the late reply's! As stated support is minimum to none!

mattbates

config= is disabled. you can think of a million ways why :)
If a user protects his stats dir, another user could just access it through his awstats!

Generic ? Yes, but that involves DA to implement it :) Will they do it ? NO!
Why ? I asked them and provided them with enough info on various emails. So I gave up!

Icheb and others with these questions

Add it to the standard DA domain_creation.sh or whatever this file is called
to do something like echo "$USERNAME" >> /usr/.../awstats/.../permissions.txt or whatever :)

Check DA's POST Scripts.

Laurent, mmx, nhwebgroup and others

The logs are rotated nightly by DA. This will run into problems if you have large amount
of traffic on some domains. Use the cron job and run it before the tally=all (see first post!!)

All problems related to strange, incomplete or even no stats is because of log rotation or incorrect
log format in apache and the one specified in the config files in /etc/awstats

RakeCommunity

The .htaccess causes to set the awstats.pl as the standard document for that dir.
So /awstats/ will be /awstats/awstats.pl

And it enables CGI for that dir, like it is in CGI-BIN.

Do you have altered apache confs ?? Check the created .htaccess etc.

TiD

Check your httpd error log for that domain /var/log/httpd/domains/[domain].error.log or whatever it's called

caribk

Again awstats has proven to have a lazy way to handle their plugins. As I removed a lot of the plugin sh*t in the
script it could be I've missed some in the 6.4 that the plugin uses. I'll check on it and deliver an update if necesary
 
Follow-Up

Final email send to DirectAdmin support about this plugin and their implementation.

I think they will probably not respond as in my various earlier mails the last year!

What will hapen ?

I will probaly quit supporting this topic (after the next update: see above) and discard any PM's, Emails etc. about this plugin. At later time the plugin probably end up in my archive.

Why ?

DA can implement my plugin transparantly into DA and this will cause a lot of problems we all bump into to disapear. The installment scripts and other changes that are done by the Plugin (whole installation almost) isn't needed when it can be setup globaly with the right httpd.conf template.

As you can understand, I'm working around the DA panel to get this plugin working. Most things are just to get it running so the panel doesn't mess it up or conflict with it.

I hope john or any other support staff will show some interest as John did in the first bricks of the plugin.
 
NO you can't stop supporting it!

DA team needs to answer your call!!

AWSTATS is FAR better than webalizer!!!

The NEED to make this part of the standard!!!

PLEASE RALLY THE TROOPS!!!!!

All in favor say aye
 
Last edited:
"I" is a personal pronoun.

"aye" is what you say if you're in favor.

So far, I'm against. "nay".

Why?

Because if I push DA staff to work on things they've chose not to work on then they're going to have to put off something they think is important.

Telling me that AW Stats is better without telling me in what way it's better certainly doesn't convince me.

I've been told that AW Stats causes a large machine load. Is that true? Is it damaging? Is there a certain size machine, under which perhaps it shouldn't be run on?

Jeff
 
The error i saw was:

(13)Permission denied: access to /awstats/awstats.pl failed because search permissions are missing on a component of the path

and i wouldn't know how to fix it
 
TiD said:
The error i saw was:

(13)Permission denied: access to /awstats/awstats.pl failed because search permissions are missing on a component of the path

and i wouldn't know how to fix it
`

chmod 755 awstats.pl
chown user:user awstats.pl
 
jlasman

I can't really understand your nay and aye's :p

So far John has nicely replied and will take a look at it, when time is available. What I can remember, John would look at it a year ago when he had time available.

But that were different times ;) I'm confident that they will put it on a higher level.
 
TiD said:
did that a while ago and it still doesn't work.

Sorry to be a problem.

ls -la your public_html and what permissions does the awstats dir has ?

ls -la your awstats.pl and what permissions does this has ?
 
lrwxrwxrwx 1 admin admin public_html
-rwxr-xr-x 1 admin admin awstats.pl
 
That's the wrong directory probably !?!

Ex.:

User test01 on your server has domain test.nl and test.com

http:// test.nl/awstats/ doesn't work ???

Check /home/test01/domains/test.nl/public_html/awstats
 
If i log into it via ftp, i can see it right there under public_html/awstats/awstats.pl with a around four or so folders that are shortcuts.
 
Back
Top