Environment
Novell Open Enterprise Server 2015 (OES 2015) Linux
Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
Situation
After installing or updating a 3rd party Linux anti-virus solution on a Novell Open Enterprise Server, odd things (anomalies) may occur, including:
- File transfers via ftp may stop.
- Management of the cluster from a terminal session may not complete.
(for example: running "cluster view" or "cluster status" may not return with out pressing Ctrl+C) - Management of the cluster from iManager may not be possible.
- NSS Pool (de)activation problems.
- NSS Volume (dis)mount problems.
- NCP Trustee problems.
- Cluster resource fail-over problems.
- Cluster status checking (via terminal session)
- Cluster management (via iManager)
- DST (Dynamic Storage Technology) policy execution problems.
- System crashes (kernel cores).
Stopping the anti-virus solution/service resolves the anomaly/malfunction.
Resolution
If stopping the anti-virus software fixes the matter but you need to still run the anti-virus software, then adding "exclusions" to the directories that are scanned or protected for "on-access" or "on-demand" use. The recommended place to start is to exclude the following:
Base linux directories (and sub-directories):
Base linux directories (and sub-directories):
/binNovell Open Enterprise Server specific directories (and sub-directories):
/boot
/dev
/etc
/home
/lib
/lib64
/mnt
/opt
/proc
/root
/sbin
/selinux
/srv
/sys
/usr
/var
/admin (owned/used by Novell Clustering)
/_admin (owned/used by Novell NSS)
/.*/\._NETWARE (owned/used by Novell NCP and found on the root of every NSS volume)
Additional Information
When not using OES services listed here, it may not be needed to exclude all of the above directories.
However when a Linux based anti-virus solution is in place and erratic system behavior at any level is observed; one of the first trouble shooting steps should be to either
However when a Linux based anti-virus solution is in place and erratic system behavior at any level is observed; one of the first trouble shooting steps should be to either
- stop the anti-virus solution, or
- ensure the above mentioned directories are excluded in the anti-virus solution