Debian GNU 4.0 in trouble help me!

Avast Business Avast Business for Linux
1

Debian GNU / Linux 4.0 (Kernel 2.6.24) on which you installed avast 4. For real-time scanning capabilities of patch-dazuko-linux-2.6.24.diff.gz also apply the patch.

However, the number of excess will have access to the server after some time, the server goes down.

Apparently, the problem seems to occur in different versions.

This Debian GNU / Linux 4.0 (Kernel 2.6.24) to work with stable versions of avast dazuko who have let me know which version of.

Regards,

SoftMail Japan

2

Hallo,
avastguard and avastd (dazuko-mediator and scanner) are just common applications that couldn’t shut the system down. Namely, 2.6.22 was tested with Dazuko some time ago - this problem was never reported. But, try Dazuko over RedirFS (redirfs re-creates the layer which dazuko relies on).

regards,
pc

3

Hello!
I encountered the same problem, too.
Do you say, “Use dazuko on the redirfs layer”?
In that case, should I install dazuko not the kernel but outside?

4

Hallo,
it’s about compiling redirfs, and using dazuko over redirfs. Deailed how-to:
notes for compiling redirfs and dazuko (for SuSE11):

  • unpack the redirfs tarball, and do as root:
    cd redirfs-0.8
    make -C /lib/modules/uname -r/build M=pwd modules
    make -C /lib/modules/uname -r/build M=pwd modules_install

  • unpack the dazuko tarball, and do as root:
    cd dazuko-2.3.7
    cp <absolute_path_to_the_redirfs-0.8_directory>/Module.symvers .
    ./configure --redirfsdir=<absolute_path_to_the_redirfs-0.8_directory>
    make install

  • the modules can be loaded as:
    modprobe --allow-unsupported redirfs
    modprobe --allow-unsupported dazuko

regards,
pc

5

Hello!

I installed redirfs-0.8 and dazuko-2.3.7 in my server referring to your advice.

Then, I was testing avast with the server. However, it hung up again during the test.

The test was executed by putting the load into Apache that is running on the server.

What should I do?

The kernel version is 2.6.24.
The configuration of avastguard.conf is below:

USESYSLOG=yes
SYSLOGFACILITY=LOG_DAEMON
LOGFILE=/var/log/avast4/avastguard.log
MAXLOGFILE=0
IGNORELOGINFO=yes
COUNT=4
MAXCOUNT=10
AVIFACE=unix:/var/run/avast4/guardscanner.sock
AVTIMEOUT=0
ONOPEN=yes
ONCLOSE=yes
ONEXEC=yes
INCLUDEPATH=/home/
EXCLUDEPATH=/dev/:/proc/:/sys/
TRUSTEDUSER=root
MAXFILESIZE=0
DENY_SCANERROR=no
DENY_ENCRYPTED=no
LOGCLEAN=no
DELETE_INFECTED=no
RENAME_INFECTED=no
RENAME_SUFFIX=.vir
QUARANTINE_INFECTED=yes
QUARANTINE_DIRECTORY=/var/lib/avastguard/quarantine
QUARANTINE_RECURSIVELY=no

My best regards.

6

Hallo,
use only ON_OPEN, those two other options, leave as “NO”. Then, restart AvastGuard.
It’s known that kernels 2.6 don’t support ON_CLOSE this way.

regards,
PC