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

Re: [condor-users] transfer files problem



Hello,

about that local account, I have to disagree. It is not created and deleted every time a job is started and finished, it is always there. If the machine is not running a job, it is disabled, but it becomes enabled, if a job starts. I saw it live. Open the local-accounts-window. Then start a job on that machine. You will see, that the account switches from disabled to enabled, if the job starts to run. And as far as I remember, the account- rights were not changed by this.
Mark, you said something about "many potential problems which cause shadow exception". Do you know any more concrete problems which causes these exceptions. It would be great, if you let me know. Maybe then I'm going to find my problem with condor and the shadow execeptions.


Which of you guys actually use Condor under Win2k?

Thomas


No, I think it is a problem of permissions. The problem is NOT on the
execution machine, as according to the logs, shadow can not read the
file it wanted to transfer, and it is the first thing it did before anything else. I would still suggest to try and check permissions. You are right, Condor uses this "condor-reuse" account only on execution
machines, when running the job. As far as I know, it recreates that
account every time it attempts to invoke a job, this is the reason why
your change did not actually change anything. And finally, there are so
many potential problems which cause "shadow exception", that you can't
really understand the reason only from that message.


On Thu, 2003-10-02 at 16:50, Thomas Bauer wrote:
When I understand it right, on every client there is a local user "condor-reuse" installed. This user is per default disabled, but if a job should be run on this machine it is enabled by condor. Because of that, I gave this user the fully, administrative rights, but this didn't change anything. The same "shadow-exception" and "can no longer talk..."-error occured.

I don't think, that this is a privileg-problem, there must be a problem in the network-communication.

Just my oppinion,
Thomas

Mark Silberstein schrieb:

>If it was so, Condor could be run from mapped drive, but it can't.
>In any case, I would like to use this opportunity and ask Condor
>developers to explain to us under which credentials runs shadow.
>
>On Thu, 2003-10-02 at 16:21, Alexander Klyubin wrote:
> >
>>Hm. I thought shadows were supposed to be running with same privileges >>as the user who submitted the job. This way they can read and write what >>the user can read and write. May be it does not apply to Windows though...
>>
>>Alexander Klyubin
>>
>>Mark Silberstein wrote:
>> >>
>>>I think that you need to make the directory C:\Condor\examples\prueba
>>>and all its contents readable/writable for "Everyone". >>> >>>
>>Condor Support Information:
>>http://www.cs.wisc.edu/condor/condor-support/
>>To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
>>unsubscribe condor-users <your_email_address>
>> >>
>
>Condor Support Information:
>http://www.cs.wisc.edu/condor/condor-support/
>To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
>unsubscribe condor-users <your_email_address>
>
>
>.
>
> >



Condor Support Information: http://www.cs.wisc.edu/condor/condor-support/ To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with unsubscribe condor-users <your_email_address>

Condor Support Information: http://www.cs.wisc.edu/condor/condor-support/ To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with unsubscribe condor-users <your_email_address>






-- Universität Münster Institut für Festkörpertheorie Condor Support Information: http://www.cs.wisc.edu/condor/condor-support/ To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with unsubscribe condor-users <your_email_address>