[389-users] Re: Server Group empty in 389 Management Console for windows
Resolved. I’ve upgrade Java and now the client works. Not sure why the version of java nor 389 client was working for so long before it broke. Thanks all for your help. From: Jason Jenkins Date: Thursday, December 6, 2018 at 11:50 AM To: Viktor Ashirov , "389-users@lists.fedoraproject.org" <389-users@lists.fedoraproject.org> Subject: Re: [389-users] Re: Server Group empty in 389 Management Console for windows As far as I can tell, it has not. This is a host that is shared by our team only for use of the 389 Management Console. Linux shop, no windows in prod if at all possible. Nothing is supposed to be installed, removed, or changed on this host. At this point I’m going to try reinstall or upgrade java and see if that resolves my issue. I’ll update this thread with my resolution. From: Viktor Ashirov Date: Thursday, December 6, 2018 at 5:27 AM To: "389-users@lists.fedoraproject.org" <389-users@lists.fedoraproject.org>, Jason Jenkins Subject: Re: [389-users] Re: Server Group empty in 389 Management Console for windows Hi, On Thu, Dec 6, 2018 at 6:00 AM Jason Jenkins mailto:jjenk...@threatmetrix.com>> wrote: Exception in thread "AWT-EventQueue-0" java.lang.UnsupportedClassVersionError: c om/netscape/management/admserv/AdminServer : Unsupported major.minor version 51. 0 Was there any change (upgrade/downgrade) of JRE on a system where you're trying to run this? -- Viktor ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
[389-users] Re: Server Group empty in 389 Management Console for windows
As far as I can tell, it has not. This is a host that is shared by our team only for use of the 389 Management Console. Linux shop, no windows in prod if at all possible. Nothing is supposed to be installed, removed, or changed on this host. At this point I’m going to try reinstall or upgrade java and see if that resolves my issue. I’ll update this thread with my resolution. From: Viktor Ashirov Date: Thursday, December 6, 2018 at 5:27 AM To: "389-users@lists.fedoraproject.org" <389-users@lists.fedoraproject.org>, Jason Jenkins Subject: Re: [389-users] Re: Server Group empty in 389 Management Console for windows Hi, On Thu, Dec 6, 2018 at 6:00 AM Jason Jenkins mailto:jjenk...@threatmetrix.com>> wrote: Exception in thread "AWT-EventQueue-0" java.lang.UnsupportedClassVersionError: c om/netscape/management/admserv/AdminServer : Unsupported major.minor version 51. 0 Was there any change (upgrade/downgrade) of JRE on a system where you're trying to run this? -- Viktor ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
[389-users] Re: Server Group empty in 389 Management Console for windows
Hi, On Thu, Dec 6, 2018 at 6:00 AM Jason Jenkins wrote: > Exception in thread "AWT-EventQueue-0" > java.lang.UnsupportedClassVersionError: c > > om/netscape/management/admserv/AdminServer : Unsupported major.minor > version 51. > > 0 > Was there any change (upgrade/downgrade) of JRE on a system where you're trying to run this? -- Viktor ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
[389-users] Re: Server Group empty in 389 Management Console for windows
) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) From: Mark Reynolds Date: Wednesday, December 5, 2018 at 8:12 PM To: "General discussion list for the 389 Directory server project." <389-users@lists.fedoraproject.org>, Jason Jenkins Subject: Re: [389-users] Server Group empty in 389 Management Console for windows Hi Jason, Are you logging in as Directory Manager? If not, try that. Now it could be possible that part of the "o=netscaperoot" suffix has been deleted(accidentally?). That entire server group folder structure is o=netscaperoot, so the entries are either missing, or you don't have permissions to read them. Logging in as Directory Manger bypasses all access controls rules - so that's one way rule out access control. As for other console issues you can run it with debug logging to get more information about failures, etc: # 389-console -D 9 Also to register instances, you run "register-ds-admin.pl", not "setup-ds-admin.pl -u". HTH, Mark On 12/5/18 10:04 PM, Jason Jenkins wrote: Hi, I have 389 Management Console v1.1.6 installed on Windows and have been using it for some time without any problems. Today I logged in and found that after connecting to a host that there is nothing to be found under the Server Group folder. I navigate the tree for my host and what used to be “Administration Server” & “Dirsrv Hostname” are both gone from the Server Group folder. [cid:part2.7411DCF7.18E87C02@redhat.com] This is the same for any directory server host that I connect to. I’ve also reinstalled the version that I am using. And there is no difference. I tried installing a newer version of Management Console and it dies right after running what-ever it does in a command prompt. So I went back to v1.1.6. I verified that nothing changed on the network end. I can telnet to ports 389, 636 and 9830. I can hit 9830 from a web browser on this windows host. I ran “setup-ds-admin.pl -u” to re-register and nothing has changed. No errors or anything new in the logs from what I have seen prior. Once again this is across all of my directory server hosts that I was able to manage in the past. ___ 389-users mailing list -- 389-users@lists.fedoraproject.org<mailto:389-users@lists.fedoraproject.org> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org<mailto:389-users-le...@lists.fedoraproject.org> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
[389-users] Re: Server Group empty in 389 Management Console for windows
Hi Jason, Are you logging in as Directory Manager? If not, try that. Now it could be possible that part of the "o=netscaperoot" suffix has been deleted(accidentally?). That entire server group folder structure is o=netscaperoot, so the entries are either missing, or you don't have permissions to read them. Logging in as Directory Manger bypasses all access controls rules - so that's one way rule out access control. As for other console issues you can run it with debug logging to get more information about failures, etc: # 389-console -D 9 Also to register instances, you run "register-ds-admin.pl", not "setup-ds-admin.pl -u". HTH, Mark On 12/5/18 10:04 PM, Jason Jenkins wrote: Hi, I have 389 Management Console v1.1.6 installed on Windows and have been using it for some time without any problems. Today I logged in and found that after connecting to a host that there is nothing to be found under the Server Group folder. I navigate the tree for my host and what used to be “Administration Server” & “Dirsrv Hostname” are both gone from the Server Group folder. This is the same for any directory server host that I connect to. I’ve also reinstalled the version that I am using. And there is no difference. I tried installing a newer version of Management Console and it dies right after running what-ever it does in a command prompt. So I went back to v1.1.6. I verified that nothing changed on the network end. I can telnet to ports 389, 636 and 9830. I can hit 9830 from a web browser on this windows host. I ran “setup-ds-admin.pl -u” to re-register and nothing has changed. No errors or anything new in the logs from what I have seen prior. Once again this is across all of my directory server hosts that I was able to manage in the past. ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
