On 13-10-2019 20:29, Frans de Boer wrote:
LS,
Below is a piece of output listing, which ends with errors:
clamonacc --config-file=/etc/clamav/clamd.conf --foreground --verbose
ClamClient: client setup for continuous scanning
Clamonacc: daemon is local
ClamFanotif: kernel-level blocking feature disabled ...
ClamFanotif: max file size limited to 10485760 bytes
Clamonacc: beginning event loops
ClamFanotif: starting fanotify event loop with process id (17850) ...
ClamInotif: starting inotify event loop ...
ClamInotif: dynamically determining directory hierarchy...
ClamScanQueue: initializing event queue consumer ... (20) threads in
thread pool
ClamScanQueue: waiting to consume events ...
ClamInotif: watching '/mnt/raidarray/fdb-data' (and all sub-directories)
ClamInotif: watching '/mnt/raidarray/sdb-data' (and all sub-directories)
ClamInotif: watching '/mnt/raidarray/shared-data' (and all
sub-directories)
ClamInotif: excluding '/mnt/raidarray/fdb-data/fdb-home/bin/BOINC'
(and all sub-directories)
ClamInotif: excluding '/mnt/raidarray/fdb-data/fdb-home/.thunderbird'
(and all sub-directories)
ClamInotif: excluding '/mnt/raidarray/fdb-data/fdb-home/.mozilla' (and
all sub-directories)
ERROR: ClamInotif: could not watch path '/mnt/raidarray/fdb-data', No
such file or directory
ClamInotif: extra scanning on inotify events enabled
ClamInotif: DELETE - removing
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/mips
from
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch
with wd:27785
ClamInotif: CREATE - adding
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k
to
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch
with wd:27785
ClamInotif: attempting to feed consumer queue
ClamWorker: handling inotify event ...
ClamWorker: performing (extra) scanning on directory
'/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k'
ClamInotif: CREATE - adding
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools
to
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k
with wd:30908
ClamInotif: attempting to feed consumer queue
ClamInotif: CREATE - adding
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools/amiga
to
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools
with wd:30909
ClamInotif: attempting to feed consumer queue
ClamWorker: handling inotify event ...
ClamWorker: performing (extra) scanning on directory
'/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools'
ClamWorker: handling inotify event ...
ClamWorker: performing (extra) scanning on directory
'/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools/amiga'
ClamInotif: CREATE - adding
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools/amiga/SCCS
to
/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools/amiga
with wd:30910
ClamInotif: attempting to feed consumer queue
ClamWorker: handling inotify event ...
ClamWorker: performing (extra) scanning on directory
'/mnt/raidarray/fdb-data/program_repository/general_sources/linux/kernel/people/marcelo/linux-2.4/arch/m68k/tools/amiga/SCCS'
ERROR: Can't send to clamd: Bad address
ClamClient: connection could not be established ... return code 0
ClamMisc: internal issue (client failed to scan)
ERROR: Can't send to clamd: Bad address
ClamClient: connection could not be established ... return code 0
ClamMisc: internal issue (client failed to scan)
...at least, it looks like that. It starts with a "Bad address" error,
followed by two messages of which one state that it's internal issue.
Anybody seen this before?
--- Frans.
The "Bad address" message is generated because a file has been created,
but before it can be act upon, the same file is already removed. I have
scripts running every 4 hours, which scan for updates on GNU, Kernel
etc. Thereby creating small files in the designated directories. After
processing, these files are removed too. Which is causing the ERROR
reports. Rightfully so, but annoying.
Now, I run clamonacc with the --foreground switch, filtering these
messages and what is left, writing it into the log file.
--- Frans
_______________________________________________
clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
