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

Re: [Condor-users] Problems with Condor



Mr. Zurek,

Thank you for the fast response! I will look into this.

The problem is that I am running on a Rocks cluster and the /home/condor folder is exported via NFS to all the compute nodes.

Greetings from cold Ohio!

Vasil


On Thu, 2007-11-15 at 00:33 +0100, Marian ZUREK wrote:
Hi,

You may want to verify whether the condor user (condor?) has enough  
rights for writing into the directory: /home/condor/spool....  
Additionally make sure that the condor gid.uid as set in the  
condor_config.local (CONDOR_IDS) are in line with the OS data (/ets/ 
passwd file).

Hope this helps.
Marian
--
Marian ZUREK
CERN - IT/GD, ETICS
CH-1211 Geneve 23
Switzerland




On 14 nov. 07, at 23:37, Vasil Lalov wrote:

> Hello everyone,
>
> I am working on a fresh Condor installation. I followed all the  
> configuration steps in the documentation. I am trying to submit a  
> job from the front end of the cluster and everything works fine. I  
> can see the job sitting in IDLE state in the queue.
>
> This is what is being stored in the condor logs of the COMPUTE nodes:
>
>
> 11/14 17:30:30 (pid:4040) DaemonCore: Command received via UDP from  
> host <10.1.1.1:32864>
> 11/14 17:30:30 (pid:4040) DaemonCore: received command 421  
> (RESCHEDULE), calling handler (reschedule_negotiator)
> 11/14 17:30:30 (pid:4040) Sent ad to central manager for lalovv@xxxxxxxxxxx
> 11/14 17:30:30 (pid:4040) Sent ad to 1 collectors for lalovv@xxxxxxxxxxx
> 11/14 17:30:30 (pid:4040) Called reschedule_negotiator()
> 11/14 17:30:32 (pid:4040) Inserting new attribute Scheduler into non- 
> active cluster cid=31 acid=-1
> 11/14 17:33:25 (pid:4040) DaemonCore: Command received via TCP from  
> host <10.1.1.1:33897>
> 11/14 17:33:25 (pid:4040) DaemonCore: received command 478  
> (ACT_ON_JOBS), calling handler (actOnJobs)
> 11/14 17:33:25 (pid:9901) statfs() failed: 13/Permission denied
> 11/14 17:33:25 (pid:9901) Attempting to chown '/home/condor/spool/ 
> cluster31.proc0.subproc0', but it doesn't appear to exist.
> 11/14 17:33:25 (pid:9901) Error: Unable to chown '/home/condor/spool/ 
> cluster31.proc0.subproc0' from 500 to 407.407
> 11/14 17:33:25 (pid:9901) (31.0) Failed to chown /home/condor/spool/ 
> cluster31.proc0.subproc0 from 500 to 407.407.  User may run into  
> permissions problems when fetching sandbox.
>
>
> Any ideas?
>
>
>
>
> ==
> Vasil Lalov
> Department Of Computer Science
> Bowling Green State University
> Bowling Green, OH 43403
> lalovv@xxxxxxxx
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx  
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/

_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at: 
https://lists.cs.wisc.edu/archive/condor-users/
==
Vasil Lalov
Department Of Computer Science
Bowling Green State University
Bowling Green, OH 43403
lalovv@xxxxxxxx