Initialization failure following squid -k reconfigure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Squid |
New
|
Medium
|
|||
eCAP |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
eCAP fails to start following squid -k reconfigure
Loading Squid module from '/usr/lib/
Squid plugin modules loaded: 1
Adaptation support is on
ERROR: failed to start optional eCAP service: ecap://
WARNING: optional eCAP service is down after initialization failure: ecap://
ERROR: failed to start optional eCAP service: ecap://
Service.cc::73: !scanner
WARNING: optional eCAP service is down after initialization failure: ecap://
Restarting squid successful initializes eCAP service.
tags: | added: clamav |
Changed in ecap: | |
status: | New → Triaged |
Changed in ecap: | |
status: | Triaged → Fix Committed |
Changed in ecap: | |
milestone: | none → 1.0.0 |
Changed in ecap: | |
status: | Fix Committed → Fix Released |
Changed in squid: | |
importance: | Unknown → Medium |
status: | Unknown → New |
This is probably a Squid bug: During reconfiguration, Squid should call libecap: :Service: :reconfigure( ) but calls libecap: :Service: :configure( ) instead. Unfortunately, I do not see a quick way to fix Squid -- it seems to be missing the whole concept of service reconfiguration. It always creates and configures service representatives from scratch.
It should be possible to work around this problem in the adapter itself. I will post a patch.