This is with FDS 1.1 on CentOS 5 with Sun's java. I'm no longer able to open the "Manage certificates" task in the management console for my directory server. I get the following exception. This worked a couple of weeks ago when I fist set up the server, so I'm not sure what would have changed.
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.netscape.management.client.security.CertificateDialog.<init>(Unknown Source) at com.netscape.management.client.security.CertificateDialog.<init>(Unknown Source) at com.netscape.admin.dirserv.task.KeyCert.run(Unknown Source) at com.netscape.management.client.TaskModel.actionObjectRun(Unknown Source) at com.netscape.management.client.TaskPage$TaskList$ButtonMouseListener.mouseClicked(Unknown Source) at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:253) at java.awt.Component.processMouseEvent(Component.java:6041) at javax.swing.JComponent.processMouseEvent(JComponent.java:3265) at java.awt.Component.processEvent(Component.java:5803) at java.awt.Container.processEvent(Container.java:2058) at java.awt.Component.dispatchEventImpl(Component.java:4410) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3995) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916) at java.awt.Container.dispatchEventImpl(Container.java:2102) at java.awt.Window.dispatchEventImpl(Window.java:2429) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
I've put a copy of the -D 9 output here:
http://www.cora.nwra.com/~orion/fedora/console.log
Any help would be greatly appreciated.
Orion Poplawski wrote:
This is with FDS 1.1 on CentOS 5 with Sun's java. I'm no longer able to open the "Manage certificates" task in the management console for my directory server. I get the following exception. This worked a couple of weeks ago when I fist set up the server, so I'm not sure what would have changed.
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.netscape.management.client.security.CertificateDialog.<init>(Unknown Source) at com.netscape.management.client.security.CertificateDialog.<init>(Unknown Source) at com.netscape.admin.dirserv.task.KeyCert.run(Unknown Source) at com.netscape.management.client.TaskModel.actionObjectRun(Unknown Source) at com.netscape.management.client.TaskPage$TaskList$ButtonMouseListener.mouseClicked(Unknown Source) at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:253) at java.awt.Component.processMouseEvent(Component.java:6041) at javax.swing.JComponent.processMouseEvent(JComponent.java:3265) at java.awt.Component.processEvent(Component.java:5803) at java.awt.Container.processEvent(Container.java:2058) at java.awt.Component.dispatchEventImpl(Component.java:4410) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3995) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916) at java.awt.Container.dispatchEventImpl(Container.java:2102) at java.awt.Window.dispatchEventImpl(Window.java:2429) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
I've put a copy of the -D 9 output here:
http://www.cora.nwra.com/~orion/fedora/console.log
Any help would be greatly appreciated.
Looks like a problem on the admin server side - check your admin server access and error logs.
Looks like a problem on the admin server side - check your admin server access and error logs.
Looks like this is probably the issue:
[Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8
But I really don't know why it wouldn't be able to resolve.
# host 192.168.0.8 8.0.168.192.in-addr.arpa domain name pointer earth.cora.nwra.com.
orion@cora.nwra.com wrote:
Looks like a problem on the admin server side - check your admin server access and error logs.
Looks like this is probably the issue:
[Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8
But I really don't know why it wouldn't be able to resolve.
# host 192.168.0.8 8.0.168.192.in-addr.arpa domain name pointer earth.cora.nwra.com.
No, that's just a [notice] - that's benign. Anything else in the error log? In the access log, do you see 500 or 404 or 403 or other HTTP error status codes (i.e. anything other than 200)?
-- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
orion@cora.nwra.com wrote:
Looks like a problem on the admin server side - check your admin server access and error logs.
Looks like this is probably the issue:
[Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8
But I really don't know why it wouldn't be able to resolve.
# host 192.168.0.8 8.0.168.192.in-addr.arpa domain name pointer earth.cora.nwra.com.
No, that's just a [notice] - that's benign. Anything else in the error log? In the access log, do you see 500 or 404 or 403 or other HTTP error status codes (i.e. anything other than 200)?
Nothing other than 200's in access. The only messages in error from that time are:
[Fri Feb 22 15:32:08 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8 [Fri Feb 22 15:32:08 2008] [notice] [client 192.168.0.8] admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth handler [Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8 [Fri Feb 22 15:33:11 2008] [notice] [client 192.168.0.8] admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.0.8
Hi,
I have exactly the same issue - look at the bug 430499 ( https://bugzilla.redhat.com/show_bug.cgi?id=430499) to see all the debug logs of apache and of the console.
The bug appears each time you configure the administration server to use the secure connection to the Directory Server configuration server (the file adm.conf contains ldapurl: ldaps://ldap- model.polytechnique.fr:636/o=NetscapeRoot).
If you change the adm.conf (or use the console to do that) to ldapurl: ldap://ldap-model.polytechnique.fr:389/o=NetscapeRoot everything works fine again (no java exception, the certificate window opens correctly).
And the bug has nothing to do with java vendor - i have tested it for serveral versions, vendors and OS...
So i think that's what you have changed during the last couple of weeks :)
2008/2/23, Orion Poplawski orion@cora.nwra.com:
This is with FDS 1.1 on CentOS 5 with Sun's java. I'm no longer able to open the "Manage certificates" task in the management console for my directory server. I get the following exception. This worked a couple of weeks ago when I fist set up the server, so I'm not sure what would have changed.
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.netscape.management.client.security.CertificateDialog.<init>(Unknown Source) at com.netscape.management.client.security.CertificateDialog.<init>(Unknown Source) at com.netscape.admin.dirserv.task.KeyCert.run(Unknown Source) at com.netscape.management.client.TaskModel.actionObjectRun(Unknown Source) at
com.netscape.management.client.TaskPage$TaskList$ButtonMouseListener.mouseClicked (Unknown Source) at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:253) at java.awt.Component.processMouseEvent(Component.java:6041) ... -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
-- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
Andrey Ivanov wrote:
Hi,
I have exactly the same issue - look at the bug 430499 (https://bugzilla.redhat.com/show_bug.cgi?id=430499) to see all the debug logs of apache and of the console.
The bug appears each time you configure the administration server to use the secure connection to the Directory Server configuration server (the file adm.conf contains ldapurl: ldaps://ldap-model.polytechnique.fr:636/o=NetscapeRoot http://model.polytechnique.fr:636/o=NetscapeRoot).
If you change the adm.conf (or use the console to do that) to ldapurl: ldap://ldap-model.polytechnique.fr:389/o=NetscapeRoot http://model.polytechnique.fr:389/o=NetscapeRoot everything works fine again (no java exception, the certificate window opens correctly).
And the bug has nothing to do with java vendor - i have tested it for serveral versions, vendors and OS...
So i think that's what you have changed during the last couple of weeks :)
Yup, I had check "Use SSL in Console" under encryption in the directory server config. Unchecking it allows it to work again.
389-users@lists.fedoraproject.org