Impossible to startup Dollar Universe as some processes are still up even after shutdown
search cancel

Impossible to startup Dollar Universe as some processes are still up even after shutdown

book

Article ID: 87054

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Affects Release version(s): 5

Error Message :
Message "unable to connect" in the console even if the node status is connected.

Patch level detected:Dollar Universe 5.6.0
Product Version: Dollar.Universe 5.6.0 FX25010

Description :One/some DUAS engine's process does not stop on server and as a consequence DUAS cannot complete nor shutdown neither startup process.

Environment

OS: All Unix

Cause

Cause type:
Other
Root Cause: Because of one of the following, the Dollar Universe engine's process does not stop on the server:
-The user used to launch the uxshutdown script does not have enough rights/privileges to apply the shutdown procedure,

Resolution

- Identify the process not stopped using the command : ps -ef | grep COMPANYNAME
ex :

[[email protected] bin]# ps -ef | grep MANOR5
root 7277 24396 0 14:29 pts/1 00:00:00 grep MANOR5
root 27339 1 0 Sep05 ? 00:04:37 ./uxioserv MANOR5 X vmstl32c58cst01.orsyptst.com
root 27367 1 0 Sep05 ? 00:00:14 ./uxdqmsrv MANOR5 X vmstl32c58cst01.orsyptst.com
root 27434 1 0 Sep05 ? 00:00:18 ./uxeepsrv start MANOR5 X vmstl32c58cst01.orsyptst.com
root 27475 1 0 Sep05 ? 00:00:07 ./uxgsisrv start MANOR5 X vmstl32c58cst01.orsyptst.com
root 27526 1 0 Sep05 ? 00:00:34 ./uxcdjsrv MANOR5 X vmstl32c58cst01.orsyptst.com
root 27556 1 0 Sep05 ? 00:00:05 ./uxbvssrv MANOR5 X vmstl32c58cst01.orsyptst.com
[[email protected] bin]#

- Kill the process not correctly stopped on the server using the command : kill -9 PROCESSID

- Do an offline reorg of the node launching the "ux_vrf_rgz_rst" script from UXMGR directory (environment previously loaded with the uxsetenv script from UXMGR directory)
- Start the node with the uxstartup command also executed from UXMGR directory

At this point, all the process will be started as expected.

Fix Status: No Fix

Additional Information

Workaround :
N/A