Disabling the pinger also works around the problem:
In /etc/squid/squid.conf:
pinger_enable off
** Summary changed:
- squid crashed with SIGABRT in xassert()
+ assertion error when rotating logs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Bug watch added: Debian Bug tracker #910337
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910337
** Also affects: squid (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910337
Importance: Unknown
Status: Unknown
** Also affects: squid via
http://bugs.squid-
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+merge/356100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794553
Title:
squid crashed with SI
If squid.conf has a cache_dir setting, then the crash doesn't happen. For
example:
cache_dir aufs /var/cache/squid-deb-proxy 4 16 256
Or, as I had in my home proxy, which wasn't crashing:
cache_dir ufs /var/spool/squid 1 16 256
** Changed in: squid (Ubuntu)
Status: In Progress =
Turns out it's easier than I thought, both in debian and ubuntu:
lxc launch images:debian/sid sid-squid
lxc exec sid-squid bash
apt update && apt install squid -y
tail -f /var/log/squid/cache.log | grep -1 assert
In another terminal:
lxc exec sid-squid bash
squid -k rotate
Watch the crash in
I also just managed to get this in debian's 4.2-2:
Oct 4 20:17:00 sid-squid4 squid[582]: assertion failed: comm.cc:428:
"!isOpen(conn->fd)"
Still working on a solid reproducer, but getting there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
This looks very much like https://bugs.squid-
cache.org/show_bug.cgi?id=4796
** Bug watch added: Squid Bugzilla #4796
http://bugs.squid-cache.org/show_bug.cgi?id=4796
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
/usr/sbin/squid -k rotate is enough to crash it on adconrad's machine,
even with the apparmor profile disabled.
We also tried with the new 4.2 packages, but -k rotate also crashes it
the same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ok, this seems to be pointing at a problem with the apparmor profile.
I'll prepare an update for that.
This is the patch I will be using:
--- etc/apparmor.d/usr.sbin.squid
+++ etc/apparmor.d/usr.sbin.squid
@@ -3,7 +3,7 @@
# vim:syntax=apparmor
#include
-/usr/sbin/squid {
+/usr/sbin/squid flag
apparently so
/usr/sbin/squid (enforce)1934 ?Ss 0:00 /usr/sbin/squid -sYC
/usr/sbin/squid (enforce) 32043 ?S 0:04 \_ (squid-1) --kid
squid-1 -sYC
/usr/sbin/squid (enforce) 32062 ?S 0:00 \_
(logfile-daemon) /var/log/squid/access.log
@jibel and @adconrad, are you guys running squid with its apparmor
profile enabled? Can you check with ps faxwZ or aa-status?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794553
Title:
squid crash
Thanks!
This is interesting. At 10:33:57, looks like this machine came back from
sleep/suspend. Is this a laptop?
Then 2s later we have these:
sept. 23 10:33:59 sark audit[12944]: AVC apparmor="DENIED" operation="capable"
profile="/usr/sbin/squid" pid=12944 comm="squid" capability=12
capname="
Here is the journal with records from September 23rd. The crash happened
again yesterday.
** Attachment added: "journal.log.gz"
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1794553/+attachment/5197120/+files/journal.log.gz
--
You received this bug notification because you are a membe
Do you still have /var/log/syslog (maybe rotated) from the time of the
crash, september 23rd? If yes, please attach it. Maybe I can correlate
it with something else going on in the system.
Is the crash still happening?
--
You received this bug notification because you are a member of Ubuntu
Bugs
I'm also running squid-deb-proxy but it's the main squid that crashed.
Here is the cache.log from the time of the crash. The access file for
the same time is empty (I don't use squid on this machine at the moment)
** Attachment added: "cache.log.1"
https://bugs.launchpad.net/ubuntu/+source/squ
@jibel, are you running squid-deb-proxy too by any chance?
Could you also attach /var/log/squid/cache.log, and perhaps a sanitized
/var/log/squid/access.log if you see something interesting in there
around the time of the crash?
--
You received this bug notification because you are a member of U
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+merge/356100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794553
Title:
squid crashed with SIGA
Here are squid 4.2 packages for cosmic, merged from debian:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3450/
If the crash happens frequently, would you mind giving these packages a
try to see if it improves the situation?
They also passed dep8 tests:
https://bileto.ubuntu.com/ex
** Changed in: squid (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: squid (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I'll work on an ubuntu update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794553
Title:
squid crashed with SIGABRT in xassert()
To manage notifications about this bug go to:
https://bugs.launchp
IIRC this may be the result of a bug found in the
src/ipc/TypedMsgHeader.* GCC-8 patch for 4.1. Debian received the fix
for that in the GCC-8 changes formally accepted into 4.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Getting this crash regularly here too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794553
Title:
squid crashed with SIGABRT in xassert()
To manage notifications about this bug go to:
https://bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: squid (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794553
Title:
squi
Thank you for the report.
I see that 4.2 is released upstream, but I don't see any related changes
upstream in this area (from a quick glance only).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17945
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794553
Title:
squid crashed with SIGABRT in xassert()
To manage notifications about this bug go to:
25 matches
Mail list logo
