Re: [Condor-users] kbdd not working on windows server 2008

[<Greg.Hitchen@xxxxxxxx>]

Yep, I don't think condor_kbdd sends updates UNLESS there is console activity

and then will send it to the condor_startd within 5 secs.

 

Further checking of the logs show no X_EVENT_NOTIFICATION messages

overnight or weekends until during normal weekday hours when a user is

actively using the keyboard or mouse. These events are then received every

5 secs. In any case the startd know within 5 secs and can (or will in our config)

evict the job essentially immediately there is user activity on the execute node.

 

Cheers

 

Greg

 

 

---

From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ziliang Guo
Sent: Monday, 25 July 2011 10:27 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] kbdd not working on windows server 2008

During testing on a vanilla install of Condor I've seen updates not 
show up for quite some time.  I don't think the wakeup timer is set to 5 
seconds, unless we have differing behavior for when the kbdd believes a system 
is idle and when it is in use.  The notification code in kbdd was present 
before we adapted it for use on Windows over two years ago, so am really hazy 
right now.  Again, will doublecheck behavior once in the office 
tomorrow.  That kbdd can do a better job than its current iteration is 
however becoming very evident.

On Sun, Jul 24, 2011 at 9:09 PM, <Greg.Hitchen@xxxxxxxx> wrote:

Doesn't the condor_kbdd send an update to the condor_startd every 5 seconds?

That's certainly what appears to be happening according to the StartLog file

(I have replaced some IP numbers with * 's):

 

07/25/11 10:01:15 Received UDP command 427 (X_EVENT_NOTIFICATION) from  <*.*.146.156:13837>, access level ALLOW
07/25/11 10:01:15 Calling HandleReq <command_x_event> (0)
07/25/11 10:01:15 Return from HandleReq <command_x_event> (handler: 0.000s, sec: 0.000s)
07/25/11 10:01:20 Received UDP command 427 (X_EVENT_NOTIFICATION) from  <*.*.146.156:13837>, access level ALLOW
07/25/11 10:01:20 Calling HandleReq <command_x_event> (0)
07/25/11 10:01:20 Return from HandleReq <command_x_event> (handler: 0.000s, sec: 0.000s)
07/25/11 10:01:25 Received UDP command 427 (X_EVENT_NOTIFICATION) from  <*.*.146.156:13837>, access level ALLOW
07/25/11 10:01:25 Calling HandleReq <command_x_event> (0)
07/25/11 10:01:25 Return from HandleReq <command_x_event> (handler: 0.000s, sec: 0.000s)

Running the command:

 

condor_status -l -direct machinename | findstr ConsoleIdle

 

continuously shows this as well as ConsoleIdle cycles from 0 up to 5 (0,1,2,3,4,5), then back

to 0 and cycles again, etc. when it is run from the computer "machinename".

 

Without the -direct option you are querying the Collector rather than machinename directly

so there can be a delay of up to UPDATE_INTERVAL (default 300s = 5 min).

However the startd will see activity and take the appropriate action (if any) quickly.

 

Cheers

 

Greg

 

 

---

From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ziliang Guo

Sent: Monday, 25 July 2011 7:50 AM

To: Condor-Users Mail List
Subject: Re: [Condor-users] kbdd not working on windows server 2008

Uh, of course it doesn't if it's running like it does under XP.  If it's running under the Condor service in the system session, it can't see keyboard activity.  Which is why we've been trying to get it to run in the user session on user login.  Even when running under the user session, it can be up to 5 minutes before the startd is updated about keyboard/mouse activity.


--
Condor Project Windows Developer

_______________________________________________
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 Project Windows Developer