Initialization failure following squid -k reconfigure

[John Bull]

eCAP fails to start following squid -k reconfigure

Loading Squid module from '/usr/lib/ecap_clamav_adapter.so'
Squid plugin modules loaded: 1
Adaptation support is on
ERROR: failed to start optional eCAP service: ecap://e-cap.org/ecap/services/clamav?mode=REQMOD: Service.cc::73: !scanner
WARNING: optional eCAP service is down after initialization failure: ecap://e-cap.org/ecap/services/clamav?mode=REQMOD
ERROR: failed to start optional eCAP service: ecap://e-cap.org/ecap/services/clamav?mode=RESPMOD:
Service.cc::73: !scanner
WARNING: optional eCAP service is down after initialization failure: ecap://e-cap.org/ecap/services/clamav?mode=RESPMOD

Restarting squid successful initializes eCAP service.

[Alex Rousskov (rousskov)]

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.

[Alex Rousskov (rousskov)]

Does the attached patch help?

[John Bull (jbull)]

Alex,

Thank you for the patch, it appears to be effective. eCAP service starts without issue following Squid reconfigure.

Thanks,
John