Hi! YES! IT WORKS!
THANK YOU! Sincerely, Polina 21.12.2017, 11:04, "Li, Jiajia" <[email protected]>: > Hi, > I think the kdc has been initialized from your log: > > 2017-12-18 10:10:11 DEBUG{LdapNetworkConnection.java:2026}--------> > MessageType : SEARCH_RESULT_ENTRY > Message ID : 2 > Search Result Entry > Entry > dn: uid=krbtgt/BIGDATA.COM,dc=bigdata,dc=com > > Could you remove the " krbtgt/BIGDATA.COM "and" kadmin/BIGDATA.COM " entry > from LDAP, then rerun kdcinit? > > Thanks, > Jiajia > > -----Original Message----- > From: Maslova Polina [mailto:[email protected]] > Sent: Monday, December 18, 2017 5:57 PM > To: [email protected] > Subject: Re: LDAP backend > > I have attached the log of kdcinit with the results of search. > When I tuned on the debug on Apache DS I recieve this in log: > > WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - Unexpected > exception forcing session to close: sending disconnect notice to client. > java.io.IOException: Соединение разорвано другой стороной (= The connection > was shut off by the other side ) > at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > at sun.nio.ch.IOUtil.read(IOUtil.java:197) > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) > at > org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:317) > at > org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:45) > at > org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:683) > at > org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:659) > at > org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:648) > at > org.apache.mina.core.polling.AbstractPollingIoProcessor.access$600(AbstractPollingIoProcessor.java:68) > at > org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1120) > at > org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > > 18.12.2017, 12:49, "Emmanuel Lécharny" <[email protected]>: >> Le 18/12/2017 à 09:53, Maslova Polina a écrit : >>> Dear Jiajia! >>> >>> In the kdcinit log I have this >>> >>> 2017-12-18 10:10:11 DEBUG{LdapNetworkConnection.java:2288}-Search >>> successful : MessageType : SEARCH_RESULT_DONE >>> Message ID : 2 >>> Search Result Done >>> Ldap Result >>> Result code : (SUCCESS) success >>> Matched Dn : '' >>> Diagnostic message : '' >>> >>> 2017-12-18 10:10:11 DEBUG{LdapNetworkConnection.java:511}-Removing >>> <2, org.apache.directory.ldap.client.api.future.SearchFuture> >>> 2017-12-18 10:10:11 DEBUG{SearchCursorImpl.java:210}-Closing >>> SearchCursorImpl >>> org.apache.directory.ldap.client.api.SearchCursorImpl@74650e52 >>> 2017-12-18 10:10:11 DEBUG{SearchCursorImpl.java:225}-Closing >>> SearchCursorImpl >>> org.apache.directory.ldap.client.api.SearchCursorImpl@74650e52 >>> 2017-12-18 10:10:11 INFO{LdapIdentityBackend.java:129}-closed connection >>> with LDAP. >>> 2017-12-18 10:10:11 DEBUG{AbstractIdentityBackend.java:112}-stop >>> called >>> 2017-12-18 10:10:11 DEBUG{LdapNetworkConnection.java:777}-received a >>> NoD, closing everything >>> >>> at the end of the log. >>> >>> Is it a problems with Apache Directory? >> >> Clearly, no. >> >> The server just send you a SearchResultDone, which is the normal >> response when a search request has been processed. We don't have any >> information about how may entries have been sent back, as the log have >> been truncated just before the SearchResultDone (it would be >> interesting to get the previous logs, especially the ones where the >> searchRequest is done, and the result entries returned, if any). >> However, again, this is an expected response. >> >> The LDAP API client then close the search cursor, as expected when the >> search has been processed fully. >> >> What would be interesting is to know why the LdapIdentityBackend class >> closed the LDAP connection (this is a Kerby class, it's in teh >> doStop() method, and it seems that the close was properly handled). >> >> Jiajia ? >> >> -- >> Emmanuel Lecharny >> >> Symas.com >> directory.apache.org
