Web Hosting Talk







View Full Version : Webalizer Version 1.30 not working right on my Raq3


Gigs
10-19-2000, 11:13 PM
I have Webalizer Version 1.30 on my raq3 and its not tracking right on one site that gets alot of hits and on the other small sites i have it's working does anyone know why it would be doing this?

For the large site the stats hasnt been updated since Oct 14 and it tracked part of the 15 it's only showing stats for thouse 2 days.

On the samll sites its only showing stats for Oct 18 and the 19 wich is up to date.

What should i do? :)

Ironlung
10-19-2000, 11:42 PM
We use webalizer on our Cobalts as well and only have this problem with the cleints that use FrontPage extensions. You might want to check that out if you are offering FPX. If you find a solution outside of this post please post it for me use. Thank you

Gigs
10-20-2000, 12:27 AM
I don't use FrontPage extensions on any of the sites and i have no idea of what FPX is? I have no idea of what could be wrong.

Gigs
10-20-2000, 12:29 AM
never mind about the FPX i know what that is duh! lol

Gigs
10-20-2000, 05:25 PM
can anyone help?

guest
10-20-2000, 07:46 PM
I dont know if this will help out or not. I pulled it from the manual at http://cpanel.darkorb.net/.


Q: Stats don't update.
A: Stats are updated every X days. Where X is the number you
have configured for the cycle in /var/cpanel/cpaneld.config. The default
value is 2 days. However stats will not get updated unless there is some
free cpu time on the server. Log Files only get analyzed when the
server's cpu is mostly idle. This is to prevent slow downs to normal
service. If stats seem like they never update, you might want to decrease
the cycle. If you still have no luck you probably have a very busy
machine and it would do best to upgrade the cpu as soon as possible.

Gigs
10-20-2000, 10:22 PM
It's still doing the same thing it's working right on sites that get 2,000 hits a day and tracking daily but on another site that gets 5,000 + hits a day it stoped working on Oct 15. I wonder what would happen if i just deleted the stats directory for the site that its not working on would that hurt anything? I guess it would just start over.

JTY
10-20-2000, 11:08 PM
You may have file system permission wrong, depending on what user webalizer is running as. Since it needs write permission to the stat directory.

Gigs
10-21-2000, 01:41 AM
I checked that to JTY it has permission to.

Gigs
10-23-2000, 12:17 PM
anyone out there? I rebooted my raq and it tracked again for a day and a half and it looks like it has stoped again.

Chicken
10-23-2000, 12:39 PM
Check the master access logs and see whether the RaQ is writing logs. If so, check the site's logs and see if that is being written. I had a problem where it wasn't splitting the logs off into the individual site's stats directories. The main access log was errrr... logging, heh, but it wasn't splitting the logs to the individual sites. Why I didn't post this, was that this was happening for all of the sites, not just one, so it didn't sound like the same problem.

My guess though is that it isn't a webalizer problem, and that the server isn't writing/splitting logs for your site in the first place (thus webalizer has nothing to webalize).

Félix C.Courtemanche
10-23-2000, 01:07 PM
I suggest an other answer...

The raq will do the log swapping for the GUI stats BEFORE doing the webalizer ones... so if your site has a lot of hits and have the log rotated daily, webalizer will only see blank logs all the time, so it won't update anything...

A solution for that... would be to hack the log rotation script and make sure webalizer is ran before they are rotated. I never actually did that, so I can only suggest.

the webalizer script is in /etc/cron.daily
if you edit your /etc/crontab file, and put webalizer before, it might work. But since cobalt is splitting up the logs itself (not using apache for it) it might as well not be doable and have no fix.

Gigs
10-23-2000, 02:00 PM
i have no idea of how to do the things you guys just said, i guess i will just have to leave it be. If i leave it like it is forever it wont hurt anything will it? thanks for the help!

Gigs
10-28-2000, 12:01 PM
.

Félix C.Courtemanche
10-28-2000, 02:51 PM
no, nothing won't be hurt by something not working :)

A server is not a big pile of software melted together... its extremely modular, and unless you really messed up when setting up webalizer, it won't affect anything.

Gigs
10-28-2000, 10:17 PM
I didn't really install it all i did was point to the url it was at on the cobalt site. I was just wondering if it would hurt anything not tracking right i guess thats a dumb question but im new at this and know nothing it's still doing the same tracking the sites that dont get many hits and on the one that gets alot of hits it just dosent track at all so should i just leave it be or have my host uninstall it? I dont want any down time of course :)

Gigs
10-28-2000, 10:44 PM
Another problem i have is Webalizer says i use 1112430 KBytes a day (when it works for a day) wich is right because i used to be on a virtual sever and theres said the same amount but the RaQ says for Total web usage only 3GB well 1112430 KBytes is alittle over 1GB correct? I use that amount everyday my traffic dosnt change so why does the raq say 3GB? If i go click on web and at the very bottom it says 3867599141 Bytes Transferred i have no idea of how many GBs that is? or thats for just this month or for the hole time i've had the raq for Period Covered it only says Oct 27-28

Keeg
10-29-2000, 12:41 AM
first off the answer is simple logs on raq's dont work that well :)
now the solution.(sort of)
first thing you have to do is make sure your masterlog located at /home/log/httpd/access is rotating properly it should have todays date on that file at all times. if that log ever reaches 81 megs in a day it will not rotate properly or at all. i have a cobalt engineer working with me to correct this problem on raq 3's and 4's he promised me we will have a working solution in a 2 week time frame. the current problem is caused by the way they have chopped up analog so it wont read the masterlog properly and causes parsing errors. when this happens logging and stats stop working. if you want the fix send me a quick email telling me you want it and as soon as he delivers ill toss it your way.

Steve
steve@tera-byte.com

Gigs
10-29-2000, 12:01 PM
okay thanks but will it hurt anything for me to leave it like it is?

Félix C.Courtemanche
10-29-2000, 02:40 PM
no but you won't have accurate stats.