Le 6 août 04, à 11:44, Andrey Kaliazin a écrit :
"parent process" for all daemons will be the condor_master process, for ex
-
$ ps -ef |grep condor
condor 15346 1 0 May26 ? 00:48:31 condor_master -f
condor 13250 15346 0 Jul04 ? 00:33:12 condor_collector -f
condor 13251 15346 0 Jul04 ? 00:05:38 condor_negotiator -f
condor 13252 15346 0 Jul04 ? 00:00:27 condor_schedd -f
condor 13253 15346 0 Jul04 ? 00:16:51 condor_startd -f
condor 13254 15346 0 Jul04 ? 00:00:10 condor_ckpt_server
so you should look in ~condor/log/MasterLog file to find out what is
happening with it.
cheers,
Andrey
-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Jerome Jaglale
Sent: Friday, August 06, 2004 10:01 AM
To: Condor-Users Mail List
Subject: [Condor-users] condor daemons exit
Hello Condor users,
We use Condor to manage our mac G5 's cluster, and we're
happy with it. We have just a problem : after a while of
inactivity, condor daemons on a computer disappear. Even on
the central-manager. So when users want to submit or control
their jobs, it doen't work.
In the daemons' log files :
8/5 22:42:37 Our parent process (pid 16496) went away; shutting down
8/5 22:42:37 Got SIGTERM. Performing graceful shutdown.
I don't know who is this "parent process" : there was only
thre daemons : collector (16497), negotiator (16498) and shedd (16499)
Has someone an explication ? Is there an option to set, so
the daemons never exited ?
Thanks for your help,
Jérôme
_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
http://lists.cs.wisc.edu/mailman/listinfo/condor-users