[Condor-users] TRUST_UID_DOMAIN works (was) RE: Initial installation - I don't understand whythejob cannot write its own file?

["Atwood, Robert C" <r.atwood@xxxxxxxxxxxxxx>]

 It seems that I dd not try TRUST_UID_DOMAIN yet, this appears to work
so far.

I think it is because the master has 2 names, master.beowulf.cluster and
xxxxx.imperial.ac.uk , each of the nodes is nodexx.beowulf.cluster. But
I still don't quite understand why specifying the interface directly in
the config file does not then pickup the name associated with the
cluster network. 'Ping' picks it up . Condor_status displays the
imperial college host name for the master, though.


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of bruce
Sent: 31 July 2006 20:26
To: 'Condor-Users Mail List'
Subject: Re: [Condor-users] Initial installation - I don't understand
whythejob cannot write its own file?

hi robert.

i'm no guru! but i've just recently got a 2 node master/client condor
setup to more or less work. i can submit a job, which queues up copies
of a perl script that then appear to get run on the two machines..

i can send you the condor_config/local config files that i have if you
think it might help..

-bruce


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Atwood, Robert C
Sent: Monday, July 31, 2006 12:18 PM
To: Condor-Users Mail List
Subject: [Condor-users] Initial installation - I don't understand why
thejob cannot write its own file?


 Hi,
I have installed Condor on a small cluster on its own private network.
The master has 2 interfaces (outside network , cluster network). I've
got it configured so that jobs can be submitted and they run on the
nodes, with minimal chages to the default configuration. 

However, there is a peculiar problem that I cannot figure out.

When the (vanilla) job starts, the output file is created, belongong to
the submitting user, with permissions -rw-r--r--  Then the job gets
held, with the log message: 

 "Error from starter on vm2@xxxxxxx : Failed to open
'/home/myuser/q/loop.out' as standard output: Permission denied (errno
13)"


The job runs as  'nobody',  but the file is created with ownership of
the submitting user. This doesn't seem right. 

I tried altering the UID_DOMAIN to all different things that I could
think of (domain of the master's outside, domain of the private network,
* ) with no difference in this behaviour. 

I thought this file should be created in /local/condor/execute , where
/local/condor is defined in the configuration file by LOCAL_DIR, not in
the submitting working directory, anyways? That is what I would like, I
thought that was the default for vanilla jobs? 


Any suggestions appreciated,

Robert


loopit.c:
#include <stdio.h>
#include <unistd.h>
int main (){
  int i;
  for(i=0;i<100;i++){
  sleep(1);
  printf("%i\n",i);
  }
}


loop.submit:

########################
# Submit description file for loop program
########################
Executable     = loopit
Universe       = vanilla
Output         = loop.out
Log            = loop.log
TARGET.FileSystemDomain = *
Queue

_______________________________________________
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 either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR