[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Trouble starting condor daemons - CONDOR_IDSerror
- Date: Tue, 23 Oct 2007 14:10:20 +0100
- From: Craig Bruce <pcxcb1@xxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Trouble starting condor daemons - CONDOR_IDSerror
Title: Re: [Condor-users] Trouble starting condor daemons - CONDOR_IDSerror
>1) Check that user 1250.551 has permission to all files used by condor. logs, config and for linux/os xa temp lock dir in /tmp..if >not..correct the file permissions.
All the condor install is owned by root, permission 755. /tmp is world writable. Local dir is owned by condor user/group.
>2) Check that the problematic machine is in >the HOSTALLOW_ADMINISTRATOR, HOSTALLOW_READ,HOSTALLOW_WRITE parameters.
HOSTALLOW_ADMINISTRATOR = $(CONDOR_HOST)
HOSTALLOW_READ = *
HOSTALLOW_WRITE = *
I altered all three to *, but makes no difference.
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.
This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.