Date: Mon, 20 Jun 2016 09:45:14 +0200 From: Andrea Venturoli <ml@netfence.it> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Periodic stuck in find (unkillable) Message-ID: <efd88372-61dd-285a-a93f-24665fcfd6a7@netfence.it>
next in thread | raw e-mail | index | archive | help
Hello. On a 10.3/amd64 box periodic is not running properly: often the mail just says "daily prior run still in progress". I've checked and there are several processes belonging to periodic; I was able to kill most of them (sometimes getting a partial report), but some instances of "find" are unkillable. > # ps ax | grep find > 10526 - D 0:34.62 find -sx / /usr /var /data /dev/null -type f ( ( ! -perm +010 -and -p > 82967 - DN 0:40.19 find -s / ! ( -fstype ufs ) -prune -or -path /tmp -prune -or -path /u > 92472 - D 1:14.42 find -sx / /usr /var /data /dev/null -type f ( -perm -u+x -or -perm - > 97995 - D 0:57.10 find -sx / /usr /var /data /dev/null -type f ( ( ! -perm +010 -and -p > 99128 0 S+ 0:00.00 grep find These processes will only go away by rebooting. On a similar box, I've got clamscan getting stuck: > # ps ax | grep clamscan > 6554 - D 279:49.04 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 13442 - D 473:55.64 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 17923 - D 461:30.71 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 34296 - D 490:31.21 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 36875 - D 475:49.56 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 39928 - D 277:08.06 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 40056 - D 460:25.45 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 43023 - D 479:36.90 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 45475 - D< 461:35.17 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 48693 - D 278:08.96 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 51667 - D 276:28.51 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 65643 - D 276:25.96 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 66804 - D 477:15.09 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 69644 - D< 461:25.68 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 71984 - D 483:20.62 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 72315 - D 277:17.21 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 74601 - D 277:31.67 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 90563 - D 474:07.14 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us > 93797 - D 465:10.58 /usr/local/bin/clamscan -r -i --stdout --exclude=//proc --exclude=/us I believe this started when I upgraded from 9.3 to 10.3. In both cases, I've got no NFS shares mounted, so it cannot be a network problem. Any idea what's going on or how to check? bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?efd88372-61dd-285a-a93f-24665fcfd6a7>