Ubuntu
squid3 package

ICAP Service cannot be connected after upgrade to 3.5.12-1ubuntu7.12

Bug #1890414 reported by Arne Roolfs
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
squid3 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hello

Ubuntu release: Ubuntu 16.04.6 LTS
Package version: 3.5.12-1ubuntu7.12
Expected behaviour: Works as before

Actual behaviour:

After upgrading from 3.5.12-1ubuntu7.11 to 3.5.12-1ubuntu7.12 the ICAP service cannot be connected.

cache.log:
essential ICAP service is down after an options fetch failure: icap://127.0.0.1:1344/squidclamav [down,!opt]

The problem occured right after the update. The access.log of c-icap reports no accesses after the update of squid.

Regards
Arne

Revision history for this message
xavier (xavier-o) wrote :

Duplicated from: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1890265

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in squid3 (Ubuntu):
status: New → Confirmed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

You are right and this was already reported and started to be discussed in bug 1890265

Marking this as a duplicate, please follow the bug there.

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

Other bug subscribers

Remote bug watches

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