LUA problem after upgrade to 2.3.9

[Zebulon]

Hi Community,
After upgrading LiveUpdate Administrator today from 2.3.7.51 to 2.3.9.30, I cannot start the web console at http://<liveupdateserver>:7070/lua , but I get the error below. Anyone?

HTTP Status 404 – Not Found
--------------------------------------------------------------------------------
Type Status Report
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
--------------------------------------------------------------------------------



------------------------------
SDC
------------------------------

[Zebulon]

http://<liveupdateserver>:7070/clu-prod/test.txt is working!


------------------------------
SDC
------------------------------

[DDDD TTTT]

But if you manualy start "C:\Program Files (x86)\Symantec\LiveUpdate Administrator\tomcat\bin\startup.bat " - http://<liveupdateserver>:7070/lua work​

[Zebulon]

Got this, Java problem?

C:\Program Files (x86)\Symantec\LiveUpdate Administrator\tomcat\bin>startup.bat
Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
At least one of these environment variable is needed to run this program

C:\>"C:\Program Files (x86)\Symantec\LiveUpdate Administrator\tomcat\bin\startup
.bat"
The CATALINA_HOME environment variable is not defined correctly
This environment variable is needed to run this program

------------------------------
SDC
------------------------------

[Zebulon]

Problem solved!
I reverted to a snap before the upgrade and exported a configuration recovery file from the LUA web console and saved it on my OneDrive. Then I went back again and uninstalled and reinstalled LUA 2.3.9 and restored the exported configuration from my OneDrive. Now everything work as expected! 😊

------------------------------
SDC
------------------------------

[Luis Ontiyuelo]

Hi all, 

I'm experiencing same issue, 

I ran into this issue some weeks ago, I was asked to Update Catalog, then, LUA server (x3) are just running for 15min., I raised a support ticket and asked me to upgrade from 2.3.8 to 2.3.9. It didn't solve it. 

https://knowledge.broadcom.com/external/article/215609/liveupdate-administrator-fails-to-downlo.html
Then, they identified this issue:

https://knowledge.broadcom.com/external/article/164724/lua-apache-tomcat-service-luatomcat-in-l.html

I changed those parameters but still getting that error, and I didn't apply any change in Java from my side.

I cannot create a backup config in LUA servers now due to this issue, and I already raised a ticket with Support: 32730027, and they just mention to perform a fresh install,

any idea?

Thank you.

[John Owens]

Hi Luis,

Which issue are you experiencing?

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[John Owens]

If your LUA servers are not accessible please work through this document and report back - https://knowledge.broadcom.com/external/article?articleId=217340

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[Luis Ontiyuelo]

Hi again John,

After following those guidelines, executing lua_content_reset.sql and cleaning:

C:\ProgramData\Symantec\LiveUpdate Administrator\Downloads\

C:/TempDownloads and CluProd 

\Symantec\LiveUpdate Administrator \clu-prod\"

I can access and export config file properly and  update Symantec Product Catalog, which is now refreshed Successfully.

Thank you.

[John Owens]

Very nice. Sounds like something was corrupt in LUA database. You can use that document if issues like this arise again.  I would export your Configuration and keep it as a backup. Export after each major change you make in the LUA as well.

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[Luis Ontiyuelo]

I've just backed it up ^^

btw, your approach is gold for LUA issues. Therefore, it should have been mentioned in this support ticket: 32730027

regards.

[John Owens]

Hi Luis,

This document for using the lua reset tool was just created a couple of days ago to help with issues like this.  Likely the agent didn't know about it.  I will let them know though!

Thanks,

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[Luis Ontiyuelo]

Hi John, 

thank you for your answer, I will try it.

and after LUA Apache Tomcat service restart or LUA server restart, it works for 15-20mins approx. and cannot gather the config backup in time. After that , LUAs are not reachable anymore via GUI: https://(server):7073/lua/login.htm

This site cannot be reached. Server took too much time to respond

[MDubya]

So just to throw out another possible work around...I had issues with my LUA's freezing up. I was able to get in and disable (uncheck) all the Client and Content updates for SEP 14.3 RU2 that had ARM in the name, and for whatever reason, that fixed things for me.

I disabled all 14.3 RU2 ARM updates in the Download/Distribution and Deployment Settings. May be a fluke, but it's working for me.

-Mike