LiveUpdate Administrator 2.x Event Log Shows Delete Content Errors, "files failed to delete as a result of the delete operation"

Article:TECH198225  |  Created: 2012-10-11  |  Updated: 2012-10-11  |  Article URL http://www.symantec.com/docs/TECH198225
Article Type
Technical Solution


Environment

Issue



LiveUpdate Administrator 2.x (LUA 2.x) may not be purging correctly.  The LUA 2.x Event log contains Delete Content errors which indicate that files are failing to delete.


Error



The LUA Event log contains entries similar to:

 

10/10/12 08:00:45 IST Delete Content informational LUA Startup 14 files failed to delete as a result of the delete operation.
10/10/12 08:00:46 IST Delete Content informational LUA Startup 14 files failed to delete as a result of the delete operation.
11/10/12 08:00:34 IST Delete Content informational LUA Startup 1 files failed to delete as a result of the delete operation.
11/10/12 08:00:38 IST Delete Content informational LUA Startup 1 files failed to delete as a result of the delete operation.
11/10/12 08:00:38 IST Delete Content informational LUA Startup 1 files failed to delete as a result of the delete operation.

 

 


Cause



These "x files failed to delete as a result of the delete operation" messages are usually harmless.  They generally reflect only that the attempt to delete a particular file was not completed because that file has already been deleted/purged/cleaned up as part of a previous ContentPackage. 

 


Solution



If there is a cause for concern, the LUA 2.x log files can be examined in depth.  To verify that all necessary older files have in fact been successfully deleted, perform the following search of the lua-application log files.

 

Purging tasks will follow the schedule configured under Configure > Preferences.  At the start of the purging task, there will be an entry such as: 

[Date] [Time] [ContentPurgeThread21] INFO  schedule.ContentPurgeThread  - ************LUA_PURGING CONTENT REPOSITORY_START************

or

[Date] [Time] [DistributionCenterPurgeThread19] INFO  schedule.DistributionCenterPurgeThread  - ************LUA_PURGING DISTRIBUTION CENTERS_START************

Identify the task that matches the time in the Event Log.  
 
Next, scroll down through the entries to the line where "Event message: content.delete.fail.count files:" is not []. For example:
 
[Date] [Time] [ContentPurgeThread21] INFO  contentrepository.DAOContentRepository  - Event message: content.delete.fail.count files: [1349652225jtun_nav2k8en121002017.m25]
 
That number will match the "x files failed to delete."  This is where the names of those files are listed.
 
Search the lines above for that file name: for example.....
 
[Date] [Time] [ContentPurgeThread21] INFO  contentrepository.DAOContentRepository  - Deleted file D:\LUA_Downloads\1349652225jtun_nav2k8en121002017.m25 status: true
 
That "deleted... status: true" line confirms that the file has been successfully deleted.  
 
As this particular file is also a component of another ContentPackage that is scheduled to be purged, LUA tries to delete it again. 
 
[Date] [Time] [ContentPurgeThread21] INFO  contentrepository.DAOContentRepository  - Deleted file D:\LUA_Downloads\1349652225jtun_nav2k8en121002017.m25 status: false
 
Because that file is already gone and cannot be deleted a second time, an error is thrown.  This results in the error "files failed to delete" entry seen in the LUA Event Logs.
 
 
If there are entries other than the above in lua-application logs, there may be an issue which needs further research.  Contact Symantec Technical Support for professional assistance, especially if it is seen that space in this hard drive is being consumed at a rapidly-growing rate.
 
 
Additional information on how LiveUpdate Administrator 2.x download, stores, purges and distributes its files can be found in the Connect forum article "Managing LiveUpdate Administrator 2.x Space Usage"
 
 

 

 





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


Terms of use for this information are found in Legal Notices