Re: [squid-users] sarg segment fault must clean squid access.log to solved it

From: ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ <mirza.k_at_gmail.com>
Date: Tue, 16 Dec 2008 09:28:08 +0700

happen again

SARG: Making report: 192.168.1.21
SARG: Making report: 192.168.1.2
SARG: Making index.html
SARG: Compressing log file: /var/log/squid/access.log
sh: Compressing: not found
SARG: End

can anyone tell me...
it's totally squid's problem or sarg ?

since the way out from this error is delete access.log

On Mon, Dec 15, 2008 at 9:20 PM, Henrik Nordstrom
<henrik_at_henriknordstrom.net> wrote:
> The information requested is needed for anyone looking into the problem.
>
> Regards
> Henrik
>
> On Mon, 2008-12-15 at 08:17 +0700, ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>> @hendrik :
>> to bad i dont know about C Programming :(
>>
>> @all " any solution : ?
>>
>> On Sun, Dec 14, 2008 at 5:54 AM, Henrik Nordstrom
>> <henrik_at_henriknordstrom.net> wrote:
>> > On Fri, 2008-12-12 at 17:55 +0700, ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>> >> SARG: Reading access log file: /var/log/squid/access.log
>> >> Segmentation fault
>> >
>> > Should be easy to fix if you know a little C programming. Or even if you
>> > don't collect information on the crash and post them hoping that someone
>> > else picks up the task..
>> >
>> > gdb /path/to/sarg
>> > run -x
>> > [wait for crash]
>> > backtrace
>> >
>> >> - some ppl maybe use sarg and have this problem too
>> >
>> > Quite likely.
>> >
>> >> - ( maybe ) this problem can be prevent from squid.conf ?
>> >
>> > Possible, but better to fix sarg I think.
>> >
>> > Regards
>> > Henrik
>> >
>> >
>>
>>
>>
>
>

-- 
-=-=-=-=
http://amyhost.com ( webhosting dengan budget terbatas )
Hot News !!! :
Pengin punya Layanan SMS PREMIUM ?
Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
Received on Tue Dec 16 2008 - 02:28:17 MST

This archive was generated by hypermail 2.2.0 : Tue Dec 16 2008 - 12:00:01 MST