Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Performing manual update of the scan engine and pattern file on ServerProtect for Linux (SPLX)

    • Updated:
    • 21 May 2014
    • Product/Version:
    • ServerProtect for Linux 3.0
    • Platform:
    • Linux - Red Hat RHEL 3 32-bit
    • Linux - Red Hat RHEL 4 32-bit
    • Linux - SuSE version 10
    • Linux - SuSE version 9
Summary

If you are having problems with the current scan engine, you can perform a manual update or rollback for SPLX.

Details
Public
Please do the following:
  1. Download the latest pattern and scan engine files for SPLX from the Trend Micro Update Center.
  2. Open a “Command Terminal” and then decompress the pattern file.
    e.g. unzip lptXXX.zip
    Important: Unix/Linux commands are case-sensitive.
  3. Extract or decompress the scan engine file.
    e.g. tar -zxvf FILENAME.tar.Z
  4. Stop the SPLX service using this command:
    /etc/init.d/splx stop
    You may also use this command: “service splx stop” (Red Hat)
  5. Create a back up of the existing scan engine file (libvsapi.so) either by renaming or copying it into another directory.
  6. Copy the downloaded pattern and scan engine files to the ServerProtect program directory using these commands:
    cp lpt'$'vpn.xxx /opt/TrendMicro/SProtectLinux
    cp libvsapi.so /opt/TrendMicro/SProtectLinux
  7. Restart the SPLX service using this command:
    /etc/init.d/splx start
    You may also use this command: “service splx start” (Red Hat)
  8. Log on to the SPLX management console and then verify that the scan engine and pattern file have been updated correctly
  9. Access the following URL through IE (for Windows) or Netscape (for Windows and Linux):
    http://[Linux_Servername-or-_IP-Address]:14942 or httpw://[Linux_Servername-or-_IP-Address]:14943
    Note: There are instances when either the latest scan engine or pattern files are not immediately reflected on the management console. When this happens, try clearing the web browser cache and/or refresh the web console. You may also restart the SPLX service on the Linux server.
Premium
Internal
Rating:
Category:
Update
Solution Id:
1054885
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.