Koozali.org: home of the SME Server

Obsolete Releases => SME 7.x Contribs => Topic started by: gdbs on August 25, 2006, 11:57:59 AM

Title: Sarg and DansGuardian Problem
Post by: gdbs on August 25, 2006, 11:57:59 AM

Hi,

I've installed on my fresh SME 7 Sarg and then DansGuardian...

To make all my users use dansguardian, i've changed the port of the transproxy with this command lignes:

Code: [Select]

db configuration setprop squid TransparentPort 8080

signal-event post-upgrade

signal-event reboot

Everything works fine but i now have a probleme... In Sarg report, it's seems that all internet connexions are considered done by the server:

1   date/time   localhost   57.125   557.136.622   59.15%   2.61%   97.39%   13:51:43   49.903.336   58.52%

And so the squid/access.log say the same thing, for exemple:

1156499740.041    180 127.0.0.1 TCP_MISS/200 5606 GET http://fr.sonofanzine.com/commun/css/news.css - DIRECT/213.186.52.226 text/css

Can you help me to correct that?

Thx

Title: Sarg and DansGuardian Problem
Post by: Franco on August 26, 2006, 04:27:41 AM

Great catch!  :-)

Now edit /etc/sarg/sarg.conf
and change the log location from
/var/log/squid/access.log
to
/var/log/dansguardian/access.log

Fixed!

Title: Sarg and DansGuardian Problem
Post by: gdbs on August 26, 2006, 11:54:44 AM

thx a lot, i'll see tomorow if it works fine!

did you fixed it in your server or in sarg package???

Maybe It would be great to add it in the dansguardian HowTo

Thx again!

Title: Sarg and DansGuardian Problem
Post by: timn on August 26, 2006, 01:34:45 PM

I've noticed the same problem too.

Wouldn't you also need to change the cron job scripts for sarg?

Title: Sarg and DansGuardian Problem
Post by: Franco on August 27, 2006, 05:56:12 PM

Yes,
I had to change a couple more things:
In /etc/dansguardian/dansguardian.conf

Code: [Select]

> # Log File Format
> # 1 = DansGuardian format        2 = CSV-style format
> # 3 = Squid Log File Format      4 = Tab delimited
> logfileformat = 3

I also upgraded my version of sargs (Per this Bug http://bugs.contribs.org/show_bug.cgi?id=1859 )
So now I'm using a newer version of sarg and that also replaced my cron job.

Title: Sarg and DansGuardian Problem
Post by: gdbs on August 28, 2006, 10:48:13 AM

ok!

And where can we find this new package?

It would be great to update the contrib's description of sarg.........

Thx

Title: Sarg and DansGuardian Problem
Post by: Franco on August 28, 2006, 03:24:21 PM

Here is the package:
ftp://fr.rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/sarg-2.2.1-1.el4.rf.i386.rpm
I recommend the upgrade, specially for those that need to collect Dansguardian information.

Title: Sarg and DansGuardian Problem
Post by: ajkeane on August 31, 2006, 09:14:13 AM

Stuntshell thanks for the info. When you did the upgrade did you use nodeps or did you download the required dependancies or enable additional repositories?

Thanks

Tony

Title: Sarg and DansGuardian Problem
Post by: gdbs on August 31, 2006, 10:08:49 AM

I have dependencies error whan I try to upgrade to version 2.2 with your files:

erreur: Dépendances requises:
        gd >= 1.8 est nécessaire pour sarg-2.2.1-1.el4.rf.i386
        libgd.so.2 est nécessaire pour sarg-2.2.1-1.el4.rf.i386
    Résolutions suggérées:
        /home/buildcentos/CENTOS/en/4.0/i386/CentOS/RPMS/gd-2.0.28-4.4E.1.i386.rpm

 :-?

Title: Sarg and DansGuardian Problem
Post by: Franco on August 31, 2006, 03:05:23 PM

being in the same directory where you downloaded the rpm:

Code: [Select]

yum install --enablerepo=base sarg-2.2.1-1.el4.rf.i386.rpm

Title: Sarg and DansGuardian Problem
Post by: ajkeane on September 01, 2006, 02:22:42 AM

Great that got it installed.

I take it you replaced the cron jobs created with the ones from the sarg contrib?

Tony

Title: Sarg and DansGuardian Problem
Post by: Franco on September 01, 2006, 03:28:42 AM

I actually left the one the new rpm created.
I was having problems with squid logs filling up and eventually killing it. So I'm still testing to see which one works better.
The cron from the contrib creates a new file 'access.log.daily'  from access.log , duplicating the size of that directory (until the next cron deletes it). The next day if I have a lot of traffic...
Since now I no longer read from that directory, I can leave it alone and squid seems happy so far.

Thanks,