Endpoint Protection

So I realize that LiveUpdate Administrator 2.3 is brand new and not widely used at this point...but just in case someone has a clue as to what this error is, I thought I'd post it...as you can see, it has happened every night since I installed LUA 2.3.

Event Log:

Thanks for any suggestions,

-Mike

P.S.Other than the error above, LUA 2.3 works PERFECTLY and is blazingly fast...thanks GrahamA and Symantec!!

Do you have too many schedules set at the same time?

Hello,

Work on the steps provided below:

Maintain the database performance:

Stop “LUA Apache Tomcat” service. Do NOT stop “LUA PostgreSQL” service. Open a command window and run the following commands. Allow each to complete before beginning the next. Each may require several minutes.

1. Analyze the database
vacuumdb -z -h 127.0.0.1 -p 7072 -U lua -d lua >out_lua.txt 2>&1

2. Verify the database
vacuumdb -v -h 127.0.0.1 -p 7072 -U lua -d lua >out_lua_vdb.txt 2>&1

3. Reindex the database
reindexdb -h 127.0.0.1 -p 7072 -U lua -d lua >out_lua_vdb_idx.txt 2>&1

4. Re analyze and re verify the database after the reindex
vacuumdb -zv -h 127.0.0.1 -p 7072 -U lua -d lua >out_lua_vdb_idx_vdb.txt 2>&1

Verify the database using the following command:

vacuumdb -fzv -h 127.0.0.1 -p 7072 -U lua -d lua >out_lua_vdb_idx_vdb_f.txt 2>&1

Follow Few Symantec Knowledgebase Article:

1) Log retention settings for LiveUpdate Administrator 2.x (LUA 2.x)

http://www.symantec.com/business/support/index?page=content&id=TECH122803&actp=search&viewlocale=en_US&searchid=1301063707385

2) LiveUpdate Administrator 2.2 Performance Tuning

http://www.symantec.com/business/support/index?page=content&id=TECH96391&actp=search&viewlocale=en_US&searchid=1301063707385

I have two download schedules which automatically spawn (start) the distribution schedules. One of the download schedules coincides with the Purge Schedule...I will change the Purge Schedule to some time earlier and see if that helps.

Thanks for the reply,

-Mike

These steps may be be more directed toward LUA 2.2.x. LiveUpdate Administrator 2.3 is already 10x faster and includes a DB maintenance job that is scheduled to run every Saturday. I think I'll hold off on these steps until I can see what happens with the DB maintenance job on Saturday, or until one of the LUA 2.3 developers/techs confirm that these steps won't break (will help) LUA 2.3. The error does not seem to be affecting my downloads/distributions so this is not a critical situation.

If you haven't messed with LUA 2.3, I encourage you all to do so. It's GREAT!

Thanks for the reply,

-Mike

Hello Mike,

I understand, the LiveUpdate Administrator 2.3 is a new Tool.

If this is a major situation, I would suggest open a web case 

You can log a case on web portal:

QuickStart Guide - Create and Manage Support Cases in SymWISE

http://www.symantec.com/docs/HOWTO31132

How to update a support case and upload diagnostic files with MySupport

http://www.symantec.com/docs/TECH71023

Once, a case is created, provide us the case #  and we will do the needful.

As i mentioned in my previous post:

"The error does not seem to be affecting my downloads/distributions so this is not a critical situation."

No support case is necessary.

-Mike

Hi iamadmin,

Am keen to understand the cause, any chance you could send me the lua-application.log file for review?

(note, we are already working on the next maintenance release of LUA 2.x which would potentially release later this year so if there is any underlying issues that we smoke out, we will do our best to include fixes for them)

Thx!

Hi Iamadmin,

Cheers for the praise of LUA 2.3.  &: ) 

Here's an article on how to collect some info (including the lua-application logs that Graham mentioned) that can help us determine why the purging is failing:

How to Collect Troubleshooting Information from LiveUpdate Administrator 2.x  (http://www.symantec.com/docs/TECH92654)

Please do atatch the resulting luadebuginfo.zip to this thread; I will have a look as well.

Thanks and best regards,

Mick

The logs have been sent directly to Graham...

-Mike