assertion failed: MemBuf.cc:216: "0 <= tailSize && tailSize <= cSize"

Bug #1762682 reported by Thomas on 2018-04-10
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Squid
Unknown
Unknown
squid3 (Ubuntu)
High
Unassigned

Bug Description

Hi,

we are getting many times squid crashes. On the cache.log it shows:

2018/04/09 11:58:47 kid1| assertion failed: MemBuf.cc:216: "0 <= tailSize && tailSize <= cSize"
2018/04/09 11:58:51| Pinger exiting.

on syslog you read this:

Apr 9 11:56:32 proxy squid[903]: Squid Parent: will start 1 kids
Apr 9 11:56:32 proxy squid[903]: Squid Parent: (squid-1) process 906 started
Apr 9 11:58:42 proxy squid[903]: Squid Parent: (squid-1) process 906 exited due to signal 6 with status 0
Apr 9 11:58:45 proxy squid[903]: Squid Parent: (squid-1) process 1522 started
Apr 9 11:58:48 proxy squid[903]: Squid Parent: (squid-1) process 1522 exited due to signal 6 with status 0
Apr 9 11:58:51 proxy squid[903]: Squid Parent: (squid-1) process 1554 started
Apr 9 11:58:54 proxy squid[903]: Squid Parent: (squid-1) process 1554 exited due to signal 6 with status 0
Apr 9 11:58:57 proxy squid[903]: Squid Parent: (squid-1) process 1594 started
Apr 9 11:58:59 proxy squid[903]: Squid Parent: (squid-1) process 1594 exited due to signal 6 with status 0
Apr 9 11:59:02 proxy squid[903]: Squid Parent: (squid-1) process 1647 started
Apr 9 11:59:04 proxy squid[903]: Squid Parent: (squid-1) process 1647 exited due to signal 6 with status 0
Apr 9 11:59:07 proxy squid[903]: Squid Parent: (squid-1) process 1683 started
Apr 9 11:59:09 proxy squid[903]: Squid Parent: (squid-1) process 1683 exited due to signal 6 with status 0
Apr 9 11:59:09 proxy squid[903]: Squid Parent: (squid-1) process 1683 will not be restarted due to repeated, frequent failures
Apr 9 11:59:09 proxy squid[903]: Exiting due to repeated, frequent failures

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: squid 3.5.27-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Tue Apr 10 11:12:27 2018
InstallationDate: Installed on 2018-03-26 (14 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
ProcEnviron:
 LANG=de_DE.UTF-8
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
SourcePackage: squid3
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.squid.squid.conf: [modified]
mtime.conffile..etc.logrotate.d.squid: 2018-03-26T14:52:15.366011
mtime.conffile..etc.squid.squid.conf: 2018-04-10T11:05:02.821725

Thomas (t.c) wrote :
Thomas (t.c) wrote :

I linked a upstream bug - it looks like the same problem.

description: updated
Joshua Powers (powersj) on 2018-04-11
Changed in squid3 (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Andreas Hasenack (ahasenack) wrote :

The activity in the upstream bug seems to have stalled. Last report seems to indicate that http://bugs.squid-cache.org/attachment.cgi?id=3549 "works around the problem", but it's not clear what the consequences are of the workaround versus a proper committed fix.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.