scheduler terminating

Hi there,

I am having an issue where the scheduler is terminating.
I start the scheduler in service mode using

./master.sh nogui &

after I exit my putty session it is getting killed for some reason.

How can I figure out what's going on?

I am running the muti platform edition 255 on red hat linux as 4.0 64 bit.

Thanks.

Is there any "logoff" kind of script or processing associated with PuTTY session that forcedly kills all processes started by the session user?
What about other commands, if you run something else, what happens to that process when you exit PuTTY session?

There is a .bash_logout file, but the only command in there is clear.
I am trying to replicate the action in debug mode.

I will let you know if I get anything.

What about other processes? If you start anything in the background then exit PuTTY session, do these processes exit or run?

what's a good process I can test this out with?

Thanks!

I guess, almost anything that doesn't terminate immediate can be used for testing. For example, you can try /bin/sh -c man & command, or just simple sleep
/bin/sh -c sleep 600 & If you start Tomcat or some other type of web or network server, you can even check it remotely.

I did a ping on a sever and exited.
I logged back in and the process is still running.

Please enable tracing option in 24x7 and let us know what it writes to the debug.log file when the scheduler terminates after session closing.

I do have tracing on and ever since I turned it on, it's been running just fine.
I will try to get it to terminate and post an update if I can get it to do so.

Thanks.

OK I do notice one thing.
If I don't execute the scheduler and exit my putty session it closes fine.

When I start the scheduler up in nogui mode in the background and then type exit, the putty session will not close by typing the exit command. It just hanges and then I have to click the "X" on the box to close the session.

Maybe this is why it's terminating sometimes.

What is in the debug.log when you click the "X" box? Is it running any jobs?

No it just disconnects.
Here is something interesting from the putty web site though...

"You can close a PuTTY session using the Close button in the window border, but this might confuse the server - a bit like hanging up a telephone unexpectedly in the middle of a conversation. We recommend you do not do this unless the server has stopped responding to you and you cannot close the window any other way."

We are running ssh2 on our boxes and it appears this can be an issue when running a process in the background. I am doing more research on this. It appears that I may have to issue a nohup and then the command to run the scheduler to prevent it from terminating.

I will post any findings if it terminates.

Sean

Another interesting thing...
I started the scheduler in nogui mode and then type exit.

The session hanged, but I kept it open (did not click the x).

I then entered another session and killed the scheduler from the new session.
Once I killed it, the hung session exited.

So for some reason, putty will not close with this process running in the background. I have a feeling sometimes its seeing the the session is being forcefully terminated and killing the process.

OK one thing I did find it that ssh will keep the session open until you redirect your output.

So I ran the following:

./master.sh nogui </dev> /dev/null 2>&1 &

When I ran this, I was able to exit clean out of my session.
Is there any issues with running the command like this?

Thanks!

Ooops here's the proper command:

./master.sh nogui </dev/null >/dev/null 2>&1 &