assertion failed: store_client.cc:92: "mem"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Squid |
Unknown
|
Unknown
|
|||
squid3 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* squid had a bug that showed up in some setup triggering
store_
Details are described in https:/
* This is backporting the upstream fix to squid for Bionic which is
rather close to the codebase the upstream fix happened.
[Test Case]
* TODO - waiting on feedback by the reporters
* Maybe we have to fall back to have (?multiple?) of the affected
reporters with complex squid setups affected by the issue to verify
this on their setup. But in that case I'd in addition ask to keep it in
-proposed for a longer duration.
[Regression Potential]
* The patch is rather huge myself and MP reviewers have tried to find an
issue with the changes to createMemObject that was changed and found
none. Never the less this is the area I'd expect issues if-any.
* On the good side thou is that the code effectively is upstream and in
Ubuntu >=18.10 for quit a while without being revoked since then (still
looks similar in 20.04). There was one fixup for the primary change
that was requested which is part of the suggested SRU.
[Other Info]
* n/a
---
Our squid crashes many times with the follow errors in /var/log/
root@proxy:~# grep -e failed /var/log/
2020/01/08 06:25:55 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 06:26:31 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 06:26:37 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 06:41:04 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 06:41:41 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 06:56:10 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 06:56:48 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:11:17 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:11:54 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:26:25 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:27:01 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:31:56 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:32:01 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:32:07 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:32:11 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:32:15 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 07:32:19 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 08:17:21 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 08:26:50 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 08:27:28 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 08:32:28 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 08:34:48 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 08:41:55 kid1| assertion failed: store_client.cc:92: "mem"
2020/01/08 08:42:35 kid1| assertion failed: store_client.cc:92: "mem"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: squid 3.5.27-1ubuntu1.4
ProcVersionSign
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Wed Jan 8 08:42:35 2020
InstallationDate: Installed on 2019-11-05 (63 days ago)
InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
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.
modified.
mtime.conffile.
mtime.conffile.
Related branches
- Robie Basak: Approve
- Canonical Server: Pending requested
- git-ubuntu developers: Pending requested
-
Diff: 334 lines (+306/-0)4 files modifieddebian/changelog (+6/-0)
debian/patches/lp-1858763-Bug-4616-store_client.cc-92-mem-assertion-50.patch (+260/-0)
debian/patches/lp-1858763-Fixed-store.cc-mem_obj-assertion-via-peerDigestReque.patch (+38/-0)
debian/patches/series (+2/-0)
description: | updated |
description: | updated |
tags: | removed: server-next |
The Bug is already fixed upstream.