[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Trouble starting condor daemons - CONDOR_IDSerror

>  I ran condor_master with strace, I don't really understand what is being
> recorded, but I did notice the global condor_config is not opened on the
> computers with the error. I attach the strace of a working and nonworking
> computer. Also the nonworking computer opens /etc/passwd, which does not
> contain the ldap user information, and hence the CONDOR_IDS error.

In looking at your strace output, the maches that work check and file
condor_config in /opt/condor:
stat64("/opt/condor/etc/condor_config", {st_mode=S_IFREG|0644,
st_size=88256, ...}) = 0
lstat64("/opt/condor/etc/condor_config", {st_mode=S_IFREG|0644,
st_size=88256, ...}) = 0
stat64("/opt/condor/etc/condor_config", {st_mode=S_IFREG|0644,
st_size=88256, ...}) = 0
open("/opt/condor/etc/condor_config", O_RDONLY) = 3
open("/opt/condor/etc/condor_config", O_RDONLY) = 3

while on the machines that don't work, it looks in
write(3, "/usr/local/etc/condor_config", 28) = 28
open("/usr/local/etc/condor_config", O_RDONLY) = -1 ENOENT (No such
file or directory)

Are you setting the CONDOR_CONFIG variable in the environment
somewhere in teh startup scripts on the machine that works?  Log in as
root on both types of machines
and see if CONDOR_CONFIG is set by default.  Also check
/etc/init.d/condor- did it
get set there before the daemon is started.

I would guess you are setting CONDOR_CONFIG to
/opt/condor/etc/condor_config in /etc/init.d/condor or in /etc/profile

You can also test whether this fix works by setting CONDOR_CONFIG to the right
value before starting condor_master on the machines that don't work.