enterprise-support team mailing list archive

Thread
Date

[Bug 1890414] [NEW] ICAP Service cannot be connected after upgrade to 3.5.12-1ubuntu7.12

To: enterprise-support@xxxxxxxxxxxxxxxxxxx
From: Arne Roolfs <1890414@xxxxxxxxxxxxxxxxxx>
Date: Wed, 05 Aug 2020 09:28:01 -0000
Reply-to: Bug 1890414 <1890414@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

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

** Affects: squid3 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to squid3 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1890414

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1890414/+subscriptions