389-users June 2010

389-users@lists.fedoraproject.org

25 participants
24 discussions

Typo in 389-console source?
by Ryan Braun [ADS] 04 Jun '10

04 Jun '10

I'm just running my build scripts against the recently release updates, and think I caught a minor bug. in build.properties console.dotversion=1.1.4 where it should be console.dotversion=1.1.6 It builds fine, just the end jar filename is versioned 1.1.4 Ryan Braun Aviation and Defence Services Division Chief Information Officer Branch, Environment Canada CIV: 204-833-2500x2625 CSN: 257-2625 FAX: 204-833-2558 E-Mail: Ryan.Braun(a)ec.gc.ca

2 2

Re: [389-users] 389-console not working on Windows XP
by Rich Megginson 03 Jun '10

03 Jun '10

> I’m able to start 389-console on WinXP but cannot login; always fails > with the error below. any ideas? > C:\Program Files\389 Management Console>"C:\Program > Files\Java\jre6\bin\java" "-Djava.library.path=." -cp > "./jss4.jar;./ldapjdk.jar;./idm-console-base.jar;./idm-console-mcc.jar;./idm-console-mcc_en.jar;./idm-console-nmclf.jar;./idm-console-nmclf_en.jar;./389-console_en.jar" > -Djava.util.prefs.systemRoot=/.389-console > -Djava.util.prefs.userRoot=/.389-console > com.netscape.management.client.console.Console > *Exception in thread "main" java.lang.UnsatisfiedLinkError: C:\Program > Files\389 Management Console\jss4.dll: The specified procedure could > not be found* > at java.lang.ClassLoader$NativeLibrary.load(Native Method) > at java.lang.ClassLoader.loadLibrary0(Unknown Source) > at java.lang.ClassLoader.loadLibrary(Unknown Source) > at java.lang.Runtime.loadLibrary0(Unknown Source) > at java.lang.System.loadLibrary(Unknown Source) > at > org.mozilla.jss.CryptoManager.loadNativeLibraries(CryptoManager.java:1339) > at org.mozilla.jss.CryptoManager.initialize(CryptoManager.java:827) > at org.mozilla.jss.CryptoManager.initialize(CryptoManager.java:800) > at > com.netscape.management.client.util.UtilConsoleGlobals.initJSS(Unknown > Source) > at com.netscape.management.client.comm.HttpsChannel.<clinit>(Unknown > Source) > at > com.netscape.management.client.comm.HttpManager.createChannel(Unknown > Source) > at com.netscape.management.client.comm.CommManager.send(Unknown Source) > at com.netscape.management.client.comm.CommManager.send(Unknown Source) > at com.netscape.management.client.comm.HttpManager.get(Unknown Source) > at com.netscape.management.client.console.Console.invoke_task(Unknown > Source) > at > com.netscape.management.client.console.Console.authenticate_user(Unknown > Source) > at com.netscape.management.client.console.Console.<init>(Unknown Source) > at com.netscape.management.client.console.Console.main(Unknown Source) What files are in *C:\Program Files\389 Management Console ? dir "**C:\Program Files\389 Management Console"*

2 12

Re: [389-users] Multi Master Replication + SSL
by Rich Megginson 03 Jun '10

03 Jun '10

Stephen Agar wrote: > That was my thought as well, so what configuration(s) should I > check/change to ensure that it connects to port 636 as it's supposed to? http://www.redhat.com/docs/manuals/dir-server/8.1/admin/Managing_Replicatio… > > my urls for referrals are both: ldaps://other.server:636/dc=blah,dc=blah > > my replication agreements both have this: > supplier: this.server:636 > consumer: this.server:389 > > in the connection tab i have these selected: > - use tls/ssl (tls/ssl encryption with ldaps) > - simple authentication > > the documentation states that the consumer will always show port 389 > there..but why? Where does the documentation say that? I believe the documentation says that the supplier will always show 389, but the consumer should show the actual port it is connecting to. > > thanks, > stephen > > On Wed, Jun 2, 2010 at 3:59 PM, Rich Megginson <rmeggins(a)redhat.com > <mailto:rmeggins@redhat.com>> wrote: > > Stephen Agar wrote: > > I have 2 389 servers that I want to configure in a Multi > Master setup(I tried mmr.pl <http://mmr.pl> <http://mmr.pl>, > but had to make modifications to allow it to connect via > LDAPS, so thought that may be my issue, results below are from > scratch following the detailed howto from 389 and redhat). I > have port 389 totally disabled on my two servers. > > > I have configured them as such: > > - server A: SSL, Multi Master Replica, agreement serverb - > supplier=servera:636, consumer:servera:389 > - server B: SSL, Multi Master Replica, agreement servera - > supplier=serverb:636, consumer:serverb:389 > > My errors logs tell me: > [02/Jun/2010:11:51:23 -0500] slapi_ldap_bind - Error: could > not send bind reques > t for id [cn=repman,cn=config] mech [SIMPLE]: error 91 (Can't > connect to the LDA > P server) -5961 (TCP connection reset by peer.) 115 (Operation > now in progress) > > Doing a packet capture on the loopback interface, I see it > trying to connect to itself on port 389. So I try enabling > port 389 and get: > > [02/Jun/2010:13:00:42 -0500] slapi_ldap_bind - Error: could > not send bind request for id [cn=repman,cn=config] mech > [SIMPLE]: error 81 (Can't contact LDAP server) -5938 > (Encountered end of file.) 11 (Resource temporarily unavailable) > > Is the server trying to do starttls via port 389 instead of > LDAPS via port 636? I'm stuck and looking for any advice. > > Looks like it is attempting to use LDAPS to port 389. > > > Thanks! > > >

1 0

Announcing 389 Directory Server 1.2.6 Alpha 4
by Rich Megginson 02 Jun '10

02 Jun '10

The 389 team is pleased to announce the availability of Alpha 4 of version 1.2.6. This release contains a new replication session API, auto DN index upgrade, and several bug fixes. ***We need your help! Please help us test this software.*** It is an Alpha release, so it may have a few glitches, but it has been tested for regressions and for new feature bugs. The Fedora system strongly encourages packages to be in Testing until verified and pushed to Stable. If we don't get any feedback while the packages are in Testing, the packages will remain in limbo, or get pushed to Stable. The more testing we get, the faster we can release these packages to Stable. See the Release Notes for information about how to provide testing feedback (or just send an email to 389-users(a)lists.fedoraproject.org) The packages that need testing are: * 389-ds-base-1.2.6.a4 - 389-ds-base * 389-admin-1.1.11.a4 - 389-admin There are some new console/java packages too, and there is a new version of the 389-ds "meta" package - 1.2.1 * Release Notes - http://port389.org/wiki/Release_Notes * Install_Guide - http://port389.org/wiki/Install_Guide * Download - http://port389.org/wiki/Download === New features === * Replication Session Hooks - http://port389.org/wiki/Replication_Session_Hooks * Upgrade to new DN format - http://port389.org/wiki/Upgrade_to_New_DN_Format === Bugs Fixed === This release contains a couple of bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing. * Tracking bug for 1.2.6 release - https://bugzilla.redhat.com/showdependencytree.cgi?id=543590&hide_resolved=0

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users June 2010