Re: [Condor-users] kbbd issues

["John (TJ) Knoeller" <johnkn@xxxxxxxxxxx>]

So the KBDD will exit if it is unable to open its log file. 

The log usually in the same directory as all other condor logs,  and the KBDD on windows runs as the logged on user,
so unless all users have write access to the $(LOG) directory, the KBDD will exit right after it starts if you use the default configuration.

If you don't want to give all users write access to the $(LOG) directory, you can just disable the KBDD log by
setting the config knob for it to NUL.

KBDD_LOG = NUL

the KBDD also has a bug that causes it to briefly create a visible console window (it's not supposed to).

It's not completely broken however.
-tj

On 2/3/2012 12:57 AM, Eric Abel wrote:

Will do...thanks Ziliang.

Eric
________________________________________
From: condor-users-bounces@xxxxxxxxxxx [condor-users-bounces@xxxxxxxxxxx] on behalf of Ziliang Guo [ziliang@xxxxxxxxxxx]
Sent: Thursday, February 02, 2012 3:55 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] kbbd issues

This is preliminary, but in the process of investigating the issue, I
am fairly confident in declaring kbdd busted in 7.6.1 (and it's
looking like it's been busted, again, for quite a few versions),
irrespective of the issue you saw, Eric.  I'll be digging into it more
tomorrow, but it looks like changes made to daemon core have ended up
fubaring kbdd on Windows.  My plans to replace kbdd with something
simpler and hopefully more robust have had its priority increased,
significantly.

As for the issue you saw, Eric, there's a connectivity issue that
seemed to have prevented kbdd from renewing its security session with
the startd.  This could easily range from a firewall issue to the kbdd
somehow using the wrong IP address or port when trying to talk to the
startd.  If you see the issue again, best bet would be to look at the
kbdd logs to see which IP and port it is trying to talk to, and
whether those match the IP and port of the machine and the startd.

Z

--
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-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/