Sophos Anti-Virus for Linux: Conflict with kdump

  • ID de l'article 118455
  • Mis à jour : 16 juil. 2014

Issue

When on-access scanning is enabled, kdump may not operate as expected.  The kdump service may fail to start, or a crashdump is not created during a kernel panic.

First seen in

Sophos Anti-Virus for Linux

Operating systems
Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6

What To Do

Follow the workaround relevant to your Operating System.

Red Hat Enterprise Linux 5
A crash dump is not created during a kernel panic.  Follow these steps:

  • Edit the kdump configuration: /etc/kdump.conf
  • Explicitly specify the dump device.  For example:  ext3 /dev/VolGroup00/LogVol00
  • Save the file
  • Restart kdump: /etc/init.d/kdump restart

To test that kdump is operating correctly, please follow the Red Hat documentation.

Red Hat Enterprise Linux 6

  1. The kdump service fails to start. Follow these steps:
    • Run: cd /lib/modules/`uname -r`
    • Create a symbolic link to the talpa modules:  ln -s /opt/sophos-av/talpa/current/
    • Search for kernel module dependancies:  depmod -a
    • Restart kdump:  /etc/init.d/kdump restart
    To test that kdump is operating correctly, please follow the Red Hat documentation.
  2. If you have followed the above procedure, we strongly recommend that you implement the following blacklist to prevent modules from loading and thereby avoid further issues.
    • Edit /etc/kdump.conf by adding the following to the blacklist:
      blacklist talpa_vfshook 
      blacklist talpa_core
      blacklist talpa_linux
      blacklist talpa_pedconnector
      blacklist talpa_pedevice
      blacklist talpa_syscall
      blacklist talpa_syscallhook
      blacklist talpa_syscallhookprobe
      blacklist talpa_vcdevice
    • Restart kdump: /etc/init.d/kdump restart

 
Si vous avez besoin de plus d'informations ou d'instructions, veuillez contacter le support technique.

Évaluez cet article

Très mauvais Excellent

Commentaires