Subject: Re: [Condor-users] kbdd not working on windows server 2008
Erik, sorry for diverging from your topic.
I have a windows 2008 Standard server that runs Condor 7.6.1 as an execute
node and the kbdd does run on this machine. Would you mind restating the
problem, and I will see it I can duplicate it on our pool.
thanks,
mike
From:
Eric Abel <Eric.Abel@xxxxxxxxxx>
To:
Condor-Users Mail List <condor-users@xxxxxxxxxxx>
Date:
07/25/2011 10:02 AM
Subject:
Re: [Condor-users] kbdd not working
on windows server 2008
Sent by:
condor-users-bounces@xxxxxxxxxxx
It seems like this thread
has diverged from the original topic J.
Does anyone have any additional suggestions for troubleshooting the
original issue?
Thanks,
Eric
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx]
On Behalf Of Ziliang Guo
Sent: Sunday, July 24, 2011 7:27 PM
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:
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.
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