[Swift-user] condor on communicado problem

[Hodgess, Erin]

I tried the following:

[erin at communicado ~]$  voms-proxy-init
-bash: voms-proxy-init: command not found
[erin at communicado ~]$ 

But this is not working either.

Thanks,
Erin


Erin M. Hodgess, PhD
Associate Professor
Department of Computer and Mathematical Sciences
University of Houston - Downtown
mailto: hodgesse at uhd.edu



-----Original Message-----
From: yecartes at gmail.com on behalf of Allan Espinosa
Sent: Mon 7/6/2009 2:16 PM
To: Hodgess, Erin
Cc: swift-user at ci.uchicago.edu
Subject: Re: [Swift-user] condor on communicado problem
 
Hi Erin,

under what VO is your proxy when you accessed the resource?  each VO
runs under a different userspace so you can't access Engage user
directories if the vo with you current proxy is not using engage.

to make sure you get the right VO, you can use voms-proxy-init

-Allan

2009/7/6 Hodgess, Erin <HodgessE at uhd.edu>:
> Hi again, Swift People:
>
> I'm on communicado, trying to run swift via condor (instead of gram).
>
> I generated my sites file and selected one location.
>
> Here is my output:
>
> [erin at communicado swift1]$ swift -tc.file tc.test.data -sites.file
> sites1k.xml wc1a.swift
> Swift svn swift-r2998 (swift modified locally) cog-r2427
>
> RunID: 20090706-1334-iq5phkm6
> Progress:
> Progress:  Selecting site:13  Initializing site shared directory:2
> Progress:  Selecting site:10  Initializing site shared directory:5
> Progress:  Selecting site:9  Initializing site shared directory:6
> Progress:  Selecting site:8  Initializing site shared directory:7
> Progress:  Selecting site:7  Initializing site shared directory:8
> Progress:  Selecting site:6  Initializing site shared directory:9
> Progress:  Selecting site:5  Initializing site shared directory:10
> Progress:  Selecting site:4  Initializing site shared directory:11
> Progress:  Selecting site:3  Initializing site shared directory:12
> Progress:  Selecting site:2  Initializing site shared directory:13
> Progress:  Selecting site:2  Initializing site shared directory:13
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Progress:  Initializing site shared directory:15
> Execution failed:
>         Could not initialize shared directory on
> Clemson-ciTeam_osgce.cs.clemson.edu
> Caused by:
>         org.globus.cog.abstraction.impl.file.FileResourceException: Cannot
> create directory /export/osg/data/engage/tmp
> Caused by:
>         Server refused performing the request. Custom message: Server
> refused creating directory (error code 1) [Nested exception message:  Custom
> message: Unexpected reply: 500-Command failed :
> globus_gridftp_server_file.c:globus_l_gfs_file_mkdir:554:
> 500-System error in mkdir: Permission denied
> 500-A system call failed: Permission denied
> 500 End.]
> [erin at communicado swift1]$
>
> This was using all of the values from the sites file.
>
> The directory that the sites file has is not present.
>
> Does anyone have any suggestions, please?
>
> Thanks in advance,
> Erin
>
> Erin M. Hodgess, PhD
> Associate Professor
> Department of Computer and Mathematical Sciences
> University of Houston - Downtown
> mailto: hodgesse at uhd.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-user/attachments/20090706/d7c8ffec/attachment.html>