RE: [squid-users] FATAL: Received Segment Violation...dying.

> -----Original Message-----
> From: squidlist [mailto:squidlist@cookthemail.com]
> Sent: Friday, October 04, 2002 10:12 AM
> To: squid-users@squid-cache.org
> Subject: [squid-users] FATAL: Received Segment Violation...dying.
> Importance: High
>
>
> Hi squid users!!!
>
> I have a HUGE problem and was hoping someone out there would have some
> advise. I am involved in a large squid implementation for my company
> (16,000 plus users). Today we tried to cut our users over
> today and as
> traffic ramped up (around 600 clients on 1 proxy, 5200
> requests per min) the
> squid process died and I found FATAL: Received Segment
> Violation...dying in
> the cache log. These machines hardware did not seem to have
> any problem
> with the traffic but the squid process just could not take
> the load. The
> details on the proxies.
>
> 2 of the following load balaning the traffic
>
> Compaq DL-360 dual 1.3ghz
> 3 GB RAM
> dual scsi 36 GB drives in a mirror RAID
> 15 GB partition for cache
>
> squid 2.4 STABLE 7
> smartfilter 3.1.1
> SUSE 8.0
> compiled with 2.95.3
>
> At first reading the archieves I thought it was a gcc
> optimization issue but
> I found a post the said ./configure auto disables gcc
> optimazation options
> in squid 2.4 STABLE 7. That being said can anyone help me out
> and point me
> in the right direction???? I thought about compiling with a
> new version of
> gcc but since -O was already disabled I have no idea what
> that would even
> do.
>
> I am hoping someone has done this big a squid implementation.
> I am hoping
> squid can handle it and that we can have another win for open source.
>

Hi

I have built squid2.4STABLE6 with Smartfilter 3.1.1 patches successfully
on
Solaris 8.

What you need to supply is the cache.log output up to the failure
and a gdb backtrace from the core file.

Regards
Anthoyn David

>

Notice:
The information contained in this e-mail message and any attached files may
be confidential information, and may also be the subject of legal
professional privilege. If you are not the intended recipient any use,
disclosure or copying of this e-mail is unauthorised. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete all copies of this transmission together with any attachments.
Received on Thu Oct 03 2002 - 19:49:10 MDT