Mailing List Archives

Authenticated access

 		[Computer Systems Lab]

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

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

These show that your LOG directory allows READ but not WRITE access to BUILTIN\Users. 
In particular the kbdlog can be read but not written to.
I would suggest that you give BUILTIN\Users write access to KbdLog and see if that fixes the problem. 
if not, try giving BUILTIN\Users full access to the LOG directory.
From your earlier posts, it appears that condor_kbdd is starting and then quitting. so that suggests that it's excepting because it can't write to the log file despite the code we added to detect and deal with the situation. I suspect that the particular pattern of rights access is different from what we 
tested and it's somehow fooling the access check in the kbdd.
The other possibility that I can think of is that the kbdd is unable to locate or read from condor_config or one of your other config files that it includes and it's quitting because of that. 

-tj

On 7/22/2011 2:56 PM, Eric Abel wrote:

Here are the outputs of the commands you wanted me to execute:

d:\condor NT AUTHORITY\SYSTEM:(F)
           BUILTIN\Administrators:(I)(OI)(CI)(F)
           NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)
           CREATOR OWNER:(I)(OI)(CI)(IO)(F)
           BUILTIN\Users:(I)(OI)(CI)(RX)
           BUILTIN\Users:(I)(CI)(AD)
           BUILTIN\Users:(I)(CI)(WD)

Successfully processed 1 files; Failed processing 0 files

d:\condor\bin NT AUTHORITY\SYSTEM:(F)
               BUILTIN\Administrators:(I)(OI)(CI)(F)
               NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)
               CREATOR OWNER:(I)(OI)(CI)(IO)(F)
               BUILTIN\Users:(I)(OI)(CI)(RX)
               BUILTIN\Users:(I)(CI)(AD)
               BUILTIN\Users:(I)(CI)(WD)

Successfully processed 1 files; Failed processing 0 files

d:\condor\log NT AUTHORITY\SYSTEM:(F)
               BUILTIN\Administrators:(I)(OI)(CI)(F)
               NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)
               CREATOR OWNER:(I)(OI)(CI)(IO)(F)
               BUILTIN\Users:(I)(OI)(CI)(RX)
               BUILTIN\Users:(I)(CI)(AD)
               BUILTIN\Users:(I)(CI)(WD)

Successfully processed 1 files; Failed processing 0 files

d:\condor\spool NT AUTHORITY\SYSTEM:(F)
                 BUILTIN\Administrators:(I)(OI)(CI)(F)
                 NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)
                 CREATOR OWNER:(I)(OI)(CI)(IO)(F)
                 BUILTIN\Users:(I)(OI)(CI)(RX)
                 BUILTIN\Users:(I)(CI)(AD)
                 BUILTIN\Users:(I)(CI)(WD)

Successfully processed 1 files; Failed processing 0 files

d:\condor\condor_config BUILTIN\Administrators:(I)(F)
                         NT AUTHORITY\SYSTEM:(I)(F)
                         VMS\eabel:(I)(F)
                         BUILTIN\Users:(I)(RX)

Successfully processed 1 files; Failed processing 0 files

d:\condor\log\kbdlog BUILTIN\Administrators:(F)
                      BUILTIN\Administrators:(I)(F)
                      NT AUTHORITY\SYSTEM:(I)(F)
                      BUILTIN\Users:(I)(RX)

Successfully processed 1 files; Failed processing 0 files

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of John (TJ) Knoeller
Sent: Friday, July 22, 2011 11:57 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] kbdd not working on windows server 2008

If condor_kbdd is starting up then exiting, the usual reason is that it
can't access something it needs to access.

please run the following commands  and send me the output

      icacls c:\condor
      icacls c:\condor\bin
      icacls c:\condor\log
      icacls c:\condor\spool
      icacls c:\condor\condor_config*
      icacls c:\condor\log\kbdlog

thanks
-tj

On 7/22/2011 11:48 AM, Eric Abel wrote:

 From what I can tell this was the 64-bit registry editor.  It was the one named regedit in the syswow64 folder.  There is also a regedt32, which I assume is the 32-bit editor.

So if there is a kbbd running as the logged on user, then it's not showing up in task manager.  It's possible that it's starting then exiting, because when I log on, I see the command prompt flash briefly, as usual with a machine running condor.

Eric

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of John (TJ) Knoeller
Sent: Friday, July 22, 2011 8:50 AM
To: condor-users@xxxxxxxxxxx
Subject: Re: [Condor-users] kbdd not working on windows server 2008

I can't tell from looking at the registry photo whether this is the 64
bit or 32 bit registry.   but it shouldn't matter.

Maybe I missed it, but I don't think you ever said whether there was a
condor_kbdd running as the
logged on user as well as the one running as system.   There should be -
that's what this key is
designed to do.

If condor_kbdd isn't running as the user, then we need to figure out
why.  did it start and then exit? or
did it not start?

tj

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

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