This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi all j2ee guru. l installed iplanet 6.5 on a solaris 8 box. After installation, l can run the "fortune" sample to quickly test out successful setup. However, as l try out various iplanet command at command prompt, l encountered lots of error message as follows 1) when l used "iasdeploy" to try to deploy sample "Helloworld" application, following error message occured. [ iasdeploy for iPlanet Application Server 6.5 Could not connect to LDAP server on xyz.test.com. port 389...retrying Could not connect to LDAP server on xyz.test.com. port 389...retrying Could not connect to LDAP server on xyz.test.com. port 389 as user cn=Directory Manager : Can't connect to the LDAP server GXBindInit: GXBindBasic failed GXContextInit: GXBindInit failed 2 [12/Nov/2002 17:42:20:0] error: ENGINE-context_init_failed: EngineClassSpace ContextModule.createContextInit failed: error: could not get context java.lang.NullPointerException at com.kivasoft.tools.KSReg.getSubKey(Unknown Source) at com.kivasoft.tools.KSReg.getSubKey(Unknown Source) at com.iplanet.ias.tools.iascli.DestInfo.initialize(Unknown Source) at com.iplanet.ias.tools.iascli.DestInfo.initLocalHost(Unknown Source) at com.iplanet.ias.tools.iascli.DestInfo.<init>(Unknown Source) at com.iplanet.ias.tools.iascli.IasCommand.getDestInfo(Unknown Source) at com.iplanet.ias.tools.iascli.IasCommand.preExecute(Unknown Source) at com.iplanet.ias.tools.buzz.cli.DeployAppCommand.preExecute(Unknown Source) at com.iplanet.ias.tools.iascli.IasCommand.execute(Unknown Source) at com.iplanet.ias.tools.iascli.IasCommandLineHandler.executeCommand(Unknown Source) at com.iplanet.ias.tools.iascli.IasCommandLineHandler.execute(Unknown Source) at com.iplanet.ias.tools.buzz.cli.IasDeploy.main(Unknown Source) ] 2) l used "ps" command to verify exisitence of LDAP server. Result is as follows. Why the owner of this process of "iplanet" even l run LDAP startup script in "root" identity ??? [ root@node0 /d01/iplanet/ias6/ias/bin> ps -ef | grep slapd iplanet 7908 1 0 17:17:38 ? 0:01 ./ns-slapd -D /d01/iplanet/ias6/slapd-websams-ed -i /d01/iplanet/ias6/slapd-web root 8477 7522 0 17:47:34 pts/3 0:00 grep slapd ] 3) then l tried out "iascontrol" command to try to shutdown an instance of iplanet app server. Following errors occured Could not connect to LDAP server on xyz.test.com. port 389...retrying Could not connect to LDAP server on xyz.test.com. port 389...retrying Could not connect to LDAP server on xyz.test.com. port 389 as user cn=Directory Manager : Can't connect to the LDAP server GXBindInit: GXBindBasic failed GXContextInit: GXBindInit failed 2 [12/Nov/2002 17:53:18:7] error: ENGINE-context_init_failed: EngineClassSpace ContextModule.createContextInit failed: error: could not get context Error in command. Please check arguments. It is very thankful someone can help me out !!! fox
hi There might be a better solution , but when I was faced with the same problem I had to reinstall as I was running out of time and could not hunt for the cause. If reinstallation is allright with you then please go ahead and do the same .
It is perfectly normal for the LDAP server to be running as a non-privileged user. The reason that you have to run the startup script as root is because port 389 is privileged. The server starts up as root so that it can bind the privileged port and then is switched over to a non-privileged user for security reasons. You are definitely having some sort of LDAP connectivity problem. My first troubleshooting steps would be : 1. Check netstat to see if there is a listener on port 389. 2. Test the resolution of the domain name from the command line. Perhaps xyz.test.com is not resolving properly. 3. Check the LDAP logs. The access log will tell you if the LDAP requests are reaching the LDAP server. The errors log will tell you whether the LDAP log is able to successfully start up and bind to the port. 4. Test the LDAP server with another LDAP client, such as an LDAP browser. David
Dear David thx a lot for your advice. In fact, l have already checked the log file before, it can startup properly. Would u please telling me where l can get LDAP browser ? By the way, Yesterday, l just brought the book, iplanet app server: Design and Building J2EE app written by u. regards Danny
Joined: Jul 19, 2002
Netscape 4.x could accept LDAP queries right in the browser window. (Which was incredibly useful.) If (not surprisingly) you don't have a copy of NN 4.x around, most mail clients also allow you to connect to LDAP servers. There are also some dedicated LDAP browsing tools. Doing a freshmet.net or google.com search will turn up a bunch of them, most of which are freely available. David