This issue needs a solution.

LUA Server not downloading the scheduled definition update for SAVFL ?

Created: 12 Nov 2012
Login to vote
0 0 Votes

Hi,

I have installed the LUA v 2.3.2 (the latest) but so far I cannot get the new definition update pushed to all of my SAVFL for Linux client ?

Where is the log directory so that I can dig down the error and post it here for assistance ?

Thanks

Filed Under

Comments

pete_4u2002
Symantec Employee
13
Nov
2012
Votes
+2

have you configured the Linux

have you configured the Linux clients to get the updates form LUA? if not, you need to configure that.

check this link

https://www-secure.symantec.com/connect/articles/how-install-sav-linux-savfl-and-update-it-using-lua-2x-23071

 

Mick2009
Symantec Employee
13
Nov
2012
Votes
+1

Hi There John, How far are

Hi There John,

How far are you getting?  Is LUA able to successfully download and distribute the SAVFL definitions?  If there is a failure, you will see it in the LUA Event Log.

If so, then the problem is likely with the SAVFL clients: LiveUpdate on the Linux machines. 

Are some SAVFL clients able to successfully connect to that Distribution Center and retrieve the latest definitions?  Or are all failing to do so?

The log on each individual SAVFL client is called liveupdt.log - the location is configurable, but it is generally in /opt/Symantec/LiveUpdate/liveupdt.log

This article may help:

Configuring Symantec Antivirus for Linux (SAVFL) to download definitions from the Distribution Center of an internal LiveUpdate Administrator (LUA) 2.x Server
Article URL http://www.symantec.com/docs/TECH93505 
  

With thanks and best regards,

Mick

14
Nov
2012
Votes
0

Mick, The LUA server itself

Mick,

The LUA server itself cannot even download the content ?

Kind regards,

John Santana
Graduate IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

Chetan Savade
Symantec Employee
Accredited
13
Nov
2012
Votes
+2

Hi, LUA provides the

Hi,

LUA provides the functionality to export all LUA related logs, and system information in a zipped package which can be provided to Symantec support for further review.

Please go through the following articles

Installation and configuration of LUA

https://www-secure.symantec.com/connect/articles/installation-and-configuration-lua\

Gathering logs and troubleshooting data from LiveUpdate Administrator

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

How to Export the LiveUpdate Administrator 2.x Server Event Log

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

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.&

14
Nov
2012
Votes
0

see the following error

see the following error message in the event logger:

Kind regards,

John Santana
Graduate IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

Mick2009
Symantec Employee
15
Nov
2012
Votes
+1

"Connection to all source

"Connection to all source servers failed" - that means LUA is trying to reach the deafult internet LiveUpdate sites in order to download new definitions, but cannot reach them. 

This is usually fixed by tweaking the  configuration.  Perhaps the proxy between the LUA server and the Internet is not set with the right username and password?  Maybe there is a firewall which blocks contact between this LUA server and the internet? 

 

With thanks and best regards,

Mick

15
Nov
2012
Votes
0

Hi,   Unfortunately I cannot

Hi,

 

Unfortunately I cannot generate the LUA debug info ? because it is always saved as corrupted .ZIP withthe size of just 56-62 KB ?

I have also tried to save it on C:\, C:\Temp drive all without any success.

Kind regards,

John Santana
Graduate IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

Mick2009
Symantec Employee
16
Nov
2012
Votes
+1

That's odd- usually works

That's odd- usually works well. 

The most important logs are located in the logs directory and tomcat\logs.

With thanks and best regards,

Mick