Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: iMonitor doesn't load

81 views
Skip to first unread message

a...@novell.com

unread,
Mar 13, 2009, 12:23:21 PM3/13/09
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Does it load manually when you try it?

Good luck.

kristow wrote:
> I just set up 4 servers, basically identical. On one of them iMonitor
> doesn't load and I can't figure out why. They are all SLES10SP2 with
> OES2SP1.
> imon is set to auto in ndsmodules.conf, but when I look at ndsd.log I
> see the line "We are in DHost" but there is not a line below it stating
> "NDS iMonitor for .... loaded successfully".
>
> Any ideas?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJJuohqAAoJEF+XTK08PnB5MOgQAIKMOrOhxjRnMYHXUFwsXjRj
ZpNH5GXjpWvkuOoSR4X58ovx5CqK4hss05gVj5WCbrigl6jVgMlPN/Jxxpk/dizR
2ypLCTvYAd9yeUBESbj6gMgh9tgPFQQj7IC4XD66WtWxgqzkXOLfDFv7NHT77DGo
HjC5JBrIbOmEnfw6fGZO7wbYKk28vhMgMCwEQEh2C3T++M/ShXSpErQ2fTZu+nMY
paHTPwhZU7jE9CXRZjc98pvpyVGNfVW/kpGw7PJGmWHB/V01hbw7uUk9YV2e5VYx
RJLs/A8qrogJ7RIDK951wSPo3jfH3CpsoUF5J3tlf/yOk8W1gOthnLE2IDwZUwLB
J3uYKO9Qon1JO3a9BLELFC7i9YMyaAWorNZ2LFEzXvFTF3ki24OH1PUCu45PWcJ2
Z1R5e1MXv62e4W/LMF3xsM9aTQoy/t/s0Fq8wmqvwAyf66p8B5lsZBUMLaLJs9lE
EGVbDvwlxticJyYFZLcve99gRv9mJdd4Tf3xgv7WTSNUFG4RxWd5UAqTge1kgcYS
tTOS035kjYAXGAeifLv/PK9yyRqXrfbsBr9Ub165MpYWoul/FpeCalgGnVjQieRt
2nmkR95oA8fIa4Sq9x7VcOE8wMKsr312JT1z5CL8wVhSkPoaeOtFh/93VPcr9Z/D
I43hLmmpviYUch6nNNR8
=e+vy
-----END PGP SIGNATURE-----

Jim Willeke

unread,
Jul 23, 2009, 9:21:42 AM7/23/09
to
I am having the same issue.
8.8.5 (32 bit)
SUSE Linux Enterprise Server 10 (i586)
VERSION = 10
PATCHLEVEL = 2


I believe that is it related to the certificate as I can only reach the
http: URLs and not the https URLs.

Any ideas on where to look?

Thanks
-jim

kristow wrote:
> I should clarify the above post. The menu screen appears, but anything
> on that screen that I click on, "DHost Console", "DS Trace", or "NDS
> iMonitor" all come back with "page cannot be displayed"
>
>

Jim Willeke

unread,
Jul 23, 2009, 9:28:30 AM7/23/09
to
Oh, we do have two NICs, but they both fail on the https: ports.

iMonitor works on our other server(s).
When we look at the server where iMonitor does not work we see:
07/23/09 09:00:43 AM 2:6 ... http://192.168.1.8:8389/portal
07/23/09 09:00:43 AM 2:7 ... http://192.168.1.9:8389/portal
07/23/09 09:00:43 AM 2:8 ... https://192.168.1.8:8636/portal
07/23/09 09:00:43 AM 2:9 ... https://192.168.1.9:8636/portal
07/23/09 09:00:43 AM 2:10 ... http://192.168.1.8:8389/nds
07/23/09 09:00:43 AM 2:11 ... http://192.168.1.9:8389/nds
07/23/09 09:00:43 AM 2:12 ... https://192.168.1.8:8636/nds
07/23/09 09:00:43 AM 2:13 ... https://192.168.1.9:8636/nds
07/23/09 09:00:43 AM 2:14 ... http://192.168.1.8:8389/soap
07/23/09 09:00:43 AM 2:15 ... http://192.168.1.9:8389/soap
07/23/09 09:00:43 AM 2:16 ... https://192.168.1.8:8636/soap
07/23/09 09:00:43 AM 2:17 ... https://192.168.1.9:8636/soap

Thanks
-jim

Jim Willeke

unread,
Jul 23, 2009, 10:24:11 AM7/23/09
to
We got it working.

Some things we looked at:
Check to see if modules are loaded:
ndstrace -c modules |grep imon
imon Running
httpstk Running [ nds hconserv imon embox ]

netstat -tanpu | grep 8636
tcp 0 0 192.168.1.9:8636 0.0.0.0:*
LISTEN 20541/ndsd
tcp 0 0 192.168.1.8:8636 0.0.0.0:*
LISTEN 20541/ndsd

So we know it is listening.
---
wget --no-check-certificate https://192.168.1.8:8636/nds
--09:58:24-- https://192.168.1.8:8636/nds
=> `nds'
Connecting to 192.168.1.8:8636... connected.
Unable to establish SSL connection.
Double check it is able to be connected to.
---
Check settings on http server
ndsconfig get |grep http
http.server.interfaces=192.168.1.8@8389,192.168.1.9@8389
http.server.sadmin-passwd=
http.server.module-base=/var/opt/novell/eDirectory/data/nds-http/
http.server.request-io-buffer-size=8192
http.server.request_timeout-seconds=300
http.server.keep-timeout-seconds=15
http.server.threads-per-processor=2
http.server.session-exp-seconds=900
http.server.trace-level=2
http.server.clear-port=8389
http.server.tls-port=8636
http.server.auth-req-tls=1
http.server.bind-restrictions=
https.server.interfaces=192.168.1.8@8636,192.168.1.9@8636
https.server.cached-cert-dn=DNS - sa.svr.willeke.com
https.server.cached-server-dn=

We changed the to the following line:
https.server.cached-cert-dn=IP AG 192\.168\.1\.8 - sa.svr.willeke.com

Unload imon
ndstrace -c "unload imon"

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:
sa.dc=svr.dc=willeke.dc=com.WILLEKETREE

Check to see if imon is running:
ndstrace -c modules |grep imon
imon Not Loaded

Load imon:
ndstrace -c "load imon"

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:
sa.dc=svr.dc=willeke.dc=com.WILLEKETREE

Check to see if imon is running:
ndstrace -c modules |grep imon
imon Running
httpstk Running [ nds hconserv embox imon ]

Access server now by either IP address of DNS name.
We do get a warning if we access the 192.168.1.9:8636 address:

"192.168.1.9:8636 uses an invalid security certificate.
The certificate is only valid for sa.willeke.com"

But we can live with that.
Thanks
-jim

0 new messages