Essbase Kill a ghost ESSSVR Process


Sometime we can see some of the sessions in Terminating state and even if we try to kill from EAS console or from MaxL we can not get rid of them or some of the process that are running in backend and we can’t see those in EAS console. so How to kill a runaway or ghost ESSSVR process.

To kill a runaway or ghost ESSSVR process:

Windows:

1. CTL/ALT/DEL and select Task Manager
2. In the processes tab, select the ESSSVR process and do an “End Process”. If you have multiple ESSSVR processes, you can search through the essbase.log file for the process ID that started the application.

UNIX:
1. From the UNIX prompt, type: ps -ef | grep ESSSVR
2. Find the runaway/ghost ESSSVR process ID and use the kill -15 command to kill that pid. If after a few minutes the ESSSVR process does not stop, you will have to use the kill -9 command.

NOTE:  The -9 argument to kill should never be used on Unix systems, except as a very last resort. The KILL signal does not allow a process to run any cleanup code, which means blasting away with kill -9 may leave child processes of a parent orphaned, temporary files open, shared memory segments active, and sockets busy. This leaves the system in a messy state, and could lead to unanticipated and hard to debug problems.

Properly written programs will respond to a -15 by cleaning up anything they need to do before dying. Understand that this is not a matter of priorities, or the system giving more time with a -15; it’s simply that a program can catch the -15, do what it needs to do and then voluntarily exit. It could also choose to ignore the -15 all together. If it hasn’t made any provisions at all, the -15 works exactly like the -9: the process dies immediately.

A “kill -9” just causes the process to die; it gets no chance to do any cleanup. Therefore, if you don’t know how a program was written, you should try the -15 first, in case it does need to clean up files, flush logs or whatever. If the -15 doesn’t work, then use the -9.

When using a kill -9 if processes do become orphaned they can attach themselves to the init process.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s