Re: [squid-users] Segment violation in 3.4.5

2014-05-06 Thread Kinkie
Unfortunately this report is still short on details. Could you try to follow the procedure explained in http://wiki.squid-cache.org/SquidFaq/BugReporting#Using_gdb_debugger_on_Squid and obtain a backtrace? Thanks! On Tue, May 6, 2014 at 3:12 AM, Dan Charlesworth d...@getbusi.com wrote: Hi

[squid-users] Segment violation in 3.4.5

2014-05-05 Thread Dan Charlesworth
Hi folks We just compiled an EL6 x86_64 RPM for the 3.4.5 update and are now receiving the “Segment violation…dying” error for every request. We’re using the same configuration and config options we have been for every 3.4 release so far, with the only change being the addition of

[squid-users] Segment Violation.

2005-06-16 Thread Danish Khan
Hi I m using sun linux with latest patch updated. It gives Received Segment Violation...dying. in cache log and squid stop serving requests. Kindly help my squid version is squid 2.5 stable 7 with following options. --enable-snmp --enable-htcp --enable-linux-netfilter --enable-uderscores

Re: [squid-users] Segment Violation.

2005-06-16 Thread Henrik Nordstrom
http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19 and please don't start new threads by replying to an existing message. Your question may get lost if you do so as it gets associated with the thread you responded to.. On Thu, 16 Jun 2005, Danish Khan wrote: Hi I m using sun linux

[squid-users] Segment Violation...dying.

2004-02-06 Thread squid
2004/02/06 09:19:37| WARNING: Closing client 137.198.232.157 connection due to lifetime timeout 2004/02/06 09:19:37| http://64.12.163.130/monitor?sid=400ca38289c6027e014c078014c3f858 FATAL: Received Segment Violation...dying. 2004/02/06 09:19:39| ctx: enter level 0:

Re: [squid-users] Segment Violation...dying.

2004-02-06 Thread Henrik Nordstrom
On Fri, 6 Feb 2004, squid wrote: 2004/02/06 09:19:37| WARNING: Closing client 137.198.232.157 connection due to lifetime timeout 2004/02/06 09:19:37| http://64.12.163.130/monitor?sid=400ca38289c6027e014c078014c3f858 FATAL: Received Segment Violation...dying. 2004/02/06 09:19:39| ctx: enter

[squid-users] Segment Violation

2003-06-23 Thread Daniellek
Tonight during logfile rotation squid died mysteriuosly: 2003/06/22 00:00:03| storeDirWriteCleanLogs: Starting... 2003/06/22 00:00:03| 65536 entries written so far. 2003/06/22 00:00:03|131072 entries written so far. 2003/06/22 00:00:03|196608 entries written so far. 2003/06/22

Re: [squid-users] Segment Violation

2003-06-23 Thread Robert Collins
Daniellek wrote: But there's no core file... Is it possible that squid: 1. Didn't create core? Yep. There is a FAQ entry on getting cores :}. I suggest you read that.. so you can be ready if this problem reoccurs. Cheers, Rob

Re: [squid-users] Segment Violation

2003-06-23 Thread Daniellek
W dniu Mon, Jun 23, 2003 at 08:38:06PM +1000, Robert Collins wystuka(a): Yep. There is a FAQ entry on getting cores :}. I suggest you read that.. so you can be ready if this problem reoccurs. Stupid thing, i've got ulimit -c 0 :-) So, I'll wait till next time, hopefully with core. Thanks for

Re: [squid-users] Segment Violation

2003-06-23 Thread Ethy H. Brito
On Mon, 23 Jun 2003, Daniellek wrote: There is a bug report I opened a few days ago about a very similar problem. I still got no answers from the developers about that dispite the fact it is stated as critical with priority 2. Check BUGZILLA database #680 at squid site. Regards Tonight during