Re: [Condor-users] Mac OS X condor startup at boot problems

[Rob Ballantyne <ballanty@xxxxxxxxxxxxx>]

On Fri, Feb 18, 2005 at 06:01:46PM -0600, Becky Gietzel wrote:
> 
> On Feb 18, 2005, at 4:59 PM, Rob Ballantyne wrote:
> 
> >Hi,
> >
> >  I'm having trouble getting the condor daemons
> >to start at boot on a 10.3.8 machine.
> >
> >  I've installed various startup scripts in both
> >/Library/StartupItems & /System/Library/StartupItems
> >and verified the structure of the directory is correct
> >and runs.  When I run the script manually at a root
> >prompt 'SystemStarter start Condor' or './Condor start'
> >everything starts just fine.  It's only when those are
> >run at boot time there seems to be a problem.
> >
> >  I thought at first that it might have been a problem
> >with SystemStarter so I added startup code to the /etc/rc
> >file (after the SystemStarter has run) and still no luck.
> >
> >  I'm beginning to think there is something about this
> >funny Apple 'Bootstrap Context' that might be getting
> >in the way.
> >
> >  In anyone else experiencing problem with boot time
> >startup on Mac OS X?
> >
> >  Thanks,
> >
> >Rob
> 
> Try using these Mac OS X startup scripts:
> 
> http://www.cs.wisc.edu/~bgietzel/condor-macscript/CondorAutoStart/
> 

  Ok, thanks for the help!!

  I tried the script you provided but the same results.  Works just
fine to start condor manually from a shell after boot but condor
isn't running after a boot.

  I scoped the condor logs a bit and found:

2/18 17:37:11 ******************************************************
2/18 17:37:11 ** condor_master (CONDOR_MASTER) STARTING UP
2/18 17:37:11 ** /usr/local/condor/sbin/condor_master
2/18 17:37:11 ** $CondorVersion: 6.7.3 Dec 28 2004 $
2/18 17:37:11 ** $CondorPlatform: PPC-DARWIN_6 $
2/18 17:37:11 ** PID = 469
2/18 17:37:11 ******************************************************
2/18 17:37:11 Using config file: /home/condor/condor_config
2/18 17:37:11 Using local config files: /usr/local/condor/local/condor_config.local
2/18 17:37:11 DaemonCore: Command Socket at <142.58.52.1:49337>
2/18 17:37:11 Started DaemonCore process "/usr/local/condor/sbin/condor_schedd", pid and pgroup = 470
2/18 17:37:11 Started DaemonCore process "/usr/local/condor/sbin/condor_startd", pid and pgroup = 471
2/18 17:37:27 Got SIGTERM. Performing graceful shutdown.
2/18 17:37:27 Sent SIGTERM to SCHEDD (pid 470)
2/18 17:37:27 Sent SIGTERM to STARTD (pid 471)
2/18 17:37:27 The SCHEDD (pid 470) exited with status 0
2/18 17:37:27 The STARTD (pid 471) exited with status 0
2/18 17:37:27 All daemons are gone.  Exiting.
2/18 17:37:27 **** condor_master (condor_MASTER) EXITING WITH STATUS 0


  It appears that immediatly after starting something is sending
condor_master a SIGTERM.  Who? Why?  I don't know.  Any thoughts?

  Thanks,

Rob
> 
> 
> Thanks,
>   --Becky
> >_______________________________________________
> >Condor-users mailing list
> >Condor-users@xxxxxxxxxxx
> >https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users