On Jul 18, 2020, at 11:15 PM, Alex Rousskov wrote:
> I would try building the previous one again, using the exact same
> procedure as you are using to build the new executable. Does the freshly
> rebuilt old executable start OK? If yes, rebuild the new one from a
> fresh directory. Just in case.
On 7/18/20 11:43 AM, Gabor Berczi wrote:
> newly compiled squid executables don't
> start. The previous one does. Where do I start looking?
I would try building the previous one again, using the exact same
procedure as you are using to build the new executable. Does the freshly
rebuilt old
On Jul 18, 2020, at 7:59 PM, Amos Jeffries wrote:
Are you building in a clean build directory from a clean set of
sources?
Yes.
What OS are you building on?
FreeBSD 8.4 amd64 but all of it is irrelevant. I know this is PEBKAC,
but what I'm interested in is where/why. Already tried
On 19/07/20 3:43 am, Gabor Berczi wrote:
> Greets.
>
> I've fucked up something and now newly compiled squid executables don't
> start. The previous one does. Where do I start looking?
>
Are you building in a clean build directory from a clean set of sources?
What OS are you building on?
Are
Greets.
I've fucked up something and now newly compiled squid executables
don't start. The previous one does. Where do I start looking?
Assertion failed: (aLabel != NULL && aSize), function
MemImplementingAllocator, file MemPool.cc, line 394.
Program received signal SIGABRT, Aborted.
On 10/22/19 3:24 PM, Antonio SJ Musumeci wrote:
> Squid 4.8
>
> Attempting to get a SMP setup with rock enabled. Instance points to an
> origin web server.
>
> With "workers 1" everything appears to work fine. If I set "workers 2" I
> get a number of issues:
>
> If I request a particular object
Squid 4.8
Attempting to get a SMP setup with rock enabled. Instance points to an
origin web server.
With "workers 1" everything appears to work fine. If I set "workers 2" I
get a number of issues:
If I request a particular object a kid will fail with:
assertion failed: Controller.cc:838:
com]
>> Verzonden: donderdag 2 augustus 2018 17:43
>> Aan: L.P.H. van Belle; squid-us...@squid-cache.org
>> Onderwerp: Re: [squid-users] assertion failed
>>
>> On 08/02/2018 07:46 AM, L.P.H. van Belle wrote:
>>
>>> If i google for "assertion failed:
sr/sbin/squid || /usr/sbin/squid
-k rotate
fi
endscript
Best regards,
Louis
> -Oorspronkelijk bericht-
> Van: Alex Rousskov [mailto:rouss...@measurement-factory.com]
> Verzonden: donderdag 2 augustus 2018 17:43
> Aan: L.P.H. van Belle; squid-us...@squid-cache.org
> Onde
On 08/02/2018 07:46 AM, L.P.H. van Belle wrote:
> If i google for "assertion failed: comm.cc:428: "!isOpen(conn->fd)"
> i get only 3 hits, is someone knows what this is, because i cant figure
> this out.
When facing an assertion, one should check Squid bugzilla:
Hai,
Im testing squid 4.1 on Debian Stretch, i've rebuilded the Debian Sid 4.1 to
Stretch.
Everything looks good, i only see one failed line in cache.log ( see below. )
this is the default configuration, only 1 change made.
in debian we have : /etc/squid/conf.d/debian.conf
# Squid
On 28/03/18 02:22, Amos Jeffries wrote:
On 28/03/18 03:24, Alex Crow wrote:
I have a squid 4.0.22 running peered with a 3.5.24 proxy. The latter
machine stopped responding and I had to reboot it, and then the 4.0.22
one crashed. Here's a log snippet:
2018/03/27 15:01:48 kid1| WARNING: failed
On 28/03/18 03:24, Alex Crow wrote:
> I have a squid 4.0.22 running peered with a 3.5.24 proxy. The latter
> machine stopped responding and I had to reboot it, and then the 4.0.22
> one crashed. Here's a log snippet:
>
> 2018/03/27 15:01:48 kid1| WARNING: failed to unpack metadata because
> store
I have a squid 4.0.22 running peered with a 3.5.24 proxy. The latter
machine stopped responding and I had to reboot it, and then the 4.0.22
one crashed. Here's a log snippet:
2018/03/27 15:01:48 kid1| WARNING: failed to unpack metadata because
store entry metadata is too big
2018/03/27
On 04/06/17 19:27, alexander lunev wrote:
Hello everyone!
I have two almost identical cache servers, both FreeBSD 10.3, both
running latest squid-3.2.25 from ports in transparent mode, one runs
OK and another is throwing this error:
Do you mean 3.5.25? (3.2 series ended at 3.2.14)
Hello everyone!
I have two almost identical cache servers, both FreeBSD 10.3, both
running latest squid-3.2.25 from ports in transparent mode, one runs OK
and another is throwing this error:
2017/06/04 10:19:08 kid1| storeLateRelease: released 0 objects
2017/06/04 10:19:19 kid1| assertion
On 13/07/2016 1:33 a.m., Omid Kosari wrote:
> Hello,
>
> squid crashes after following error
> assertion failed: DestinationIp.cc:41: "checklist->conn() &&
> checklist->conn()->clientConnection != NULL"
>
>
> From the error massage i guess that following config may cause the problem
>
> #acl
Hello,
squid crashes after following error
assertion failed: DestinationIp.cc:41: "checklist->conn() &&
checklist->conn()->clientConnection != NULL"
From the error massage i guess that following config may cause the problem
#acl download_until_end_by_ip dst 13.107.4.50
acl freetimes time
On 24/02/2016 5:37 a.m., William Lima wrote:
> Hi all,
>
> It's easy to make a DoS. The reply (and cause) of the problem of the
mentioned link:
>
William; Please do not do that again. The squid-bugs mailing list is for
(private) discussion of security related issues like attack PoC. This
attack
Hi Folks,
I'm running squid 3.5.14 on slackware linux 64 bit (compiled from source).
When users connect to http://www.oggi.it/global_assets/js/plugins.js?v=1.6
squid crash with the following message:
assertion failed: String.cc:174: "len_ + len < 65536"
I have seen the same error on this
Hello,
I did an upgrade from 3.5.8 to 3.5.11 and now sometimes I get the
message:
assertion failed: client_side.cc:819: "areAllContextsForThisConnection()"
in cache.log and squid dies.
Is this a known problem or shall I create a bugreport ?
--
Regards
Dieter
--
I do not get viruses
On 08/04/2015 04:27 PM, HackXBack wrote:
I'm not sure how to fix that. then who should i talk to..
you guys should dig in source and found out
Yes, somebody should dig in source and fix the bug. However, Amos (or
anybody else providing free support on this mailing list) is _not_
obligated
I'm not sure how to fix that. then who should i talk to.. you guys
should dig in source and found out its important tks any should i ask
outside ??
--
View this message in context:
On 30/06/2015 7:57 p.m., HackXBack wrote:
i copy from normal log to the assertion error\
is this enough or you need more ?
Its leading me to a very horrible conclusion. This appears to be a
pinned connection with two transactions trying to read data out of the
server connection simultaneously.
i copy from normal log to the assertion error\
is this enough or you need more ?
Thanks Amos.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670979p4671959.html
Sent from the Squid -
2015/06/30 10:09:38.432 kid1| Acl.cc(138) matches: checking always_direct
2015/06/30 10:09:38.432 kid1| Acl.cc(138) matches: checking always_direct#1
2015/06/30 10:09:38.432 kid1| Acl.cc(138) matches: checking fakespeed
2015/06/30 10:09:38.432 kid1| RegexData.cc(51) match: aclRegexData::match:
On 29/06/2015 10:56 p.m., HackXBack wrote:
i gave you backtrace report and i gave you my configure option ?
what else you want from me ?
The backtrace shows where the assert is from. But without those symbols
the gdb cant seem to find in your builds we cant debug what state the
transaction is
On 29/06/2015 3:40 p.m., HackXBack wrote:
what you supposed me to do Amos, !!
Not sure. I have not been able to replicate or identify the source of
the problem you are having.
Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
dear friend, your conf make the same problem, and i dont have
half_closed_clients in my conf !
and this is my configure option maybe the problem from it ...
./configure --prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
--libexecdir=/usr/lib/squid --sysconfdir=/etc/squid --localstatedir=/var
Better to use:
# Adobe/Java and other updates
acl adobe_java_updates urlpath_regex /usr/local/squid/etc/urlregex.updates
# Youtube CDN store rewrite ACLs
acl store_rewrite_list urlpath_regex
\/(watch\?|get_video|videoplayback\?)
\.(jp(e?g|e|2)|gif|png|tiff?|bmp|ico|webp|flv|f4f|mp4)\?
acl Y-TUBE dstdomain .googlevideo.com
range_offset_limit -1 Y-TUBE
this conf make the assertion bug,
we need a solution
am still waiting Amos
Thanks.
--
View this message in context:
i install 3.5 and still the same problem ,
this assertion error exist when i use
acl partial dstdomain .googlevideo.com
acl partial dstdomain .youtube.com
acl partial dstdomain .mgccw.com
range_offset_limit none partial
--
View this message in context:
this patch didnt solve the problem :)
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670979p4671832.html
Sent from the Squid - Users mailing list archive at Nabble.com.
used the latest squid 3.5.5 and still the same assertion error
where is the patch for this bug ??
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670979p4671827.html
Sent from the
OK. I went back to 3.4.13 for prod. I will try upgrading one proxy this
weekend.
On Wed, Jun 10, 2015 at 12:11 PM, Amos Jeffries squ...@treenet.co.nz
wrote:
On 10/06/2015 5:24 a.m., Michael Pelletier wrote:
Hello,
I am getting these errors on 3.5.5 any ideas? Here is my build
I can try. I only saw it once under heavy load. I will see what I can do...
Michael
On Thu, May 14, 2015 at 12:40 AM, Amos Jeffries squ...@treenet.co.nz
wrote:
On 14/05/2015 9:34 a.m., Michael Pelletier wrote:
Squid does recover. What do you think?
I think its a bug that needs fixing.
I am running 3.4.12
On Wed, May 13, 2015 at 3:23 PM, Amos Jeffries squ...@treenet.co.nz wrote:
On 14/05/2015 5:42 a.m., Michael Pelletier wrote:
Hello,
What does this warning mean?
assertion failed: DestinationIp.cc:64: checklist-conn()
checklist-conn()-clientConnection != NULL
Squid does recover. What do you think?
On Wed, May 13, 2015 at 5:25 PM, Michael Pelletier
michael.pellet...@palmbeachschools.org wrote:
I am running 3.4.12
On Wed, May 13, 2015 at 3:23 PM, Amos Jeffries squ...@treenet.co.nz
wrote:
On 14/05/2015 5:42 a.m., Michael Pelletier wrote:
Hello,
What does this warning mean?
assertion failed: DestinationIp.cc:64: checklist-conn()
checklist-conn()-clientConnection != NULL
Michael
--
*Disclaimer: *Under Florida law, e-mail addresses are public records. If
you do not want your e-mail address released in response to a public
On 14/05/2015 9:34 a.m., Michael Pelletier wrote:
Squid does recover. What do you think?
I think its a bug that needs fixing.
Can you get a trace of what ACLs is being tested using debug_options
28,5 ?
Amos
___
squid-users mailing list
but am not ready now to use 3.5.4
can i use this patch on 3.4 without any problem ?
Thanks Amos.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670979p4671104.html
Sent from the Squid -
Thanks you amos for giving time,
but about this part :
for looping 302 on youtube
acl text-html rep_mime_type text/html
acl http302 http_status 302
store_miss deny text-html
store_miss deny http302
send_hit deny text-html
send_hit deny http302
i use this config with patch file to make
On 3/05/2015 10:59 a.m., HackXBack wrote:
Thanks you amos for giving time,
but about this part :
for looping 302 on youtube
acl text-html rep_mime_type text/html
acl http302 http_status 302
store_miss deny text-html
store_miss deny http302
send_hit deny text-html
send_hit deny
squid.conf you can see it all , and the answer on your question is no i dont
have .
# should be allowed
acl localnet src 10.11.20.0/24
acl localnet src 10.150.15.0/24
# ACL for rewriter
acl fakespeed url_regex -i
\.*(speedtest|espeed).*\/((latency|random.*|upload)\.(jpg|txt|php)).*
acl
On 1/05/2015 10:09 p.m., HackXBack wrote:
squid.conf you can see it all , and the answer on your question is no i dont
have .
Actually the answer was yes.
ssl_bump server-first all
Which is good news. The bug will probably disappear when you move to the
3.5.4 version. Which will be
On 1/05/2015 10:09 p.m., HackXBack wrote:
squid.conf you can see it all , and the answer on your question is no i dont
have .
Okay, a bit of an audit...
# should be allowed
acl localnet src 10.11.20.0/24
acl localnet src 10.150.15.0/24
# ACL for rewriter
acl fakespeed url_regex -i
Hi Nathan,
Thanks for the reply, I applied the latest build (squid.3.5.3-r13808),
waiting for the client to check if it fixed or not
Bye Fred
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-557-F-flags-open-tp4670788p4670935.html
root@issa:~# netstat -anl | grep 80 | awk '/^tcp/ {t[$NF]++}END{for(state in
t){print state, t[state]} }'
FIN_WAIT2 12
LISTEN 1
CLOSE_WAIT 3
TIME_WAIT 809
ESTABLISHED 597
LAST_ACK 9
SYN_SENT 4
FIN_WAIT1 14
--
View this message in context:
root@fibernet:~# netstat -anl | grep 80 | awk '/^tcp/ {t[$NF]++}END{for(state
in t){print state, t[state]} }'
FIN_WAIT2 1
LISTEN 1
CLOSE_WAIT 7
TIME_WAIT 71
ESTABLISHED 125
LAST_ACK 2
FIN_WAIT1 2
Every 2.0s: netstat -antop | grep -iE --regexp=TIME_WAIT
Hi Fred,
I believe you're experiencing bug 3329:
http://bugs.squid-cache.org/show_bug.cgi?id=3329
Please try the patch that I have on there and see if that helps your issue.
Thank you,
Nathan.
On 17 April 2015 at 17:06, Stakres vdoc...@neuf.fr wrote:
Hi All,
Is anyone with an trick
i installed squid from source code
http://www.squid-cache.org/Versions/v3/3.4/squid-3.4.12-20150414-r13219.tar.gz
this is my configure option
./configure --prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
--libexecdir=/usr/lib/squid --sysconfdir=/etc/squid --localstatedir=/var
--libdir=/usr/lib
[New LWP 20933]
[New LWP 20907]
[New LWP 20918]
[New LWP 20922]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by `(squid-1) -YC -f
As I mentioned earlier, this hasn't worked the because the debug
symbols you're running gdb against don't quite match the binary in
which the crash occurred. I would check the version of the debug
symbols you're running gdb against versus the version of the squid
binary that was installed. These
Hi All,
Is anyone with an trick regarding this error message in the cache.log ?
*assertion failed: comm.cc:557: F-flags.open*
Squid *3.5.3-20150415-r13798*.
config in diskd, tproxy and ssl_bump.
when the squid faces this error, it reloads itself but it breaks the surf
for a while.
Thanks in
On 17/04/2015 1:12 a.m., HackXBack wrote:
i changed the squid version to last updated one
squid-3.4.12-20150414-r13219
and also the same assertion error ...
Good. Now you can start working on what the assertion is secure in the
knowledge that the ssl_crtd corruption is not getting subtly in
i changed the squid version to last updated one
squid-3.4.12-20150414-r13219
and also the same assertion error ...
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670726p4670781.html
Thank you Amos for answer,
but can you please tell me what may cause this assertion error so i can
solve it ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670726p4670785.html
Sent from
this bug exist after changing in certificate_db.cc from flock to lockf
=== modified file 'src/ssl/certificate_db.cc'
--- src/ssl/certificate_db.cc 2014-12-03 11:58:37 +
+++ src/ssl/certificate_db.cc 2015-01-09 10:27:12 +
@@ -55,7 +55,7 @@
#if _SQUID_WINDOWS_
if (!LockFile(hFile,
same issue with your patch , this didnt solve the problem and i still have it
..
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670726p4670737.html
Sent from the Squid - Users mailing
am running squid 3.4.12 under debian7
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/assertion-failed-comm-cc-178-fd-table-conn-fd-halfClosedReader-NULL-tp4670726p4670749.html
Sent from the Squid - Users mailing list archive at Nabble.com.
What version of Squid are you running, and in what environment?
Based on the fact that the output of the gdb backtrace doesn't show
function parameters (debug symbols don't quite match up to the
binary), this may not work, but if you could run these commands in gdb
and show the output, that would
Hello,
I believe you're experiencing bug 3329:
http://bugs.squid-cache.org/show_bug.cgi?id=3329
Please try the patch that I have on there and see if that helps your issue.
Thank you,
Nathan.
On 15 April 2015 at 07:16, HackXBack hack.b...@hotmail.com wrote:
[New LWP 4677]
[New LWP 4704]
[New LWP 4677]
[New LWP 4704]
[New LWP 4687]
[New LWP 4702]
[New LWP 4695]
[New LWP 4725]
[New LWP 4697]
[New LWP 4490]
[New LWP 4493]
[New LWP 4473]
[New LWP 4508]
[New LWP 4495]
[New LWP 4460]
[New LWP 4511]
[New LWP 4516]
warning: Can't read pathname for load map: Input/output error.
[Thread
Hello,
Do you have a core dump? If so, if you could get a backtrace as
described here http://wiki.squid-cache.org/SquidFaq/BugReporting and
post it here?
Thank you,
Nathan.
On 2 April 2015 at 03:45, Stakres vdoc...@neuf.fr wrote:
Hi All,
Strange problem during surf, squid 3.5.3, 64bits,
Hi All,
Strange problem during surf, squid 3.5.3, 64bits, Debian 7.8:
*2015/04/01 19:19:06 kid3| assertion failed: Read.cc:205: params.data ==
data*
caches:
workers 3
cache_dir rock /var/spool/squid3r1 166400 min-size=0 max-size=65536
swap-timeout=500 max-swap-rate=200/sec
if ${process_number} =
Hey Amos
This error's still happening on the 3.5.3 RPM I just built. I know nothing
about “atomics”, mind you. I’m all ears if you have any other suggestions :-)
Squid Cache: Version 3.5.3
Service Name: squid
configure options: '--build=x86_64-redhat-linux-gnu'
Hi Dan,
This appears by a breakage in the 3.5 snapshots' GNU atomics detection.
Though we are still not sure why the error occurs yet with atomics disabled.
Snapshots labelled r13783 or later available in a few hrs should be fixed.
Cheers
Amos
On 27/03/2015 11:47 a.m., Dan Charlesworth wrote:
Bumping this because I think it might have gone into the black hole the other
night.
On 23 Mar 2015, at 5:44 pm, Dan Charlesworth d...@getbusi.com wrote:
Turns out it’s also shitting the bed whenever I go to an SSL site now that
I’ve added --enable-storeio=rock:
2015/03/23 17:40:13
Okie dokie! boxes are crashing all over the place today so I finally have
some back traces without stuff optimised out.
Here are the details from two of these crashes which occurred on two
separate deployments—please let me know if they actually contain actionable
information now and I will
Resending this after the last attempt went into the mail server black hole:
Hey Amos
I decided I’m not confident enough in 3.5.HEAD, after last time, to go back
into production with it. Going to to do some more local testing first.
That being said, I now have 3.4.12 in production with
On 20/03/2015 1:07 p.m., Dan Charlesworth wrote:
Well I got 3.5.2 into production for a few hours and Bad Things happened:
*1) A hefty performance hit*
Load average was maybe a tad higher but CPU. memory and I/O were about the
same.
However the system seemed to top out at around 40
Well I got 3.5.2 into production for a few hours and Bad Things happened:1) A hefty performance hitLoad average was maybe a tad higher but CPU. memory and I/O were about the same. However the system seemed to top out at around 40 requests per second (on a client that usually hits 100—150 rps) and
Hello Dan:
i used 3.5.2 just now , i worried 3.5.3 isn't
very stable too ,
i use 2.7stable 9 ago , and you ?
if version is 3.xxx , which version is stablest
until now .
Best Regard
于
John -
For us the 3.4 series is definitely the stablest.
I was hoping 3.5.2 + plus a patch would avoid the error in this thread’s
subject—and it might have done—but it introduced two other major problems (for
us).
On 20 Mar 2015, at 2:29 pm, johnzeng johnzeng2...@yahoo.com wrote:
Hello
Hello Dan:
i used squid 2.7stable9 ago ,and i worried whether
squid 3.5.2 is stablest for us until now too .
and you ?
Do you think Whether version is stablest at squid
3.xxx ?
Well I got 3.5.2 into production for a few hours and
please i need solution for this am using 3.4.12 and still same problem every
few hour squid restart automatically
maybe high traffic make this problem ?
--
View this message in context:
On 27/02/2015 12:25 p.m., Dan Charlesworth wrote:
Alright I got abrtd on board, finally.
Here’s a a backtrace from this morning (bt and bt full versions included
separately):
Wonderful.
Can you get a print from frame 3 please of which of the connIsUsable()
checks if failing?
gdb
Alright I got abrtd on board, finally.Here’s a a backtrace from this morning (bt and bt full versions included separately):#0 0x00397e232625 in raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00397e233e05 in abort () at abort.c:92
#2 0x005656ef in xassert
By the way, I think Eliezer suggested I should file a bug report. There is in
fact one already filed here:
http://bugs.squid-cache.org/show_bug.cgi?id=3930
Which brings me to my next question ...
Amos, is it possible to sponsor bug fixes?
On Tue, Feb 24, 2015 at 2:47 PM, null
On 2015-02-25 15:11, d...@getbusi.com wrote:
By the way, I think Eliezer suggested I should file a bug report.
There is in fact one already filed here:
http://bugs.squid-cache.org/show_bug.cgi?id=3930
Which brings me to my next question ...
Amos, is it possible to sponsor bug fixes?
Of
Thanks for the help!
In file client_side.h:
inline void setServerBump(Ssl::ServerBump *srvBump) {
if (!sslServerBump)
sslServerBump = srvBump;
else
assert(sslServerBump == srvBump);
}
Changed to:
inline void setServerBump(Ssl::ServerBump
This is kind of off-topic but on one of our deployments this crash is now
consistently deadlocking squid whenever it occurs rather than just ending the
process. Meaning that is can’t be restarted by any means except kill -9, which
obviously a huge disruption to hundreds of clients and
Error negotiating SSL connection on FD 44: error:140A1175:SSL
routines:SSL_BYTES_TO_CIPHER_LIST:inappropriate fallback (1/-1)
This prepends the previous info.
___
squid-users mailing list
squid-users@lists.squid-cache.org
root@dotspot:~# gdb /usr/sbin/squid /var/spool/squid/cache/squid/core.3722
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
root@dotspot:~# gdb /usr/sbin/squid /var/spool/squid/cache/squid/core.4434
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
root@dotspot:~# gdb /usr/sbin/squid /var/spool/squid/cache/squid/core.3543
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
On 20/02/2015 5:46 p.m., Eliezer Croitoru wrote:
Hey Dan,
The basic rule of thumb in programming lands is script vs compiled code.
Where compiled code can be considered very reliable and in most cases
tested much more then scripts.
I am fearing that there is some race between all sorts of
Thanks Eliezer …
We've only ever used `kill` as very last resort when the squid process wouldn’t
respond to anything else.
Anyway, I think I missed what led you to think the crash is related to the
reply_body_max_size rules' external ACL as opposed to the many others we define?
That would
Hey Dan,
The basic rule of thumb in programming lands is script vs compiled code.
Where compiled code can be considered very reliable and in most cases
tested much more then scripts.
I am fearing that there is some race between all sorts of things on
runtime which might lead to this failed
On 20/02/2015 7:15 p.m., Dan Charlesworth wrote:
Thanks Amos -
So then it more than likely is related to our external ACLs that deal with
the HTTP response?
I think they may be making the issue more noticable by slowing down the
request processing. But Squid should not be getting into
Thanks Amos -
So then it more than likely is related to our external ACLs that deal with the
HTTP response?
On 20 Feb 2015, at 5:06 pm, Amos Jeffries squ...@treenet.co.nz wrote:
On 20/02/2015 5:46 p.m., Eliezer Croitoru wrote:
Hey Dan,
The basic rule of thumb in programming lands is
Hey Dan,
I am not the best at reading squid long debug output and it is needed in
order to understand the path that the request is traveling between the
ACLs and helper to determine if the issue is since the connection is
unusable because of a helper or because of another reason.
And so
Installed v3.4.12 and almost went a whole day without this crash.
Ended up rearing its head during a spike in traffic after lunch. Seems
to be more prone to occurring when the HTTP requests per second
reaches about 100.
I have a script running that runs a squid reload whenever this crash
occurs
last time i used 3.5 i lost about 6TB data because squid crash's and then
need to format the hdd's
so am afraid to use it again and no update addedd to that version
--
View this message in context:
root@dotspot:~# gdb /usr/sbin/squid /var/spool/squid/cache/squid/core.53359
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
root@dotspot:~# squid -v
Squid Cache: Version 3.4.9
build by : ANDO_TBLRB HackXBack
configure options: '--prefix=/usr' '--bindir=/usr/bin'
'--sbindir=/usr/sbin' '--libexecdir=/usr/lib/squid'
'--sysconfdir=/etc/squid' '--localstatedir=/var' '--libdir=/usr/lib'
'--includedir=/usr/include'
Hey Dan,
First I must admit that this squid.conf is quite complicated but kind of
self explanatory.
I have tried to understand the next lines:
# File size (download) restrictions
acl response_size_100 external response_size_type 100 192.168.0.10
http_access allow response_size_100
Hi Eliezer
Took a while to get this up—sorry about that. Here’s an example of a production
config of ours (with some confidential stuff necessarily taken out/edited):
https://gist.github.com/djch/92cf0b04afbd7917
https://gist.github.com/djch/92cf0b04afbd7917
Let me know if there’s any
Hi Eliezer
Thanks for paying attention, as always. I’m working on getting an
(appropriately censored) example of our squid.conf up for your perusal.
In the mean time I just wanted to point out that when this crash occurs some of
the most busy external_acl_types appear to crash too. Though the
Bumping this one for the new year 'cause I still don't understand squid
traces and because it's still happening with v3.4.11.
I would speculate that's it's something to do with the External ACLs
(there's a bunch). Let me know if a more recent traceback (than those
earlier in the thread) would
1 - 100 of 249 matches
Mail list logo
