Hello, We are seeing an issue with clamonacc on a Rocky Linux server. This is not a machine that we have access to and are asking this on their behalf. They currently are seeing clamonacc consume all the inodes on /tmp. The only way to recover the inodes is to kill clamonacc. Of course, this causes numerous issues while the server is in operation and the clamonacc program is hung. The server is running kubernetes in user mode, not under the root user. They have quite a few jobs in kubernetes that run and add log files to /tmp. /tmp is being actively monitored and must be monitored by clamav. The log file shows these error messages
ERROR: ClamCom: TIMEOUT while waiting on socket (recv) ERROR: Can't send to clamd: Broken pipe ERROR: Clamonacc: clamonacc has experienced a fatal error, if you continue to see this error, please run clamonacc with --verbose and report the issue and crash report to the developpers Other note, SELinux is enabled on this server but we have not encountered anything in the logs that indicates clamav is triggering. Some notes on the server OS: Rocky Linux 8 ClamAV Version: ClamAV 1.0.7/27490 We would be grateful for any tips or thoughts you may have! Thanks for your help! _______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
