VirusScan Enterprise for Linux 1.9.x Known Issues
技術的な記事 ID:
KB78126
最終更新: 6/21/2018
最終更新: 6/21/2018
環境
McAfee VirusScan Enterprise for Linux (VSEL) 1.9.x
For details of VSEL supported environments, see KB75270.
概要
This article contains important information about known issues of high or medium rating that are outstanding with this product release. This article will be updated if new issues are identified post-release, or if additional information becomes available. To read the Release Notes, see:
Recent updates to this article:
Release Details:
Known Issues
CRITICAL: There are no critical issues.
Non-critical:
Recent updates to this article:
| Date | Update |
| June 21, 2018 | Added:
|
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Release Details:
| Product Version | Released to World (RTW) date |
Release Notes |
| VSEL 1.9.2 Hotfix 1229391 RTS 1 |
June 20, 2018 | - |
| VSEL 1.9.2 | March 29, 2016 | PD26452 |
| VSEL 1.9.1 Hotfix 1073855 |
August 20, 2015 | PD26098 |
| VSEL 1.9.1 Hotfix 1065267 |
June 25, 2015 | PD26058 |
| VSEL 1.9.1 | March 4, 2015 | PD25820 |
| VSEL 1.9.0 | April 28, 2013 | PD24455 |
| 1 | McAfee Enterprise investigated this issue and a solution is currently available. This solution is currently not generally available, but is in Released to Support (RTS) status. To obtain the RTS build, log on to the ServicePortal and create a Service Request. Include this article number in the Problem Description field.
See KB51560 - McAfee Enterprise on-premises product release cycle for more information. |
Known Issues
CRITICAL: There are no critical issues.
Non-critical:
| Reference Number | Related Article | Found Version | Fixed Version | Issue Description |
| 1229391 | - | - | 1.9.2 HF1229391 |
Issue: Intermittent reboot issue on Red Hat Enterprise for Linux systems with VirusScan Enterprise for Linux installed. |
| 1236238 | - | - | 1.9.2 HF1229391 |
Issue: The “.” files in the /var/opt/NAI/LinuxShield/etc/ directory are now deleted, when starting the on-demand scan task. |
| 1127780 | - | 1.9.x | n/a | Issue: A core dump is generated for Mue_InUse when trying to update the DAT and Engine through the common updater site. The update task exits in the middle of the engine download preventing the DAT from being updated. This issue happens only in a standalone environment and when a later version of the engine is posted to the common updater site. When this issue occurs, the following message is left in the syslog. The signal type is segfault and the library module is libmfecomn.so.4.8, but the value of ip (instruction pointer) and sp (stack pointer) would vary depending on the environment. "kernel: Mue_InUse[50950]: segfault at 0 ip 00000000f7745fcd sp 00000000fff25450 error 4 in libmfecomn.so.4.8[f7727000+55000]" Workaround: Deselect Engine Update in the task and perform a DAT-only update. The Engine must be updated manually. |
| n/a | n/a | n/a | n/a | Issue: Internet Explorer 7 is not supported on VSEL 1.9.x Extensions. Workaround: Use a supported browser. |
| 1125683 | n/a | 1.9.x | n/a | Issue: Google Chrome version 48.0.2564.116 (64-bit) is not supported. |
| n/a | n/a | 1.9.x | n/a | Issue: Unable to check in the second VSEL 1.9.x hotfix to the Current branch of the ePO Master Repository from the ePO Software Download Manager (SDM). Workaround: Instead of clicking the Check-in option, click the Update option to check in to the Current branch. Do not select the option to move any existing hotfix. |
| n/a | n/a | 1.9.x | n/a | Issue: Unable to check in the second VSEL 1.9.x hotfix to the Current branch of the ePO Master Repository from the ePO Software Download Manager (SDM). Workaround: Instead of clicking the Check-in option, click the Update option to check in to the Current branch. Do not select the option to move any existing hotfix. |
| 965938 | n/a | 1.9.x | n/a | Issue: If a file is infected using redirection on NFS4 mounted volumes, it is not detected. |
| n/a | n/a | 1.9.x | n/a | Issue: You see a blank pop-up message when you try to save either a VSEL OAS or general policy that has already been assigned in ePO (Firefox 23). Resolution: Click OK and continue. You can safely ignore this error. |
| n/a | KB73344 | 1.9.x | n/a | Issue: NFS V4 does not support kernel versions lower than 2.6.20. Resolution: This release supports only systems running on RHEL and SUSE platforms with kernel versions later than 2.6.20. |
| n/a | KB73043 | 1.9.x | n/a | Issue: With VSEL 1.9.x enabled, you see a kernel panic in SLES (all Kernel 3.0.xxx.x versions) and Ubuntu systems when running as an NFS server and NFS client simultaneously. Resolution: This configuration is not supported in VSEL 1.9. |
| n/a | n/a | 1.9.x | n/a | Issue: Password change task for VSEL 1.9.x does not work on Ubuntu 64 computers. Workaround: On Ubuntu, install the 32-bit pam_nologin32.so library for the change password feature to work. |
| 844977 | n/a | 1.9.x | n/a | Issue: On RHEL 6.4, OEL 6.4, CentOS 6.4, and later, the VSEL On-Access Scan fails to detect infections on CIFS-mounted volumes. Workaround: Use an on-demand scan to detect infections on CIFS-mounted volumes. |
| n/a | n/a | 1.9.x | n/a | Issue: The On-Access Scanner cannot be loaded on Ubuntu 12.04.3 running Kernel 3.8.0.xx. Resolution: This kernel version is not supported. Supported kernels are listed in KB72999. |
| n/a | KB72999 | 1.9.x | n/a | Issue: Amazon Linux releases with the 3.4.43-X Kernel (for example, AMl releases 2013.03 and 2013.09) are not currently supported. |
| n/a | n/a | 1.9.x | n/a | Issue: You see the error 'LogClient connect failed on /var/opt/NAT/LinuxShield/dev/nailslog fd=3 No such file or directory (2)'. Resolution: This error also occurs in previous version of VSEL. This error can be safely ignored. There is no issue caused on the VSEL system. |
| n/a | n/a | 1.9.x | n/a | Issue: Traces are generated while unmounting CIFS volumes. Comments: These traces dumps do not harm any functionality of VSEL. |
| n/a | n/a | 1.9.x | n/a |
Issue: The web UI only works for browsers that have TLSv1.1 and TLSv2 protocol support (Security enhancement).
|
| n/a | n/a | 1.9.2 | n/a | Issue: When VSEL 1.9.2 Extensions are checked-in ePO, the product id is shown as LYNXSHLDMETA and the version shown as 2.0.2.1737. Workaround: You can safely ignore this information because VSEL now comes with common Extensions that manage both VSEL 1.9.2 and VSEL 2.x versions using single policy/task Extension.
|
| n/a | n/a | 1.9.1 1.9.2 |
n/a | Issue: VSEL 1.9.1 and 1.9.2 do not support kernel versions lower than 2.6.16. Comments: The new toolset supports only 2.6.16 and higher kernel versions. |
| n/a | n/a | 1.9.0 1.9.1 |
1.9.2 | Issue: VSEL 1.9.x deployment fails with McAfee Agent 5.x if both the RTW and hotfix packages are checked in to the ePO Master Repository. |
| n/a | n/a | 1.9.0 1.9.1 |
1.9.2 | Issue: The LogePO process does not start. The events generated are not sent to ePO. |
| n/a | n/a | 1.9.1 HF988521 |
n/a | Issue: VSEL 1.9.1 Hotfix 988521 installation might require a reboot to complete. Comments: This hotfix replaces Kernel Modules, which requires a reboot. |
| 1067281 | KB85308 | 1.9.1 | 1.9.2 | Issue: The shutdown -h now command no longer works after installing VSEL 1.9.1 on Red Hat Enterprise 6.4 systems. These systems can reboot unexpectedly. Resolution: Previously resolved with VSEL 1.9.1 Hotfix 1065267. |
| 1060443 | KB85309 | 1.9.1 | 1.9.2 | Issue: Mounting an NFS Volume using the NFS client v3 causes a system with VSEL 1.9.1 to hang. Resolution: Previously resolved with VSEL 1.9.1 Hotfix 1065267. |
| 1073855 | n/a | 1.9.1 | 1.9.2 | Issue: A Kernel panic occurs when writing files on NFSv4 network-mounted volumes with VSEL 1.9.1 installed. Resolution: Previously resolved with VSEL 1.9.1 Hotfix 1073855. NOTE: HF1073855 supersedes HF1065267. |
| n/a | n/a | 1.9.1 | 1.9.2 | Issue: When you deploy hotfixes for VSEL 1.9.1, McAfee Agent might report a successful installation on earlier versions of VSEL when the installation is not successful. This issue occurs because VSEL 1.9.1 hotfixes are not compatible with earlier versions. Also, VSEL 1.9.x and VSEL 1.7.x use the same ePO product code "LYNXSHLD1700," so McAfee Agent does not distinguish between the actual versions installed. Resolution: This issue is resolved in VSEL 1.9.2 and upcoming hotfixes for this release apply only for this version of VSEL. NOTE: To avoid this issue, target the deployment of hotfixes to only the systems that have the relevant version of VSEL. Or, organize or group clients in the ePO System Tree according to the VSEL version installed, and deploy it only to the corresponding groups. |
| n/a | n/a | 1.9.0 | n/a | Issue: Sometimes you see an error or you are logged out if you check in a VSEL 1.9.0 Extension. Workaround: Clear the browser cache before you check in the VSEL 1.9.0 Extensions to ePolicy Orchestrator (ePO). |
| n/a | n/a | 1.9.2 | n/a |
Issue: Sometimes, when you check in the VSEL 1.9.0 Extension, the product ID is shown as LYNXSHLD1700.
Workaround: Although the product name is VSEL 1.9.0, sometimes (see examples below) you see the product ID listed as LYNXSHLD1700. You can safely ignore this product ID.
|
McAfee Enterprise product software, upgrades, maintenance releases, and documentation are available from the Product Downloads site.
NOTE: You need a valid Grant Number for access. See KB56057 - How to download Enterprise product updates and documentation for more information about the Product Downloads site, and alternate locations for some products.
NOTE: You need a valid Grant Number for access. See KB56057 - How to download Enterprise product updates and documentation for more information about the Product Downloads site, and alternate locations for some products.
言語:
この記事は、次の言語で表示可能です:
GermanEnglish United States
Spanish Spain
French
Italian
Japanese
Portuguese Brasileiro
Chinese Simplified
