[squid-users] Re: Squid 3.3.6 FATAL: Received Segment Violation...dying.

2013-07-30 Thread x-man
I produced another binary by compiling on another paltform - this time Ubuntu
12.04 and it looks like this new binary doesn't have this problem... strange
enough. 

Compiled with all the same options/flags.





--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-3-6-FATAL-Received-Segment-Violation-dying-tp4661026p4661321.html
Sent from the Squid - Users mailing list archive at Nabble.com.


Re: [squid-users] Re: Squid 3.3.6 FATAL: Received Segment Violation...dying.

2013-07-30 Thread Antony Stone
On Tuesday 30 July 2013 at 11:21:55, x-man wrote:

 I produced another binary by compiling on another paltform - this time
 Ubuntu 12.04 and it looks like this new binary doesn't have this
 problem... strange enough.
 
 Compiled with all the same options/flags.

Which platform did you compile it on the first time, and which platform are you 
running the binary on?


Antony.

-- 
In fact I wanted to be John Cleese and it took me some time to realise that 
the job was already taken.

 - Douglas Adams

 Please reply to the list;
   please don't CC me.


[squid-users] Re: Squid 3.3.6 FATAL: Received Segment Violation...dying.

2013-07-24 Thread x-man
cache.zip
http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4661225/cache.zip  


Hi,

I've attached zipped version of my cache.log file which clearly shows 3
times FATAL: Received Segment Violation...dying.


This session is very small - only 2-3 minutes of traffic for 1000 users, but
same happens in lab tests with 5 users, just it takes more time...

Tested squid 3.3.7 - same is happening.

Squid Cache: Version 3.3.7
configure options:  '--target=x86_64-pc-linux-gnu'
'--host=x86_64-pc-linux-gnu' '--build=x86_64-linux' '--prefix=/usr'
'--sysconfdir=/etc/squid3' '--localstatedir=/var'
'--libexecdir=/usr/lib/squid3' '--disable-maintainer-mode'
'--disable-dependency-tracking' '--disable-silent-rules'
'--datadir=/usr/share/squid3' '--enable-inline' '--enable-async-io=8'
'--enable-storeio=ufs,aufs,diskd' '--enable-removal-policies=lru,heap'
'--enable-delay-pools' '--enable-cache-digests' '--enable-underscores'
'--enable-icap-client' '--enable-follow-x-forwarded-for' '--enable-auth'
'--enable-auth-basic' '--enable-auth-digest' '--enable-auth-ntlm'
'--enable-auth-negotiate'
'--enable-basic-auth-helpers=LDAP,MSNT,NCSA,PAM,SASL,SMB,YP,DB,POP3,getpwnam,squid_radius_auth,multi-domain-NTLM'
'--enable-ntlm-auth-helpers=smb_lm,'
'--enable-digest-auth-helpers=ldap,password'
'--enable-negotiate-auth-helpers=squid_kerb_auth'
'--enable-external-acl-helpers=ip_user,ldap_group,unix_group,wbinfo_group'
'--enable-arp-acl' '--enable-esi' '--enable-zph-qos' '--enable-wccpv2'
'--enable-ecap' '--disable-translation' '--with-logdir=/var/log/squid3'
'--with-pidfile=/var/run/squid3.pid' '--with-filedescriptors=65536'
'--with-large-files' '--with-default-user=proxy' '--enable-linux-netfilter'
'build_alias=x86_64-linux' 'host_alias=x86_64-pc-linux-gnu'
'target_alias=x86_64-pc-linux-gnu'
'CC=/flashos/build64/ct/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-gcc'
'CFLAGS=-pipe -O2 -Wall -march=core2 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -fno-stack-protector
-mno-stackrealign -I/flashos/s64/include -I/flashos/s64/usr/include -fPIE
-fstack-protector --param=ssp-buffer-size=4' 'LDFLAGS=-L/flashos/s64/lib
-L/flashos/s64/usr/lib' 'CPPFLAGS=-pipe -O2 -Wall -march=core2
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-fno-stack-protector -mno-stackrealign -I/flashos/s64/include
-I/flashos/s64/usr/include -D_FORTIFY_SOURCE=2'
'CXX=/flashos/build64/ct/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-g++'
'CXXFLAGS=-pipe -O2 -Wall -march=core2 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -fno-stack-protector
-mno-stackrealign -I/flashos/s64/include -I/flashos/s64/usr/include -fPIE
-fstack-protector --param=ssp-buffer-size=4'
'EXT_LIBECAP_CFLAGS=-I/flashos/s64/usr/include' 'EXT_LIBECAP_LIBS=-lecap'
--enable-ltdl-convenience




--
View this message in context: 
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-3-6-FATAL-Received-Segment-Violation-dying-tp4661026p4661225.html
Sent from the Squid - Users mailing list archive at Nabble.com.


Re: [squid-users] Re: Squid 3.3.6 FATAL: Received Segment Violation...dying.

2013-07-24 Thread Amos Jeffries

On 25/07/2013 2:17 a.m., x-man wrote:

cache.zip
http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4661225/cache.zip


Hi,

I've attached zipped version of my cache.log file which clearly shows 3
times FATAL: Received Segment Violation...dying.



It is unclear from this log what is causing the segment violations. They 
all occur at random different times in the processing and there is also 
an assertion failure in there.


The wiki page Eliezer referenced youto has a script to run a live proxy 
under gdb and obtain stack trace information with minimal downtime to 
your production server users. If you can run your proxy with that script 
please it should produce some more useful information.


Amos