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

Re: [condor-users] still shadow exceptions...

> 11/25 14:20:35 LogonUser(condor-reuse-vm1, ... ) failed with status
> 138511/25 14:20:35 ERROR "Failed to create a user nobody" at line 293 in
> file ..\src\condor_c++_util\uids.C

Status 1385 according to Microsoft is: "Logon failure: the user has not
been granted the requested logon type at this computer.".

Condor has to log on the condor-reuse-vm1 account so that it can run
the job as this user. Condor will attempt to log on this account first
as a Batch login, then as an Interactive login. It would appear that
this account does not have rights to do either. 

The easiest way to fix this is to delete the condor-reuse-vm1 account
and let Condor re-create it with the appropriate account rights. If
you're a Windows-admin type, you can go to Control Panel->Administrative
Tools->Local Security Policy and check out who's allowed (or denied) to
"Log on as batch job" or "Log on Locally". It's also important that the
condor-reuse-vmX accounts are members of the BUILITIN\User local group.

> So what is the deal with this user Nobody? I thought, that the
> condor-reuse-vm1 logs on the executing machine and does the work. But what
> is Nobody for?

That is just a carry-over from our unix code. The condor-reuse-vmX
accounts are considered analogous to unix's 'nobody' user. Admittedly,
it's a misleading error message. Sorry.

> The second thing I don't understand is, that my old workaround (give my
> account read/write-access to the folder) doesn't work anymore.

The starter is failing to logon the condor-reuse-vm1 account, so that's
where your problem is. Folder permissions aren't going to affect this

Condor Support Information:
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>