Endpoint Protection

 View Only

LiveUpdate Administrator 2.x Server Connection Recommendations 

Oct 12, 2012 05:06 AM

I've been proclaiming for several years that Symantec's LiveUpdate Administrator 2.x is a great tool, when used correctly.  Let me add a corollary: LUA 2.x works great, when configured correctly. 

Here in Tech Support, I have very often seen LUA 2.x servers that were failing in their job to keep all the endpoints updated because their settings were not well suited to their environment.  So, here's a quick article that can help LUA admins overcome one common failure:  Download failures!

 

10/10/12 22:26:47 IST Download CRITICAL admin Failed to download file "1349882530jtun_ennlu64.aix" while processing request id "446".
10/10/12 22:33:48 IST Download CRITICAL admin Failed to download file "1349881801jtun_ennlu.is4" while processing request id "446".
10/10/12 22:33:48 IST Download CRITICAL admin Download job from source server "Symantec LiveUpdate" has failed. There were "2" updates that failed to download.
10/10/12 22:34:17 IST Download CRITICAL admin Download request  "446" started by "admin" has failed.

 

 

Why configure?

Some products kept up-to-date by LUA 2.x have small file sizes and so the server will encounter no trouble at all running with the default values.  The new content needed by other products, though - Symantec Endpoint Protection is a good example - has grown and grown.  (Millions of threats in circulation means very large AntiVirus signatures).  Network interruptions, etc can cause a file to become corrupted during transit and thus an entire LUA download task to fail.  This article has some additional information:

How Big are Current Symantec Endpoint Protection Definitions?
https://www-secure.symantec.com/connect/articles/how-big-are-current-symantec-endpoint-protection-definitions

 

Increasing connection timeouts and retry attempts can help LUA to successfully download large files, especially over busy internet connections.

 

Where to configure?

There are two places where connection settings should be altered: one is in the LUA GUI, and one is in its Tomcat configuration files.  The settings configured in Configure > Preferences controls server connection parameters.  There is also a lua_static.properties file which take cares of the download failures retries.

First: in the LUA GUI, click on Configure, then Preferences.  Scroll down to Server Connections.  Increase the timeout, retry and retry interval to improve the chance of successful connections.

TIMEOUT: 120 seconds
RETRY: 5
RETRY INTERVAL: 10 seconds

  

The second place to change settings is in the file ...\Symantec\LiveUpdate Administrator\tomcat\webapps\lua\WEB-INF\classes\lua_static.properties - lua_static.properties can be opened in notepad, textpad or your favorite text editor. I recommend updating the following values to increase the number of retries and period between retries:

  
download.retry.corruptFile=3
download.resume.corruptFile.retry=10
download.retry.corruptFile.sleep.msec=20000
download.http.header.acceptRanges=bytes


Do be sure to restart the LUA Tomcat service in order to reflect these changes.  Those changes will not go into effect until Tomcat restarts!
 
 
What else?

These recommendations are being created in Connect Forum so that LUA admins in the community can post their own observations, advice and feedback to the above.  So, please do comment! 

Statistics
0 Favorited
14 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Mar 21, 2014 04:58 AM

Good one.

Mar 20, 2013 05:39 AM

Gr8 work Mick & Mithun  !!!!

Goodluck for next...

Mar 20, 2013 01:50 AM

Thank u Mick to sharing article.

Mar 20, 2013 01:29 AM

Hi,

The default LUA Apache Tomcat service Run as Local System, should I change that into the DOMAIN\LiveupdateServiceAccount name ?

Oct 21, 2012 10:59 AM

mrezap2000,

Do all the same ones still fail if you re-run the download (before the next def release) ?  Plenty of space on the server?

Oct 21, 2012 03:42 AM

i set all setting that you say . but not repair my error

 

  10/21/2012 10:36:51 AM GMT+03:30 Download critical admin Download request 12 started by admin has failed.
10/21/2012 10:36:48 AM GMT+03:30 Download critical admin Download job from source server Symantec LiveUpdate has failed. There were 4 updates that failed to download.
10/21/2012 10:36:48 AM GMT+03:30 Download critical admin Failed to download file 1350770324jtun_sep12en121003002nohub.m26 while processing request id 12.
10/21/2012 10:36:48 AM GMT+03:30 Download critical admin Failed to download file 1350677004jtun_sepmfull25.x86 while processing request id 12.
10/21/2012 8:10:43 AM GMT+03:30 Download critical admin Failed to download file 1350770324jtun_sep12en121003002nohub.m26 while processing request id 12.
10/21/2012 7:35:13 AM GMT+03:30 Download critical admin Failed to download file 1350677004jtun_sepc120927011-121019011.x86 while processing request id 12.
10/21/2012 7:13:27 AM GMT+03:30 Download informational admin Started download of content for request id 12 started by user

 

Oct 12, 2012 01:17 PM

Hello,

Thank you for this Informative Article:

Users reading this Article would also be interested in these Articles below:

A Helpful LiveUpdate Administrator 2.x Analogy

Managing LiveUpdate Administrator 2.x Space Usage

How Big are Current Symantec Endpoint Protection Definitions?

Using IIS Logs to Check LiveUpdate Administrator 2.x Health

Hope that helps!!!

Related Entries and Links

No Related Resource entered.