I have a samba with samba-vscan vfs module and clamav antivirus. In some cases,
when a viruses is founded ( I guess ! ) I receive this message in the log file
for the computer.
The smbd process take 100% of cpu and seems to me orphans / defuncts. In some
cases I have multiple process wich takes 100% too ( beetween them..) . I have
to kill all of them and restart the service.
Description of log file :
[2004/08/16 07:47:23, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 11 in pid 9836 (3.0.5)
Please read the appendix Bugs of the Samba HOWTO collection
[2004/08/16 07:47:23, 0] lib/fault.c:fault_report(39)
[2004/08/16 07:47:23, 0] lib/util.c:smb_panic2(1398)
PANIC: internal error
[2004/08/16 07:47:23, 0] lib/util.c:smb_panic2(1406)
BACKTRACE: 19 stack frames:
#0 smbd(smb_panic2+0x18c) [0x8191dfb]
#1 smbd(smb_panic+0x10) [0x8191c6d]
#2 smbd [0x8182422]
#3 smbd [0x8182477]
#4 /lib/tls/libc.so.6 [0xb22a18]
#5 /lib/tls/libc.so.6(__libc_free+0x8b) [0xb6a28b]
#6 /usr/lib/libmagic.so.1 [0xc37f41]
#7 /usr/lib/libmagic.so.1(magic_close+0x24) [0xc37fc4]
#8 /usr/lib/vfs/vscan-clamav.so(filetype_close+0x2a) [0x9f49a2]
#9 /usr/lib/vfs/vscan-clamav.so [0x9f589b]
#10 smbd(close_cnum+0xf5) [0x80c2b14]
#11 smbd(reply_tdis+0xa6) [0x809cff3]
#12 smbd [0x80bf895]
#13 smbd [0x80bf91f]
#14 smbd(process_smb+0x1b7) [0x80bfc1b]
#15 smbd(smbd_process+0x157) [0x80c0672]
#16 smbd(main+0x706) [0x81ed410]
#17 /lib/tls/libc.so.6(__libc_start_main+0xf0) [0xb10750]
#18 smbd(chroot+0x31) [0x80779e1]
Looks like a samba-vscan bug. Not our. I suggest you contact
the maintainers of that module.
what samba-vscan version do you use ?
There was a lot done after Version 0.3.5 for the clamav daemon.
what configurate params do you use ?
I use samba 3.0.5 to 3.0.7 on a single Processor and on a dual processor
machine and had no problems.
I hope you donot use the libclamav compile option.
Tanks for you reply.
I'm using Samba 3.0.5, Clamav 0.75 and Samba-vscan 0.3.5.RC1.
My samba was compiled with --with-vfs to support the vfs module of vscan.
The vscan was compiled --with samba-source=<path> and finally the clamav was
compiled without extra parameters.
I tried many configurations in vscan-clamav.conf according my proposite, but i
think the most significant are :
verbose file logging = no
scan on open = no
scan on close = yes
deny access on error = yes
infected file action = delete
this is important too..the lines of the service witch the error occurrs :
vfs object = vscan-clamav
vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
so.. at time with I got the error I was using the lastest version of the daemon
( samba, vscan and clamav ).
I'll search for the lastest version of samba-vscan to check if something
If you have some other sugestion, comment or want more information, please feel
free to reply me....
Maybe you can send your parameters (.conf) in these daemons for my analysis.
(In reply to comment #2)
> what samba-vscan version do you use ?
> There was a lot done after Version 0.3.5 for the clamav daemon.
> what configurate params do you use ?
> I use samba 3.0.5 to 3.0.7 on a single Processor and on a dual processor
> machine and had no problems.
> I hope you donot use the libclamav compile option.
> Regards Helmut
originally against 3.0.5rc1 (which was 34.0.6rc1 due to the security release).