Video Screencast Help

LUA PostgreSQL service stopped

Created: 22 Oct 2012 • Updated: 23 Oct 2012 | 16 comments
This issue has been solved. See solution.

The LUA PostgreSQL service on our server has stopped evertime I try to start it manually I get the message "The LUA PostgreSQL service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs." I've tried restarting the server which has not allowed the service to start back up.

I'm currently running LUA version 2.3.2.99

Comments 16 CommentsJump to latest comment

Ashish-Sharma's picture

HI,

Try to repaire LUA add/remove Program..

Thanks In Advance

Ashish Sharma

 

 

GeoGeo's picture

Already tried a repair and total uninstall and re-install of the LUA this has not fixed the issue :(

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

pete_4u2002's picture

what is the event id associated with the service stop?

can you post it?

 

GeoGeo's picture

Event ID error is as follows even after attempt to re-install/repair. Current Java version 6 update 17 (Build 1.6.0_17-b04) this can not be updated atm until latest version tested.

The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

FATAL: database "Administrator\TempDownloads\luadebug\lua_db.dump" does not exist

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

Ashish-Sharma's picture

HI,

Check this artical

PostgreSQL service not starting after server reboot

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

Thanks In Advance

Ashish Sharma

 

 

GeoGeo's picture

Hi Ashish,

Nice article unfortunatly when I went through the solution steps there was no pid of that type within task manager to end even when the view was enabled. sad

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

GeoGeo's picture

Also getting event ID 7036 "The LUA PostgreSQL service entered the stopped state."

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

Ashish-Sharma's picture

Hi GeoGeo,.

If above artical does not help

I Recommend you can raised support ticket

How to create a new case in MySymantec (formerly MySupport)

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

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

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

OR

Regional Support Telephone Numbers:

United States: 800-342-0652 (407-357-7600 from outside the United States)

Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)

United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

Thanks In Advance

Ashish Sharma

 

 

GeoGeo's picture

Already got a support case open with symantec but thought I'd see what I get from people on the forums while waiting for a reply.

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

Ashish-Sharma's picture

Once you will received solution please update on this thread.

 

Thanks In Advance

Ashish Sharma

 

 

Mithun Sanghavi's picture

Hello,

I would suggest you looking at these Articles:

The LUA Apache Tomcat Service (LUATomcat) in LiveUpdate Administrator 2.x Crashes or Fails

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

If the above does not help, PM me your case #

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

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

GeoGeo's picture

Hi Mithun,

It's not the LUA Tomcat service that is having issues that is up and running with no issues. It's the LUA PostgreSQL service that remains in a stopped status.

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

Mithun Sanghavi's picture

Hello,

I believe this may be due to PostgreSQL Log files being corrupted.

To repair the issue, command " pg_resetxlog
.exe -f C:\Program Files\Symantec\LiveUpdate Administrator\pgsql\data" need to be issued from %ProgramFiles%\Symantec\LiveUpdate Administrator\pgsql\bin directory.

pg_resetxlog clears the write-ahead log (WAL) and optionally resets some other control information stored in the pg_control file. This function is sometimes needed if these files have become corrupted.

After issuing this command LUA PostgreSQL service should start without any problems.

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

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

SOLUTION
GeoGeo's picture

That seems to have worked Mithun ran the command and got the same error when I tried to manually start the service but this time when I uninstalled and re-installed the LUA the service started automatically.

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

Mick2009's picture

Many thanks, GeoGeo, for updating this thread with the status!  &: )

Here is a new article that may help if that LUA server is having any download or connection issues:

LiveUpdate Administrator 2.x Server Connection Recommendations
https://www-secure.symantec.com/connect/articles/liveupdate-administrator-2x-server-connection-recommendations

Also: is there a SEPM on that same computer, by any chance?  If so, then either the SEPM or the LUA serevr will need to be moved elsewhere.  Having two major web-server-and-database products like LUA and SEPM on the same machine can lead to errors like the one you describe.

LiveUpdate Administrator 2.x and Symantec Endpoint Protection Manager on the same computer
Article URL http://www.symantec.com/docs/TECH105076  

With thanks and best regards,

Mick