Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

H. Bases on this log, issue occurs in ICAP processing. Most close to this: http://bugs.squid-cache.org/show_bug.cgi?id=4597 As I can remember, this bug occurs on ECAP, not with ICAP. Configuration was like you, chained ecap+icap services. Sadly, I can't show patch for 3.5, especially it was

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

And the gd backtrace: Warm Regards, - Bug Reporter Contributor OpenSource = Open-Minded -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Chaining-icap-and-ecap-services-FATAL-Received-Segment-Violation-dying-tp4683033p4683040.html Sent from the Squid

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

Yes I had some issue with ecap-gzip (related to chunked content) that I have already resolved by bypassing chunked content (I modified the code). Now I have no issue with ecap-gzip when it's used alone (without being in a chain). Herewith the log file (debug_options ALL,3): squid.gz

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

Also it can be issue with ecap-gzip adapter itself. AFAIK it has opened issue with segfault on some sites. Public version has not close this bug because of author abandoned project. 10.07.2017 0:54, bugreporter пишет: > Thank you for your prompt response Yuri. Below information that you have > r

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

10.07.2017 0:54, bugreporter пишет: > Thank you for your prompt response Yuri. Below information that you have > requested: > > - Squid 3.5.26 > - Linux kernel 3.10.100 on an LFS (Linux From Scratch) > - gcc-4.8.1, glibc-2.18 > > Don't yet have a core dump. Are you interested in having the log fi

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

Thank you for your prompt response Yuri. Below information that you have requested: - Squid 3.5.26 - Linux kernel 3.10.100 on an LFS (Linux From Scratch) - gcc-4.8.1, glibc-2.18 Don't yet have a core dump. Are you interested in having the log file in debug mode? Cheers - Bug Reporter Contr

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

Details. Squid's version, OS version, compiler version, core dump contents. 09.07.2017 22:59, bugreporter пишет: > Hi, > > Is it allowed (supported) to chain icap and ecap services (using > /adaptation_service_chain/)? I get a "FATAL: Received Segment > Violation...dying." when trying to do it wi

[squid-users] Squid 4.0.21 beta RPM's are out.

Squid 4.0.21 beta RPM's are out for: CentOS 7, Oracle Enterprise Linux 7, SLES 12SP1 http://ngtech.co.il/repo/centos/7/beta/ http://ngtech.co.il/repo/oracle/7/beta/ http://ngtech.co.il/repo/sles/12sp1/beta/ With hope that it will help to move faster from beta to stable. All The Bests, Eliezer -

[squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

Hi, Is it allowed (supported) to chain icap and ecap services (using /adaptation_service_chain/)? I get a "FATAL: Received Segment Violation...dying." when trying to do it with some websites (www.linguee.com for instance). Each of those services works very well separately. Maybe this has never be

[squid-users] [squid-announce] Squid 4.0.21 beta is available

The Squid HTTP Proxy team is very pleased to announce the availability of the Squid-4.0.21 release! This release is a bug fix release resolving several issues found in the prior Squid releases. The major changes to be aware of: * Regression Bug 4492: Chunk extension parser is too pedantic Wi