Purge Updates not working for LUA 2.3

[Subhani]

Hi  , I am using Symnatec Liveupdate Administrator version 2.3.0.71 for Multiple products such as SMSMSE ,SMG and SEP 12.1  .It is working fine however its Purge Updates Option is not working ,neither for the Distribution Center nor for the Manage Updates directory .Due to this , the CLU-PROD folder  became very big and was holding SMG & SMSMSE  Updates since more than 3 months .NOw I have cleared them manually . Any ideas on how to fix this as the event log doesn't show any detailed error message regarding Purge task .

[pete]

pass on the event log from the LUA.it will show some error if it has failed.

collect the logs using the link below

http://www.symantec.com/business/support/index?page=content&id=TECH92654

[Subhani]

Hi ,It is 8 MB of data with lot of files .May I know which log file is the most relevant for this so that I can attach it here .

[Subhani]

Here is log extract from LUA-Application.log(full file is attached)

2012-08-31 22:15:00,023 [QuartzLuaScheduler_Worker-1] INFO  schedule.DistributionCenterPurgeTriggerJob  - About to fire Distribution Center Purge thread
2012-08-31 22:15:00,023 [QuartzLuaScheduler_Worker-1] INFO  schedule.DistributionCenterPurgeTriggerJob  - Finished firing DistributionCenter purge schedule for LUA Startup
2012-08-31 22:15:00,023 [DistributionCenterPurgeThread23] INFO  util.LuaUtil  -  JVM Runtime - Memory in MB - Total memory: 127 Free Memory: 72 maximum memory: 508
2012-08-31 22:15:00,023 [DistributionCenterPurgeThread23] INFO  schedule.DistributionCenterPurgeThread  - ********************Event Start********************
*************************************************
*************************************************
2012-08-31 22:15:00,023 [DistributionCenterPurgeThread23] INFO  schedule.DistributionCenterPurgeThread  - ************LUA_PURGING DISTRIBUTION CENTERS_START************
2012-08-31 22:15:00,023 [DistributionCenterPurgeThread23] INFO  server.PurgeServerContentServiceImpl  - start startPurgeOldUpdatesSchedule at time: 2012-08-31
2012-08-31 22:15:00,242 [DistributionCenterPurgeThread23] INFO  common.CleanUpLock  - Write Lock on CleanUpLock accquired
2012-08-31 22:15:00,413 [DistributionCenterPurgeThread23] INFO  contentrepository.DAOContentRepository  - CR_DETAILS DAO CLASS Time (ms) to getAllFileNamesInAllServers: 62
2012-08-31 22:15:03,382 [DistributionCenterPurgeThread23] INFO  contentrepository.DAOContentRepository  - CR_DETAILS DAO CLASS Time (ms) to getFileNamesInCZ: 2875
2012-08-31 22:15:03,413 [DistributionCenterPurgeThread23] ERROR cleanCLU.CleanUpThreadPool  - An error occured in startPurgeOldUpdatesSchedule: java.lang.NullPointerException
java.lang.NullPointerException
    at com.symantec.lua.common.CatalogZipCache.a(DashoA10*..)
    at com.symantec.lua.common.CatalogZipCache.populateServerCatalogZipCache(DashoA10*..)
    at com.symantec.lua.manager.server.PurgeServerContentManager.startPurgeOldUpdatesSchedule(DashoA10*..)
    at com.symantec.lua.service.server.PurgeServerContentServiceImpl.startPurgeOldUpdatesSchedule(DashoA10*..)
    at com.symantec.lua.manager.schedule.DistributionCenterPurgeThread.run(DashoA10*..)
    at java.lang.Thread.run(Unknown Source)
2012-08-31 22:15:03,413 [DistributionCenterPurgeThread23] INFO  common.CleanUpLock  - Write Lock on CleanUpLock released
2012-08-31 22:15:03,413 [DistributionCenterPurgeThread23] INFO  cleanCLU.CleanUpThreadPool  - ************LUA_PURGING DISTRIBUTION CENTERS_END************
2012-08-31 22:15:03,413 [DistributionCenterPurgeThread23] INFO  cleanCLU.CleanUpThreadPool  - ********************Event End************************
*************************************************
*************************************************
2012-08-31 22:15:03,413 [DistributionCenterPurgeThread23] INFO  server.PurgeServerContentServiceImpl  - end startPurgeOldUpdatesSchedule at time: 2012-08-31
2012-08-31 22:15:03,413 [DistributionCenterPurgeThread23] INFO  util.LuaUtil  -  JVM Runtime - Memory in MB - Total memory: 127 Free Memory: 73 maximum memory: 508

Attachment(s)

lua-application_0.zip   159 KB 1 version

[Migration User]

HI,

Check this thread

http://www.symantec.com/connect/forums/lua-23-purge-schedule-error

[Mithun Sanghavi]

Hello,

A couple of points:

We use SEPM for the vast majority of our clients and SEPM gets it's updates from this LUA server,  they are both on the same host. 

The SEPM and LUA should never be on the same server.  It's unsupported.  Here's an article on the subject:

LiveUpdate Administrator 2.x and Symantec Endpoint Protection Manager on the Same Physical Server
Article: TECH105076   |  Created: 2008-01-05   |  Updated: 2011-07-11   | 
Article URL http://www.symantec.com/docs/TECH105076 

Managing LiveUpdate Administrator 2.x Space Usage
https://www-secure.symantec.com/connect/articles/managing-liveupdate-administrator-2x-space-usage
 

Is there a specific reason why LUA is being used if the SEPM has internet access-?  Generally, in an all-SEP environment, the SEPM can do an efficient job of downloading and distributing everything its clients need.  LUA is a great product when used in the circumstances for which it was designed.

If there is a reason, I recommend upgrading the version of LUA that you are using:

LUA version is 2.3.0.71.

I recommend upgrading to LUA 2.3.1, and installing it fresh on a server that does not have a SEPM installed.  That should work fine.

Here are a couple articles about LUA that may help:

https://www-secure.symantec.com/connect/articles/managing-liveupdate-administrator-2x-space-usage

https://www-secure.symantec.com/connect/articles/helpful-liveupdate-administrator-2x-analogy

Please do keep this thread up to date with your progress!

Hope that helps!!

[Mick2009]

Hi Subhani,

Symnatec Liveupdate Administrator version 2.3.0.71

Please do upgrade to LUA 2.3.1, and to the forthcoming LUA 2.3.2 to take advantage of improvements and fixes.

How many revisions are you configuring LUA to retain?  I usually just configure it for 1 or 2. 

Some info on purging from the article Mithun recommended.....

Purging in LUA does not operate in a similar way to "keeping X number of content revisions" in a SEPM.  Some files which can seem very old are retained by LUA.  This is by design: LUA mirrors Internet contents, rather than creating deltas.  As certain content updates rarely change, the initial files will be the most recent release available even though they date back several months.  An example: SESM AntiVirus client update files. 

• Tuesday, February 22, 2011 1:59 PM 15025400 1256246532 jtun_sesmantivirusclientwin32_1567to333_20090918437_51903.zip
• Tuesday, February 22, 2011 1:58 PM 12113593 1256246532 jtun_sesmantivirusclientwin32_19to333_20090918984_51174.zip
• Tuesday, February 22, 2011 1:58 PM 13136468 1256246532 jtun_sesmantivirusclientwin32_2224to333_20090918765_46396.zip
  etc

Using "Manage Updates" can display when a particular file or product last updated a component.

Also: examine the LUA Event Log for any errors regarding "Distribution Center Cleanup," "Purge Schedule" and "Delete Content."  These errors can take place in the event of LUA database corruption, failure to delete files that were locked by other processes, etc.

     
Can Files Be Purged Manually?

Though Windows will allow it, it is NOT recommended to manually delete files that are in LUA's TempDownloads, Manage Updates and Distribution Center locations.  Doing so will throw the LUA database out of alignment with what is present on the disk.  In case this has been done, please read:  

What to do if you have Manually Deleted Files from a LiveUpdate Administrator 2.x Distribution Center?
Article URL http://www.symantec.com/docs/TECH132036
 

An "emergency purge" option may be added to a future release of LUA.  There is a Connect Forum "Idea" (proposed enhancement request) that can be supported by those who wish to voice their interest in such an option: "Purge Now" Button for LiveUpdate Administrator 2.x

The best current solution, if it is strongly believed that an existing DC contains files that it should not:

1. Backup the LUA 2.x server's settings
2. Backup the contents of the DC
3. Delete the DC in LUA's Configure / Distribution Centers GUI
4. Afterward, re-create the DC with the same location, name, etc

This will wipe out all of the current contents and replace them with only the current, known-good, valid materials from the LUA server's Manage Updates directory.

[John Santana]

"future release of LUA" ?

when that will be released ?

[pete]

currently under BETA

LiveUpdate Administrator 2.3.2 beta testing opportunity\

https://www-secure.symantec.com/connect/forums/liveupdate-administrator-232-beta-testing-opportunity

[John Santana]

great, many thanks Pete.

most probably it will ship with RU2 at the end of October this year ?

[pete]

:-), the forum will be updated when the new release is available

[Mick2009]

Also, you can subscribe to the following article.  When that is updated, you will receive a notification.

How to obtain the latest version of Symantec LiveUpdate Administrator (LUA) 2.x
Article:TECH134809   |  Created: 2010-01-09   |  Updated: 2012-06-19   | 
Article URL http://www.symantec.com/docs/TECH134809 
 

[John Santana]

Great, 

Many thanks as usual guys.

[Mick2009]

Hi Subhani,

Just checking to see if LUA 2.3.2 resolved this issue for you.

Also, here is a new purge-related KB article that may be of interest:

LiveUpdate Administrator 2.x Event Log Shows Delete Content Errors, "files failed to delete as a result of the delete operation"
Article URL http://www.symantec.com/docs/TECH198225 
 

[Subhani]

No Luck Yet . the Latest article is good .I tried it and here is what my log says .See the bold items .by the way ,how can I get LUA 2.3.2 .

 

2012-11-06 13:35:00,046 [DistributionCenterPurgeThread46] INFO  schedule.DistributionCenterPurgeThread  - ********************Event Start********************
*************************************************
*************************************************
2012-11-06 13:35:00,046 [DistributionCenterPurgeThread46] INFO  schedule.DistributionCenterPurgeThread  - ************LUA_PURGING DISTRIBUTION CENTERS_START************
2012-11-06 13:35:00,046 [DistributionCenterPurgeThread46] INFO  server.PurgeServerContentServiceImpl  - start startPurgeOldUpdatesSchedule at time: 2012-11-06

2012-11-06 13:35:00,046 [DistributionCenterPurgeThread46] INFO  common.CleanUpLock  - Write Lock on CleanUpLock accquired

2012-11-06 13:35:01,374 [DistributionCenterPurgeThread46] INFO  contentrepository.DAOContentRepository  - CR_DETAILS DAO CLASS Time (ms) to getAllFileNamesInAllServers: 1250

2012-11-06 13:35:05,968 [DistributionCenterPurgeThread46] INFO  contentrepository.DAOContentRepository  - CR_DETAILS DAO CLASS Time (ms) to getFileNamesInCZ: 4547
 

2012-11-06 13:35:05,984 [DistributionCenterPurgeThread46] ERROR  cleanCLU.CleanUpThreadPool  - An error occured in startPurgeOldUpdatesSchedule: java.lang.NullPointerException
java.lang.NullPointerException
 at com.symantec.lua.common.CatalogZipCache.a(DashoA10*..)
 at com.symantec.lua.common.CatalogZipCache.populateServerCatalogZipCache(DashoA10*..)
 at com.symantec.lua.manager.server.PurgeServerContentManager.startPurgeOldUpdatesSchedule(DashoA10*..)
 at com.symantec.lua.service.server.PurgeServerContentServiceImpl.startPurgeOldUpdatesSchedule(DashoA10*..)
 at com.symantec.lua.manager.schedule.DistributionCenterPurgeThread.run(DashoA10*..)
 at java.lang.Thread.run(Unknown Source)
 

2012-11-06 13:35:05,984 [DistributionCenterPurgeThread46] INFO  common.CleanUpLock  - Write Lock on CleanUpLock released
 

2012-11-06 13:35:05,984 [DistributionCenterPurgeThread46] INFO  cleanCLU.CleanUpThreadPool  - ************LUA_PURGING DISTRIBUTION CENTERS_END************
 

2012-11-06 13:35:05,984 [DistributionCenterPurgeThread46] INFO  cleanCLU.CleanUpThreadPool  - ********************Event End************************

2012-11-06 13:35:05,984 [DistributionCenterPurgeThread46] INFO  server.PurgeServerContentServiceImpl  - end startPurgeOldUpdatesSchedule at time: 2012-11-06

[John Santana]

Subhani,

What I did was to send email to Symantec then they get back to me with the link to download it directly.

or give them a call then they will provide you with the link:

 

To find regional customer care contact information:

http://www.symantec.com/enterprise/support/assistance_care.jsp

To find regional technical support contact information:

http://www.symantec.com/enterprise/support/techsupport_global.jsp