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

RE: [condor-users] Condor locking Windows NT accounts

Title: RE: [condor-users] Condor locking Windows NT accounts

Hi Colin

Yes, the sequence of events you list are correct. There is nothing that I can think of that would reset the registry key. We do not use roaming profiles. Could it be because there were jobs in the queue, submitted by the user, which were still queued after his password had changed? This account lock out issue has been experienced by a couple of our users and is about the only cause we could come up with.


-----Original Message-----
From: Colin Stolley [mailto:stolley@xxxxxxxxxxx]
Sent: Wednesday, 18 February 2004 7:04 AM
To: condor-users@xxxxxxxxxxx
Subject: Re: [condor-users] Condor locking Windows NT accounts


So if I understand you correctly, the sequence of events is:

1. Password is set on the account, condor_store_cred add is run with
the same password, Condor jobs are submitted and run happily.

2. The account password expires and a new password is set on the account.

3. condor_store_cred add is run again, with the new account password.

4. The user's account gets locked out, presumably because step 3 is
failing to take affect for some reason and Condor is repeatedly attempting
to log on the user with the wrong password.

So the question in this case is why condor_store_cred isn't properly
updating the password. Without any additional debugging information,
it's hard to say, but I wonder if it's possible that the registry key
that Condor stores the passwords in is getting wiped out somehow? Do you
use roaming profiles, or some other mechanism that might clear (or reset)
registry keys on the system?

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


NOTICE - This message and any attached files may contain information that is confidential and/or subject of legal privilege intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein.  If you have received this message in error please notify the sender immediately and delete the message.