C-ICAP - Error adding acl spec: !localserver.

Started by GreenMatter, June 13, 2025, 11:58:02 AM

Previous topic - Next topic


Since version 25.1.7 C-ICAP doesn't start automatically and throws following errors in log: 


2025-06-12T21:03:43Criticalc-icapmain proc, Error opening/parsing config file
2025-06-12T21:03:43Criticalc-icapmain proc, WARNING: Can not check the used c-icap release to build service clamd_mod.so
2025-06-12T21:03:43Criticalc-icapmain proc,
2025-06-12T21:03:43Criticalc-icapmain proc, WARNING: Can not check the used c-icap release to build service virus_scan.so
2025-06-12T21:03:43Criticalc-icapmain proc, Warning, alias is the same as service_name, not adding
2025-06-12T21:03:43Criticalc-icapmain proc, The line is: sys_logger.access !localserver
2025-06-12T21:03:43Criticalc-icapmain proc, Fatal error while parsing config file: "/usr/local/etc/c-icap/c-icap.conf" line: 32
2025-06-12T21:03:43Criticalc-icapmain proc, Error adding acl spec: !localserver.
2025-06-12T21:03:10Criticalc-icapmain proc, Error opening/parsing config file
2025-06-12T21:03:10Criticalc-icapmain proc, WARNING: Can not check the used c-icap release to build service clamd_mod.so
2025-06-12T21:03:10Criticalc-icapmain proc,
2025-06-12T21:03:10Criticalc-icapmain proc, WARNING: Can not check the used c-icap release to build service virus_scan.so
2025-06-12T21:03:10Criticalc-icapmain proc, Warning, alias is the same as service_name, not adding
2025-06-12T21:03:10Criticalc-icapmain proc, The line is: sys_logger.access !localserver
2025-06-12T21:03:10Criticalc-icapmain proc, Fatal error while parsing config file: "/usr/local/etc/c-icap/c-icap.conf" line: 32
2025-06-12T21:03:10Criticalc-icapmain proc, Error adding acl spec: !localserver.

And once line:
sys_logger.access !localserver
is removed in config file /usr/local/etc/c-icap/c-icap.conf, I'm able to manually start C-ICAP.

How to fix it permanently?
OPNsense on:
Intel(R) Xeon(R) E-2278G CPU @ 3.40GHz (4 cores)
8 GB RAM
50 GB HDD
and plenty of vlans ;-)

Filing a plugins bug report could help reach the maintainer. Not sure if this a general issue as I haven't seen a ticket and nothing really changed except the C-ICAP upstream version recently I think.


Cheers,
Franco

Quote from: franco on June 13, 2025, 12:20:00 PMFiling a plugins bug report could help reach the maintainer. Not sure if this a general issue as I haven't seen a ticket and nothing really changed except the C-ICAP upstream version recently I think.
Thanks, I filed bug report...
OPNsense on:
Intel(R) Xeon(R) E-2278G CPU @ 3.40GHz (4 cores)
8 GB RAM
50 GB HDD
and plenty of vlans ;-)