user
June 3, 2009, 8:49am
1
Hi all,
I’m configuring the antivir solution with on-demand scan in my openSuSE 11.1, but I have some problems/errors with dazuko module. The status is:
**- Kernel 2.6.27.21-0.1-default #1 SMP 2009-03-31 14:50:44 +0200 x86_64 x86_64 x86_64 GNU/Linux
antivir-2.1.10.15-52.4
antivir-gui-2.1.10.15-1.117
antivir-avguard-2.1.10.15-52.4
dazuko-kmp-default-2.3.6_2.6.27.19_3.2-1.49.6
dazuko-2.3.6-7.1**
When I try to load the dazuko module I receive an error:
cal0024:~ # /etc/init.d/boot.dazuko start
Loading dazuko on-access scanner interface failed
or
cal0024:~ # modprobe dazuko
FATAL: Module dazuko not found.
The AppArmor is completely uninstalled.
Any idea?
Fabio Sambugaro
To be honest I’m not sure what the problem is. I have never bothered with this application. It’s just not required in Linux.
Someone may be able to advise though, just wait it out.
user
June 3, 2009, 9:47am
3
ok It’s just not required in Linux, but I’m configuring in the same host an external ftp server, and I would add a security scan layer on uploaded files.
Thanks. I wait for further suggestions.
Found it !! You upgraded the kernel to 2.6.27.21 while your dazuko module is built for 2.6.27.19 There’s the problem. You should have dazuko compiled for the running kernel.
user
June 3, 2009, 2:29pm
5
Where can I find the right package, compiled for my kernel?
Thanks.
Nope:
# uname -r
2.6.27.21-0.1-pae
# zypper in dazuko-kmp-pae
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
dazuko-kmp-pae
Overall download size: 293.0 K. After the operation, additional 1.3 M will be used.
Continue? [YES/no]:
Retrieving package dazuko-kmp-pae-2.3.6_2.6.27.19_3.2-1.49.6.i586 (1/1), 293.0 K (1.3 M unpacked)
Retrieving: dazuko-kmp-pae-2.3.6_2.6.27.19_3.2-1.49.6.i586.rpm [done]
Installing: dazuko-kmp-pae-2.3.6_2.6.27.19_3.2-1.49.6 [done]
Additional rpm output:
24475 blocks
# modprobe -v dazuko
insmod /lib/modules/2.6.27.21-0.1-pae/weak-updates/updates/redirfs/redirfs.ko
insmod /lib/modules/2.6.27.21-0.1-pae/weak-updates/updates/dazuko/dazuko.ko
# lsmod |grep dazuko
dazuko 31144 1
redirfs 40808 1 dazuko,[permanent]
Works for me™
user
June 3, 2009, 3:07pm
7
Hello Akoellh,
you installed dazuko-kmp-pae, while I installed the dazuko-kmp-default: they are different.
Other suggestions?
Somehow I knew what the answer would be.
I had to, because I use kernel-pae, but to show you that it’s not because of that (1 reboot later):
# uname -r
2.6.27.21-0.1-default
# zypper in dazuko-kmp-default
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
dazuko-kmp-default
Overall download size: 283.0 K. After the operation, additional 1.9 M will be used.
Continue? [YES/no]:
Retrieving package dazuko-kmp-default-2.3.6_2.6.27.19_3.2-1.49.6.x86_64 (1/1), 283.0 K (1.9 M unpacked)
Installing: dazuko-kmp-default-2.3.6_2.6.27.19_3.2-1.49.6 [done]
Additional rpm output:
26870 blocks
# modprobe -v dazuko
insmod /lib/modules/2.6.27.21-0.1-default/weak-updates/updates/redirfs/redirfs.ko
insmod /lib/modules/2.6.27.21-0.1-default/weak-updates/updates/dazuko/dazuko.ko
# lsmod |grep dazuko
dazuko 36752 1
redirfs 51176 1 dazuko,[permanent]
Works for me™ (Part 2)
So you are obviously doing something wrong here.
user
June 3, 2009, 4:12pm
9
Hello,
I haven’t these links:
/lib/modules/2.6.27.21-0.1-default/weak-updates/updates/redirfs/redirfs.ko
/lib/modules/2.6.27.21-0.1-default/weak-updates/updates/dazuko/dazuko.ko
Why? I have installed the packages by Yast. ???
rpm -qa "*kernel*" "*dazuko*"
uname -r
?
mdhnews
December 1, 2009, 6:21pm
11
I had the same issue,
cat /tmp/clamd.log
ERROR: Clamuko: Can’t register with Dazuko
I found that Dazuko was being loaded after clamav
I ran /etc/init.d/clamd restart
cat /tmp/clamd.log
Tue Dec 1 09:55:09 2009 -> Log file size limited to 1048576 bytes.
Tue Dec 1 09:55:09 2009 -> Reading databases from /var/lib/clamav
Tue Dec 1 09:55:09 2009 -> Not loading PUA signatures.
Tue Dec 1 09:55:10 2009 -> Loaded 660902 signatures.
Tue Dec 1 09:55:10 2009 -> TCP: Bound to address 127.0.0.1 on port 3310
Tue Dec 1 09:55:10 2009 -> TCP: Setting connection queue length to 15
Tue Dec 1 09:55:10 2009 -> LOCAL: Unix socket file /var/lib/clamav/clamd-socket
Tue Dec 1 09:55:10 2009 -> LOCAL: Setting connection queue length to 15
Tue Dec 1 09:55:10 2009 -> Limits: Global size limit set to 104857600 bytes.
Tue Dec 1 09:55:10 2009 -> Limits: File size limit set to 26214400 bytes.
Tue Dec 1 09:55:10 2009 -> Limits: Recursion level limit set to 16.
Tue Dec 1 09:55:10 2009 -> Limits: Files limit set to 10000.
Tue Dec 1 09:55:10 2009 -> Archive support enabled.
Tue Dec 1 09:55:10 2009 -> Algorithmic detection enabled.
Tue Dec 1 09:55:10 2009 -> Portable Executable support enabled.
Tue Dec 1 09:55:10 2009 -> ELF support enabled.
Tue Dec 1 09:55:10 2009 -> Mail files support enabled.
Tue Dec 1 09:55:10 2009 -> OLE2 support enabled.
Tue Dec 1 09:55:10 2009 -> PDF support enabled.
Tue Dec 1 09:55:10 2009 -> HTML support enabled.
Tue Dec 1 09:55:10 2009 -> Self checking every 600 seconds.
Tue Dec 1 09:55:10 2009 -> Clamuko: Correctly registered with Dazuko.
Tue Dec 1 09:55:10 2009 -> Clamuko: Scan-on-open mode activated.
Tue Dec 1 09:55:10 2009 -> Clamuko: Scan-on-close mode activated.
Tue Dec 1 09:55:10 2009 -> Clamuko: Scan-on-exec mode activated.
Tue Dec 1 09:55:10 2009 -> Clamuko: Included path /data
Tue Dec 1 09:55:10 2009 -> Clamuko: Max file size limited to 5242880 bytes.
Hopefully this helps you or anyone else.
Thanks
mdhnews
December 1, 2009, 6:41pm
12
Update,
found that this is all lost when the box is rebooted.
I ran, lsmod | grep dazuko,
nothing
Then ran this, modprobe -v dazuko
and /etc/init.d/clamd restart
back working:
Clamuko: Correctly registered with Dazuko.
So , why is the module for Dazuko not being loaded at startup ? and how do we change startup to get dazuko loaded before clamav?
mdhnews
December 1, 2009, 8:07pm
13
workaround
edit the local boot file
vi /etc/init.d/boot.local
addthis:
/etc/init.d/boot.dazuko start
/etc/init.d/clamd restart
reboot
check the clamd log
cat /tmp/clamd.log
should see :
Clamuko: Correctly registered with Dazuko.
etc etc