Bug 56556 – Squid crashes because of 'assertion failed' error in squid-cache

Bug 56556 - Squid crashes because of 'assertion failed' error in squid-cache


Summary:	Squid crashes because of 'assertion failed' error in squid-cache

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Squid
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:	http://www.squid-cache.org/Versions/v...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-09-08 11:07 CEST by Wolfgang Bayrhof
Modified:	2024-01-18 07:23 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	7: Crash: Bug causes crash or data loss
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.240
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:	Yes
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023082321000182
Bug group (optional):
Max CVSS v3 score:

Flags:	requate: Patch_Available+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Wolfgang Bayrhof

2023-09-08 11:07:53 CEST

Squid proxy server can crash sporadically with messages like this:
kid1| assertion failed: stmem.cc:98: "lowestOffset () <= target_offset"

Caused by this known bug at debian or squid-cache:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943692
https://bugs.squid-cache.org/show_bug.cgi?id=4823

The regarding fix is not included yet in UCS 5.0

Current workaround for the customer is to restart the squid server and/or to implement automatic restarting.

Comment 1 Mirac Erdemiroglu

2024-01-18 07:23:29 CET

Fixed in Debian with squid Source-Version: 4.9-1

UCS squid version is 
Inst squid (4.6-1+deb10u9A~5.0.6.202401091025 Univention Corporate Server:5.0.6-errata/errata506 [amd64])

Package: univention-squid
Version: 13.0.7-3

Workaround for this failure:

You can try to set the restart policy for squid to always, than squid will be restarted even if it exited with exit code 0:

Create /etc/systemd/system/squid.service.d/override.conf and add the following:

[Service]
Restart=always