AD problem. There are currently no logon servers available to service the logon request
-
2011年6月28日 10:35
I have a cluster with HPC Pack Sp2 Beta on it and I got the following error when I want to run Diagnostic or when I access he web portal:
There are currently no logon servers available to service the logon request.
I installed the cluster with a LOCAL administrator account, because I didn't find exactly which rights needed for install. Also the cluster build for evaluation purpose and I can't change the network configuration on it. The nodes is part of an enterprise network, and the AD controller is working well, but I don't have write access on it.
Can somebody suggest something how can I find a workaround for the problem?
P.S: The cluster build for evaluation. I don't use any auto deploying features, just azure burst scenarios.
すべての返信
-
2011年6月29日 11:08I use the following user to run tests and install: CCNT\s138782 and Domain controller: cns.cranfield.ac.uk
The following details I found in the logs:
Authentication failed when I want to start the diagnostic:
</Event><Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /><EventID>4625</EventID><Version>0</Version><Level>0</Level><Task>12544</Task><Opcode>0</Opcode><Keywords>0x8010000000000000</Keywords><TimeCreated SystemTime="2011-06-29T11:03:26.580797300Z" /><EventRecordID>397328</EventRecordID><Correlation /><Execution ProcessID="544" ThreadID="4320" /><Channel>Security</Channel><Computer>MS-HPC-Head.cns.cranfield.ac.uk</Computer><Security /></System><Data Name="SubjectUserSid">S-1-5-18</Data><Data Name="SubjectUserName">MS-HPC-HEAD$</Data><Data Name="SubjectDomainName">CCNT</Data><Data Name="SubjectLogonId">0x3e7</Data><Data Name="TargetUserSid">S-1-0-0</Data><Data Name="TargetUserName" /><Data Name="TargetDomainName" /><Data Name="Status">0xc000005e</Data><Data Name="FailureReason">%%2304</Data><Data Name="SubStatus">0x0</Data><Data Name="LogonType">3</Data><Data Name="LogonProcessName">C</Data><Data Name="AuthenticationPackageName">Kerberos</Data><Data Name="WorkstationName">MS-HPC-HEAD</Data><Data Name="TransmittedServices">-</Data><Data Name="LmPackageName">-</Data><Data Name="KeyLength">0</Data><Data Name="ProcessId">0x5e8</Data><Data Name="ProcessName">C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\HpcDiagnostics.exe</Data><Data Name="IpAddress">-</Data><Data Name="IpPort">-</Data></EventData>
Hpc event about the error:
</Event><Provider Name="Microsoft-HPC-Diagnostics" Guid="{5FD636C3-5ADD-4564-93A3-C8BAB2527FCA}" /><EventID>7</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x2000000000000000</Keywords><TimeCreated SystemTime="2011-06-29T11:03:26.583727100Z" /><EventRecordID>237</EventRecordID><Correlation /><Execution ProcessID="1512" ThreadID="1716" /><Channel>Windows HPC Server</Channel><Computer>MS-HPC-Head.cns.cranfield.ac.uk</Computer><Security UserID="S-1-5-18" /></System><Data Name="Message">There are currently no logon servers available to service the logon request.</Data><Data Name="ExceptionString">Exception detail: System.Security.SecurityException: There are currently no logon servers available to service the logon request. at System.Security.Principal.WindowsIdentity.KerbS4ULogon(String upn) at System.Security.Principal.WindowsIdentity..ctor(String sUserPrincipalName, String type) at System.Security.Principal.WindowsIdentity..ctor(String sUserPrincipalName) at Microsoft.Hpc.Diagnostics.Controller.Utilities.CreateJob(ISchedulerStore store, String requestedBy, StoreProperty[] jobProps) at Microsoft.Hpc.Diagnostics.Controller.PreStepFinishedHandler.ScheduleRunWithTaskResult(DiagnosticTestRun testRun, DiagnosticTest test, StepResult result) at Microsoft.Hpc.Diagnostics.Controller.PreStepFinishedHandler.ExecuteInternal(DiagnosticTestRun testRun) at Microsoft.Hpc.Diagnostics.Controller.StateHandlerBase.Execute() The Zone of the assembly that failed was: MyComputer Current stack: at Microsoft.Hpc.Diagnostics.DiagnosticsTracing.TraceException(String facility, Exception exception) at Microsoft.Hpc.Diagnostics.Controller.StateHandlerBase.Execute() at Microsoft.Hpc.Diagnostics.Controller.DiagnosticsController.RunStateHandlers(Object o) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)</Data></EventData> -
2011年8月5日 15:07You probably need Domain Admin rights to setup the HPC Cluster to be part of the domain correctly. You may want to setup a test domain first, then setup your HPC eval on that test domain. I wouldn't use the production domain to run the eval.