Re: [Condor-users] condor-reuse-vm2 Job Owner in Windows

["Chin, Tammy" <chint@xxxxxxx>]

Diane,

I didn't see the email with the links that Ian sent you, so I may be repeating information that you already have.

Did you do the condor_store_cred add -c -p <password> on each of your machines in the pool? 

Also, I find with windows, you may have to restart the condor service on the master node to get it to realize you have changed the credd information.

The error log that you want to look at is your creddlog. If you had forgotten to set up the pool password there should be a error message in the creddlog similar to:

5/15 13:40:18 sspi_client_auth() exiting
5/15 13:40:18 SEC_DEBUG_PRINT_KEYS is undefined, using default value of False
5/15 13:40:18 SEC_DEBUG_PRINT_KEYS is undefined, using default value of False
5/15 13:40:18 SEC_DEBUG_PRINT_KEYS is undefined, using default value of False
5/15 13:40:18 SEC_DEBUG_PRINT_KEYS is undefined, using default value of False
5/15 13:40:24 SEC_DEBUG_PRINT_KEYS is undefined, using default value of False
5/15 13:40:24 getStoredCredential(): Could not locate credential for user 'condor_pool@xxxxxxx'
5/15 13:40:24 getStoredCredential(): Could not locate credential for user 'condor_pool@xxxxxxx'
5/15 13:40:44 condor_read(): timeout reading buffer.
5/15 13:40:44 IO: Failed to read packet header
5/15 13:40:44 AUTHENTICATE: handshake failed!
5/15 13:40:44 DC_AUTHENTICATE: authenticate failed: AUTHENTICATE:1002:Failure performing handshake|AUTHENTICATE:1004:Failed to authenticate using PASSWORD
5/15 13:42:27 SEC_DEBUG_PRINT_KEYS is undefined, using default value of False

If not, the creddlog should give you an idea of what is really the issue.

Hope this helps,

Tammy


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of diane
Sent: October 23, 2007 10:08 PM
To: 'Condor-Users Mail List'
Subject: [Condor-users] condor-reuse-vm2 Job Owner in Windows


Hi Ian,

Thanks for the info sites.  They were very helpful.

However, I'm still unable to get the secondary processes that 
are started by a job in the condor queue running as owner 'diane',
to also run as user 'diane'.  

When I make changes to the condor configuration,
as described in the documentation (I think), restart condor, 
and then submit the job, the job now hangs 
in the queue (and doesn't even get started).

Maybe you can see what I'm doing wrong.

I tried setting the following in condor_config:

   CREDD_HOST = $(CONDOR_HOST):$(CREDD_PORT)
   CREDD_CACHE_LOCALLY = True
   QUEUE_ALL_USERS_TRUSTED = True
   STARTER_ALLOW_RUNAS_OWNER = True

And put the following into my condor.submit file:

	+Owner = "diane"
      run_as_owner = True

But the job hangs in the queue.
Note that when I remove the 'run_as_owner' and '+Owner' statements,
and resubmit, the job starts and runs to completion (although it's sub
processes 
run as 'condor-reuse-vm2', which I'm trying to avoid).

Any help would be appreciated.
Thanks,
Diane

The condor logs for the job that hangs indicate the following:

StartLog:
No new entries for the submission

CollectorLog:
10/23 15:39:10 (Sending 1 ads in response to query)
10/23 15:39:10 (Sending 6 ads in response to query)
10/23 15:39:10 Got QUERY_STARTD_PVT_ADS
10/23 15:39:10 (Sending 2 ads in response to query)

MatchLog:
10/23 15:39:10       Rejected 630.0 diane@winxp-dev-01 <192.168.2.105:1221>:
no match found

SchedLog:
10/23 15:39:10 (pid:128) DaemonCore: Command received via UDP from host
<192.168.2.105:1486>
10/23 15:39:10 (pid:128) DaemonCore: received command 421 (RESCHEDULE),
calling handler (reschedule_negotiator)
10/23 15:39:10 (pid:128) Sent ad to central manager for diane@winxp-dev-01
10/23 15:39:10 (pid:128) Sent ad to 1 collectors for diane@winxp-dev-01
10/23 15:39:10 (pid:128) Called reschedule_negotiator()
10/23 15:39:10 (pid:128) Activity on stashed negotiator socket
10/23 15:39:10 (pid:128) Negotiating for owner: diane@winxp-dev-01
10/23 15:39:10 (pid:128) Checking consistency running and runnable jobs
10/23 15:39:10 (pid:128) Tables are consistent
10/23 15:39:10 (pid:128) Out of servers - 0 jobs matched, 1 jobs idle, 1
jobs rejected

NegotiatorLog
10/23 15:39:10 ---------- Started Negotiation Cycle ----------
10/23 15:39:10 Phase 1:  Obtaining ads from collector ...
10/23 15:39:10   Getting all public ads ...
10/23 15:39:10   Sorting 6 ads ...
10/23 15:39:10   Getting startd private ads ...
10/23 15:39:10 Got ads: 6 public and 2 private
10/23 15:39:10 Public ads include 1 submitter, 2 startd
10/23 15:39:10 Phase 2:  Performing accounting ...
10/23 15:39:10 Phase 3:  Sorting submitter ads by priority ...
10/23 15:39:10 Phase 4.1:  Negotiating with schedds ...
10/23 15:39:10   Negotiating with diane@winxp-dev-01 at <192.168.2.105:1221>
10/23 15:39:10 0 seconds so far
10/23 15:39:10     Request 00630.00000:
10/23 15:39:10       Rejected 630.0 diane@winxp-dev-01 <192.168.2.105:1221>:
no match found
10/23 15:39:10     Got NO_MORE_JOBS;  done negotiating
10/23 15:39:10 ---------- Finished Negotiation Cycle ----------



_______________________________________________
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: 
https://lists.cs.wisc.edu/archive/condor-users/


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian Chesal
Sent: Monday, October 22, 2007 6:00 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] condor-reuse-vm2 Job Owner in Windows

> Why is that?  
> Is there a way to change that job to run as 'diane'?
> 
> I am using condor.6.8.5 under Windows XP.
> Thanks,

The way Window's jobs are run and how local accounts and permissions
come into play is explained in detail here:

http://www.cs.wisc.edu/condor/manual/v6.8/6_2Microsoft_Windows.html#SECT
ION00725000000000000000

And here's how you can have Window's jobs run as domain accounts other
than the temporary local accounts Condor creates:

http://www.cs.wisc.edu/condor/manual/v6.8/6_2Microsoft_Windows.html#SECT
ION00723000000000000000

That should get you started!

- Ian


Confidentiality Notice.  This message may contain information that is
confidential or otherwise protected from disclosure.
If you are not the intended recipient, you are hereby notified that any use,
disclosure, dissemination, distribution, 
or copying of this message, or any attachments, is strictly prohibited.  If
you have received this message in error, 
please advise the sender by reply e-mail, and delete the message and any
attachments.  Thank you.




_______________________________________________
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: 
https://lists.cs.wisc.edu/archive/condor-users/



_______________________________________________
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: 
https://lists.cs.wisc.edu/archive/condor-users/
CONFIDENTIAL AND PRIVILEGED INFORMATION NOTICE

This e-mail, and any attachments, may contain information that
is confidential, subject to copyright, or exempt from disclosure.
Any unauthorized review, disclosure, retransmission, 
dissemination or other use of or reliance on this information 
may be unlawful and is strictly prohibited.  

AVIS D'INFORMATION CONFIDENTIELLE ET PRIVILÉGIÉE

Le présent courriel, et toute pièce jointe, peut contenir de 
l'information qui est confidentielle, régie par les droits 
d'auteur, ou interdite de divulgation. Tout examen, 
divulgation, retransmission, diffusion ou autres utilisations 
non autorisées de l'information ou dépendance non autorisée 
envers celle-ci peut être illégale et est strictement interdite.