Date: Sun, 13 Dec 2020 12:03:06 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251802] security/clamav: unstoppable, unkillable clamscan process blocking system in state "ufs" Message-ID: <bug-251802-7788-e509BlobU2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251802-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-251802-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251802 O. Hartmann <ohartmann@walstatt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|clamav |security/clamav: | |unstoppable, unkillable | |clamscan process blocking | |system in state "ufs" --- Comment #1 from O. Hartmann <ohartmann@walstatt.org> --- OS: FreeBSD CURRENT (FreeBSD 13.0-CURRENT #168 r368515: Thu Dec 10 15:01:30= CET 2020 amd64), port clamav-0.103.0,1 and clamav-unofficial-sigs-7.0.1. Roughly seven days ago the access to the hosts/netoworks providing clamav's update files were blockes by our firewall. Since 12th of December, clamscan= is running with two instances for a user (myself) on the specified host and it= is unkillable. I tried almost every KILL signal to stop the process as root, as the UID it runs as, with no success. Opening files with vi doesn't work or starting a new screen with screen com= mand (sysutils/screen, screen-4.8.0) is stuck forever - the attached tty is irresponsive, ssh sessions are stuck and stay in that state forever. The problem looks like a full /tmp or /var/tmp filesystem, but there is ple= nty of space left and I can't see anything wrong with out of space or out of inodes. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251802-7788-e509BlobU2>