Squid crashes with "assertion failed" authenticateUserAuthenticated

[maxim]

Binary package hint: squid3

Squid3 commonly crashes several times a day with no apparent reason, after several seconds squid3 restarts.

In /var/log/squid3/cache.log, the last lines are:
2009/12/15 11:46:12.987| ctx: exit level 0
2009/12/15 11:46:12.988| hdr cc: unknown cache-directive: near 'post-check=0, pre-check=0' in 'no-store, no-cache, must-revali
date, post-check=0, pre-check=0'
2009/12/15 11:46:12.988| hdr cc: unknown cache-directive: near 'pre-check=0' in 'no-store, no-cache, must-revalidate, post-che
ck=0, pre-check=0'
2009/12/15 11:46:12.988| The reply for GET http://www.tns-counter.ru/V13a****rambler_ru/ru/CP1251/tmsec=rambler_search/ is ALL
OWED, because it matched 'password'
2009/12/15 11:46:12.989| The request GET http://www.rambler.ru/cl?nv&name=begunBm&reqid=CA0CFB29D35AD619&links=id:1,cl:0.03571
,dm:no_domain|id:2,cl:0.03571,dm:joomla-admin.alex-kurteev.ru is ALLOWED, because it matched 'password'
2009/12/15 11:46:13.091| The reply for GET http://yandex.ru/yandsearch?text=%D0%B2%D1%8B%D1%88%D0%B8%D0%B2%D0%BA%D0%B0+%D0%BA%
D1%80%D0%B5%D1%81%D1%82%D0%BE%D0%BC&lr=225 is ALLOWED, because it matched 'password'
2009/12/15 11:46:13.091| assertion failed: ACLProxyAuth.cc:227: "authenticateUserAuthenticated(checklist->auth_user_request)"

# lsb_release -rd
Description: Ubuntu 8.04.3 LTS
Release: 8.04

# apt-cache policy squid3
squid3:
  Установлен: 3.0.STABLE1-1ubuntu1
  Кандидат: 3.0.STABLE1-1ubuntu1
  Таблица версий:
 *** 3.0.STABLE1-1ubuntu1 0
        500 http://ru.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

[Brian J. Murrell (brian-interlinx)]

OK. So when will this be fixed? This bug has been open for a year and 3 months already. It was reported in the previous LTS and is still present in the current LTS. That makes this bug over 2 years old.

Is having a crashing proxy server in two LTS releases acceptable? Is it acceptable especially considering there is a fix and that's to simply update the package to something more current?

I notice this isn't even fixed for the next release, Quantal since the fix is only in squid 3.2 and Quantal is still reporting as using 3.1.20. Or was the fix for this backported from the upstream's 3.2 release to Quantal's 3.1.20 release? I don't see anything in http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/squid3/quantal/files/head:/debian/patches/ (assuming that's the correct place to look) that indicates a patch for this issue.

I guess once again, I will be rolling my own packages here again to fix what my distro won't. ~sigh~

[Tiago Stürmer Daitx (tdaitx)]

This seems to have been fixed in an earlier squid release.