I get 204 when c-icap fails to connect clamd via socket during c-icap startup.
Steps to reproduce:
two ways,
wrong startup order
- prerequisities: working clamd/c-icap installation. Tested with CentOS 7 system
- disable clamd and c-icap services
- reboot system
- start c-icap and wait until it fully starts
- start clamd
- test using c-icap-client with eicar or actual virus file
- actual result: 204, and "Registry 'virus_scan::engines' does not exist!" and "Antivirus engine is not available, allow 204" mesages on server.log
expected result: blocks file
c-icap does not have access to socket
- install clamav and c-icap, run as different users , use socket connection
- make sure that c-icap does not have access to clamd socket
- test using c-icap-client with eicar or actual virus file
- actual result: 204, and "Registry 'virus_scan::engines' does not exist!" and "Antivirus engine is not available, allow 204" mesages on server.log
- expected result: blocks file