Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tomcat not loading

Status
Not open for further replies.

pagy

Technical User
Sep 23, 2002
1,162
GB

On one server that has been built into a tree tomcat will not load, the error on the logger screen is:

Error "tccheck:LDAP is not up yet:waiting
LDAP connectivity not found on ldap://localhost:636
Please load NLDAP and then manually execute command: sys:/tomcat/4/bin/startup

I followed TID 10087091 which tells how to export the host certificate but when I did this I get an error about not having rights to modify the objects in the container.

If I run the tomcat commands manually tomcat loads fine.

This only happens on one server, any other server I build and put in the tree is fine.

To try and fix I decided to remove the server from the tree and start again, I removed DS from the server and then deleted all the objects in that OU. Left it overnight,
next day built the server again with the same name and in the same OU and got exactly the same problem.

Can anybody shed some light on this please.

All servers are Netware 6.5 SP1.
 
The TIDS never helped me on this on either. You shouldn't have to reinstall DS. What I have done in the past to fix this is the following..

Remove all ldap, pki, sas, and other security related objects from NDS (only for the bad server)... Delete the Tomcat, apache, and admsrv folders from SYS (Or rename them). Remove all product records in NWCONFIG that relate to above items.

Make sure that you go in DSBROWSE and that NO [deleted] objects still exist. Force the janitor process or wait overnight to get rid of everything. Make sure that all servers with replicas have no [deleted] objects.

Then go into the GUI and INSTALL, then browse to the root of the CD1 for the script file that is there. Load that up and clear everything. Then tick the first one on the list (apache/tomcat i believe). If there are any others relating to ldap or certificates, tick those too. You probably also want to tick iManager.

Then just step through it and it pretty much takes your server and reinstalls it, but the pieces needed (LDAP) to correctly load Tomcat are put down and configured correctly.

I spent a lot of time on this exact problem with several NW6.5 servers when it first came out and this process is the only way I could find to get past those errors. Note that I had very good luck doing this on NW6.5 (No SP), but am not sure about the SP1.


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 

Thanks Marvin, that worked a treat.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top