[389-users] Admin Server - Encryption Tab

Thu Feb 9 17:08:55 UTC 2012

From: Rich Megginson [mailto:rmeggins at redhat.com] 
Sent: 09 February 2012 18:04
To: MATON Brett
Cc: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] Admin Server - Encryption Tab

On 02/09/2012 10:01 AM, MATON Brett wrote: 

On 02/09/2012 08:45 AM, MATON Brett wrote: 

Platform RHEL6.2 x86_64 (EPEL repository enabled)

$ rpm -qa | grep 389

389-admin-console-doc-1.1.8-1.el6.noarch

389-ds-base-libs-1.2.9.14-1.el6_2.2.x86_64

389-admin-console-1.1.8-1.el6.noarch

389-adminutil-1.1.14-2.el6.x86_64

389-ds-console-1.2.6-1.el6.noarch

389-ds-1.2.2-1.el6.noarch

389-ds-base-1.2.9.14-1.el6_2.2.x86_64

389-ds-console-doc-1.2.6-1.el6.noarch

389-console-1.1.7-1.el6.noarch

389-admin-1.1.25-1.el6.x86_64

gpg-pubkey-b3892132-4c63febc

389-dsgw-1.1.7-2.el6.x86_64

I can only access the Encryption Tab of 389 Admin Server from the local
host.

When I try to access it from a remote desktop, it hangs for want of a
better description at "Loading" the progress bar in the bottom right
corner fills up and then starts over.

Nothing to note in the logs other than:

Blah admserv_host_ip_check: ap_get_remote_host could not resolve blah

Which is another thread...

This happens whether I'm using LDAPS to plain vanilla LDAP.

Any thoughts ?

you do seem to have the magic bug finger . . .  (I have my Moments J )

try 389-console -D 9 -f console.log 
to see if there is anything interesting in the console.log

hmm - try 
rm -rf ~/.389-console
to clear out the jar file cache
then run the console again

New output, attached complete log (Googlizing the NMC errors didn't
return much...):

Not sure why you are getting NoSuchMethodError
That seems like a mismatch between jar files

Try updating to the latest packages from epel-testing on both the client
and the server

server - yum update --enablerepo=epel-testing idm-console-framework
389-console 389-admin-console 389-ds-console 389-admin
client - yum update --enablerepo=epel-testing idm-console-framework
389-console
unless the client is also a server, in which case use the packages for
server

  I'll Update the server now and try it again, the client is running on
Windows 7 x64 (http://port389.org/download/389-Console-1.1.6-x86_64.msi)

Ah, ok.  The cache dir is different on Windows.  Not sure where it is -
I guess you could look for a .389-console folder somewhere under
\users\yourusername
Yeah, sits my users "home" as .389-console.

  (canned it as requested, before last log).

I only got a few new packages after enabling epel-testing:

# yum list | grep 389

389-admin.x86_64                     1.1.27-1.el6
@epel-testing

389-admin-console.noarch             1.1.8-1.el6               @epel

389-admin-console-doc.noarch         1.1.8-1.el6               @epel

389-adminutil.x86_64                 1.1.14-2.el6              @epel

389-console.noarch                   1.1.7-1.el6               @epel

389-ds.noarch                        1.2.2-1.el6               @epel

389-ds-base.x86_64                   1.2.9.14-1.el6_2.2        @Updates

389-ds-base-libs.x86_64              1.2.9.14-1.el6_2.2        @Updates

389-ds-console.noarch                1.2.6-1.el6               @epel

389-ds-console-doc.noarch            1.2.6-1.el6               @epel

389-dsgw.x86_64                      1.1.7-2.el6               @epel

389-admin.i686                       1.1.27-1.el6
epel-testing

389-adminutil.i686                   1.1.15-1.el6
epel-testing

389-adminutil.x86_64                 1.1.15-1.el6
epel-testing

389-adminutil-devel.i686             1.1.15-1.el6
epel-testing

389-adminutil-devel.x86_64           1.1.15-1.el6
epel-testing

389-ds-base-libs.i686                1.2.9.14-1.el6_2.2
rhel6-base-x86_64

389-dsgw.x86_64                      1.1.9-1.el6
epel-testing

You don't want to update the 389-ds-base* or 389-ds packages

Not sure why you are getting .i686 and .x86_64 packages
Any suggestions on how to replace the pair of updates packages?

  I'll drop the 686 packs and see if it breaks anything

Attached compressed log (previous attempt bounced).

Brett

-------------------------------------------------------------------