Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Highlighted
6566817 Absent Member.
Absent Member.
3864 views

iManager down

Out of the blue with no configuration changes I have a Netware 6.5 SP7 file server that will not allow me to access iManager. However, Remote Manager is working fine this morning. Apache is running but gives a 404 for iManager. Apache says:

Not Found

The requested URL /welcome/LoginPage was not found on this server.
Apache/2.0.59 (NETWARE) mod_jk/1.2.21 Server at Pincus.nahbrc.net Port 2200

Also, the Apache 2.0.59 for Netware console is not happy about LDAP. It keeps cycling through the following events:

1. Configured LDAP was found ready to use.
2. NIF Certhandler: Root certificate for master ldap not found, requesting a new one from server.
3. NIF Certhandler: # Root Certs=1.
4. NIF Certhandler: Retrieved certificate of size=1322
5. *MASTER[servername.DNSdomain][-1] ldap_simple_bind : Can't contact LDAP Server (81)
6. ldap *MASTER[servername.DNSdomain] down
7. LDAP initialization failed. Check LDAP and restart Apache.
8. LDAP initialization failed.

How I can still log in to Remote Manager with such complaints about LDAP is a mystery. However, Remote Manager reports a completely healthy machine, and otherwise this server is working great. I'm leaning toward reinstalling the iManager.

Any insight would be greatly appreciated! Thanks!

Brian Cook
Labels (2)
0 Likes
17 Replies
Knowledge Partner
Knowledge Partner

Re: iManager down

6566817,
> How I can still log in to Remote Manager with such complaints about
> LDAP is a mystery. However, Remote Manager reports a completely healthy
> machine, and otherwise this server is working great. I'm leaning toward
> reinstalling the iManager.
>

Can you try checking your certificates with PKIDIAG first?

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iManager down

6566817 wrote:

>
> Out of the blue with no configuration changes I have a Netware 6.5 SP7
> file server that will not allow me to access iManager. However, Remote
> Manager is working fine this morning. Apache is running but gives a
> 404 for iManager. Apache says:
>
> Not Found
>
> The requested URL /welcome/LoginPage was not found on this server.
> Apache/2.0.59 (NETWARE) mod_jk/1.2.21 Server at Pincus.nahbrc.net Port
> 2200
>
> Also, the Apache 2.0.59 for Netware console is not happy about LDAP.
> It keeps cycling through the following events:
>
> 1. Configured LDAP was found ready to use.
> 2. NIF Certhandler: Root certificate for master ldap not found,
> requesting a new one from server.
> 3. NIF Certhandler: # Root Certs=1.
> 4. NIF Certhandler: Retrieved certificate of size=1322
> 5. *MASTER[servername.DNSdomain][-1] ldap_simple_bind : Can't contact
> LDAP Server (81)
> 6. ldap *MASTER[servername.DNSdomain] down
> 7. LDAP initialization failed. Check LDAP and restart Apache.
> 8. LDAP initialization failed.
>
> How I can still log in to Remote Manager with such complaints about
> LDAP is a mystery. However, Remote Manager reports a completely
> healthy machine, and otherwise this server is working great. I'm
> leaning toward reinstalling the iManager.
>
> Any insight would be greatly appreciated! Thanks!


Sounds like tomcat has died because of an expired certificate. Run
pkidiag (hit option 4, then 0) and see if any certs are being fixed. If
so, then start tomcat and check iManager again.

remote manager and imanager are unrelated to eachother as remote
manager uses its own webserver.


--
Cheers,
Edward
0 Likes
6566817 Absent Member.
Absent Member.

Re: iManager down

>QUOTE=Edward van der Maas;1648403]6566817 wrote:
>
>Sounds like tomcat has died because of an expired certificate. Run
>pkidiag (hit option 4, then 0) and see if any certs are being fixed. If
>so, then start tomcat and check iManager again.

How can I get get a copy of PKDIAG? It's not on the server and apparently you can't download it from the support site.

Thanks! Brian
0 Likes
6566817 Absent Member.
Absent Member.

Re: iManager down

I found PKIDIAG. How do you restart tomcat? Thanks! Brian
0 Likes
Knowledge Partner
Knowledge Partner

Re: iManager down

6566817,
> I found PKIDIAG. How do you restart tomcat? Thanks! Brian
>

Java -show

Note the numbers

java -killxxx
java -killyyy (note no space between kill and the process id)

tomcat4
tcadmup

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iManager down

<g>, or rather more gracefully

tomcat4 stop (or tc4stop)
tcadmdn

Cheers Dave


--
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
6566817 Absent Member.
Absent Member.

Re: iManager down

>tomcat4
>tcadmup

Anders- This procedure seemed to work. But now my iManager link says this:

--------------------------------
Service unavailable!
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

If you think this is a server error, please contact the webmaster.

Error 503
10.5.0.184
Wednesday, October 1, 2008 12:23:34
Apache/2.0.59 (NETWARE) mod_jk/1.2.21
--------------------------------

Here's what java -show says now:

Class name ID
------------------------------------------------------------------
com.novell.application.tomcat.util.tccheck.LDAPVerifier 1265
com.novell.application.tomcat.util.tccheck.LDAPVerifier 1285

Total running: 2

Also, PKIDIAG reported that it found and fixed 2 problems. Another pass with PKIDIAG shows no problems.

Any ideas? Thanks a bunch!!!

Brian
0 Likes
Knowledge Partner
Knowledge Partner

Re: iManager down

Dave Parkes,
> <g>, or rather more gracefully
>

You do grace, I do brutal 😉

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
Knowledge Partner
Knowledge Partner

Re: iManager down

OK. When tomcat starts, you will probably see a number of LDAP error.
Try running tckeygen and restart tomcat

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
6566817 Absent Member.
Absent Member.

Re: iManager down

>OK. When tomcat starts, you will probably see a number of LDAP error.
>Try running tckeygen and restart tomcat

Hi Anders- Well tckeygen did SOMETHING! It apparently ran but all that happened at the console was I got another prompt.

It's pretty apparent that something happened because now when I use my iManager link instead of a 503 error I get a login prompt for Virtual Office (which of course fails to recognize my credentials). This is not really the outcome I was hoping for!

The Apache console is still complaining about LDAP. I have discovered another server that displays a 503 error when attempting to get into iManager, but I don't see the LDAP complaints in the Apache console on that box. It seems that both machines COULD have expired certificates as they are both +- 2 years or so old.

I'm down to one iManager machine and it's a bit disconcerting. Any ideas?

Thanks! Brian
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iManager down

Dave Parkes wrote:

> <g>, or rather more gracefully
>
> tomcat4 stop (or tc4stop)
> tcadmdn
>
> Cheers Dave


tomcat can't be running as he had issues with it......so no need to
stop it, its already stopped 🙂

--
Cheers,
Edward
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iManager down

6566817 wrote:


> The Apache console is still complaining about LDAP. I have discovered
> another server that displays a 503 error when attempting to get into
> iManager, but I don't see the LDAP complaints in the Apache console on
> that box. It seems that both machines COULD have expired certificates
> as they are both +- 2 years or so old.


type java -show and tell us what you see

> I'm down to one iManager machine and it's a bit disconcerting. Any
> ideas?


Still better then 0 😉



--
Cheers,
Edward
0 Likes
Knowledge Partner
Knowledge Partner

Re: iManager down

6566817,
> Hi Anders- Well tckeygen did SOMETHING! It apparently ran but all that
> happened at the console was I got another prompt.
>

I am at a conference today, so my coverage may be spotty, but there are
some tids in the knowledgebase that discuss tckeygen, java and ldap in
general.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iManager down

The thought crossed my mind - but it was Ander's homicidal tendencies that
I felt needed correcting anyway 🙂

Cheers Dave


--
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.