Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] Hostname problem, OSX 10.5
- Date: Tue, 02 Oct 2012 17:04:03 +1300
- From: Chris Jewell <c.p.jewell@xxxxxxxxxxxx>
- Subject: [Condor-users] Hostname problem, OSX 10.5
Hi all,
I've run into a problem on Mac OSX 10.5 concerning the hostname and IP
address that Condor registers when it starts. I've written a
LaunchDaemon plist (below) to launch condor_master on boot on the worker
machines. However, it seems to be binding to 127.0.0.1 -- when it
registers with the Collector I get errors (from the Collector) such as:
DC_AUTHENTICATE: session theCollector:1254:1349141429:44 NOT FOUND; this
session was requested by <130.123.155.217:49223> with return address
<127.0.0.1:49153>
The MasterLog on the worker machine confirms the daemons have bound to
127.0.0.1. AFAICS this looks like the daemons on the worker machine have
come up before networking was available (we assign our hostnames and
IP's by DHCP) and hence grabbed the loopback address.
Does anyone have any tips for how I might delay the start of the Condor
daemons until after networking is up, or prevent them from binding to
the loopback address?
Thanks,
Chris
Example .plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>condor</string>
<key>ProgramArguments</key>
<array>
<string>/condor/sbin/condor_master</string>
<string>-f</string>
</array>
<key>EnvironmentVariables</key>
<dict>
<key>CONDOR_CONFIG</key>
<string>/condor/etc/condor_config</string>
</dict>
<key>RunAtLoad</Key>
<true/>
<key>KeepAlive</key>
<true/>
</dict>
</plist>
--
Dr Chris Jewell
Lecturer in Biostatistics
Institute of Fundamental Sciences
Massey University
Private Bag 11222
Palmerston North 4442
New Zealand
Tel: +64 (0) 6 350 5701 Extn: 3586