Java LiveUpdate Fails with "Unknown Error" in Symantec Mail Security for Domino Multi Platform Edition on Solaris 10.x

Article:TECH171228  |  Created: 2011-10-06  |  Updated: 2011-10-26  |  Article URL http://www.symantec.com/docs/TECH171228
Article Type
Technical Solution

Issue



When Java LiveUpdate (JLU) runs on Solaris, the SMSDOM-MPE log reports several 'Unable to complete LiveUpdate session [unknown errors]'. No detailed information is given on the error. In liveupdt.log file an error will be visible, related to liveupdt.tri file being an invalid entry size


Error



Errors in SMSDOM log, Domino console, and liveupdt.log.


- Example of livupdt.log errors:
 

Oct 11 2007 21:00:54 Unzipping livetri.zip into /Symantec/LiveUpdate ...
Oct 11 2007 21:00:54 Extracting liveupdt.tri
Oct 11 2007 21:00:54 java.util.zip.ZipException: invalid entry size (expected 5827801 but got 5829586 bytes)
              at java.lang.Throwable.(Throwable.java:195)
              at java.lang.Exception.(Exception.java:41)
              at java.io.IOException.(IOException.java:40)
              at java.util.zip.ZipException.(ZipException.java:39)
              at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:367)
              at java.util.zip.ZipInputStream.read(ZipInputStream.java:141)
              at java.io.FilterInputStream.read(FilterInputStream.java:90)
              at b.a(DashoA5380:0)
              at b.e(DashoA5380:0)
              at LiveUpdate.main(DashoA5380:0)

Oct 11 2007 21:00:54 java.util.zip.ZipException: invalid entry size (expected 5827801 but got 5829586 bytes)
              at java.lang.Throwable.(Throwable.java:195)
              at java.lang.Exception.(Exception.java:41)
              at java.io.IOException.(IOException.java:40)
              at java.util.zip.ZipException.(ZipException.java:39)
              at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:367)
              at java.util.zip.ZipInputStream.read(ZipInputStream.java:141)
              at java.io.FilterInputStream.read(FilterInputStream.java:90)
              at b.a(DashoA5380:0)
              at b.e(DashoA5380:0)
              at LiveUpdate.main(DashoA5380:0)

Oct 11 2007 21:00:54 The Java LiveUpdate session did not complete successfully.
Oct 11 2007 21:00:54 Return code = -1



- Example of SMSDOM log errors


Cause



Version 3.2.1.27 of SMSDOM-MPE has an older version of Java LiveUpdate (jlu.jar) incorporated with the installer. The older version had a hard-coded file size limit for liveupdt.tri file. The liveupdt.tri file has grown and now exceeds this limit, causing jlu.jar to throw an exception.

This issue will also affect users who are attempting to  use SMSDOM-MPE 3.x to download virus defintions from an internal LiveUpdate Administrator 2.x (LUA 2.x) server.


Solution



The purpose of the jlu.jar process is to allow the latest virus defintions to be download to your machine.
 
Steps for (Replacing jlu.jar with newer version)

1.   A newer version of the jlu.jar file will be needed. Here is a copy of the 3.2 version that is password-protected with the password of symantec:

2.  Log into Solaris machine with root account.
3.  Change the group access to avdefs for the file /etc/liveupdate.conf by issuing the command:
chgrp avdefs /etc/liveupdate.conf
4.  Change the permissions to /etc/liveupdate.conf file by issuing the command:
chmod 664 /etc/liveupdate.conf
5.  Change the owner access to root for the file /etc/liveupdate.conf by issuing the command:
chown root /etc/liveupdate.conf
6.  Now extract the jlu.zip file that you downloaded from step 2 above. Put the jlu-3.2.2.jar in the /opt/Symantec/LiveUpdate folder on the server.
7.  Change the permissions for the jlu-3.2.2.jar file by issuing the command:
chmod 755 /opt/Symantec/LiveUpdate/jlu-3.2.2.jar
8. Remove the current symbolic link for jlu.jar by issuing the command:
rm /opt/Symantec/LiveUpdate/jlu.jar
9. Create a new symbolic link that points to our new jlu-3.2.2.jar file by issuing the command:
ln -s /opt/Symantec/LiveUpdate/jlu-3.2.2.jar /opt/Symantec/LiveUpdate/jlu.jar
10. The newer version of JLU requires a new file called Product.Catalog.JavaLiveUpdate. Issue the command:
touch /etc/Product.Catalog.JavaLiveUpdate
11. Change the group access to Product.Catalog.JavaLiveUpdate by issuing the command:
chgrp avdefs /etc/Product.Catalog.JavaLiveUpdate
12. Change the permissions to Product.Catalog.JavaLiveUpdate by issuing the command:
chmod 774 /etc/Product.Catalog.JavaLiveUpdate
13. Change the group access to /opt/Symantec/LiveUpdate by issuing the command:
chgrp avdefs /opt/Symantec/LiveUpdate
14. Change the permissions to /opt/Symantec/LiveUpdate by issuing the command:
chmod 775 /opt/Symantec/LiveUpdate
15. At this point Java LiveUpate will function correctly, and can be scheduled within our program to update definitions.
 


Attachments

jlu.zip (2.4 MBytes)


Article URL http://www.symantec.com/docs/TECH171228


Terms of use for this information are found in Legal Notices