[389-users] replication errors

2012-03-01 Thread Ellsworth, Josh
I am trying to set up replication between 2 389 servers. The master is running the following packages: 389-admin.x86_64 1.1.16-1.el5 installed 389-admin-console.noarch 1.1.7-1.el5 installed 389-admin-console-doc.noarc

Re: [389-users] managing 389 with a different admin server

2012-03-01 Thread Ellsworth, Josh
The solution was to run setup-ds-admin.pl -u. That changed all the settings for me. From: 389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Ellsworth, Josh Sent: Monday, February 27, 2012 11:52 AM To: General discussion list for the

Re: [389-users] managing 389 with a different admin server

2012-02-27 Thread Ellsworth, Josh
wiki page on this but I could not find it. So you use setup-ds-admin.pl for the first server and then for the second server you would use setup-ds.pl which you then use to register your instance against the existing admin db. Regards On 27 February 2012 16:39, Ellsworth, Josh wrote: We

[389-users] managing 389 with a different admin server

2012-02-27 Thread Ellsworth, Josh
We have two instances of 389 that were installed with the setup-ds-admin.pl script, and they both have unique admin servers. Is there a way to manage them both with the same admin server? If so, how is this accomplished. Thanks! Josh -- 389 users mailing list 389-us...@lists.fedoraproject.

Re: [389-users] console issues

2011-12-15 Thread Ellsworth, Josh
OK, I got it by installing a bunch of RPMs that put the .jar files in the right places. From: 389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Ellsworth, Josh Sent: Thursday, December 15, 2011 5:07 PM To: General discussion list for

Re: [389-users] console issues

2011-12-15 Thread Ellsworth, Josh
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) From: Ellsworth, Josh Sent: Thursday, December 15, 2011 3:34 PM To: 'Rich Megginson'; General discussion list for the 389 Directory server project. Sub

Re: [389-users] console issues

2011-12-15 Thread Ellsworth, Josh
: Ellsworth, Josh Subject: Re: [389-users] console issues On 12/15/2011 10:46 AM, Ellsworth, Josh wrote: I am working on deploying 389 in my organization but I'm having an issue with the Windows console. After I log in, the console looks like the screenshot here: http://imgur.com/W1hVd

[389-users] console issues

2011-12-15 Thread Ellsworth, Josh
I am working on deploying 389 in my organization but I'm having an issue with the Windows console. After I log in, the console looks like the screenshot here: http://imgur.com/W1hVd When I click on the Directory Server tree it changes to say "this server component has not yet been downloade

Re: [389-users] change IP of admin server

2011-12-06 Thread Ellsworth, Josh
-users] change IP of admin server 2011/12/6 Ellsworth, Josh What do I need to do to change the IP of the admin server? I brought up an instance from an image of a working 389 install and now I can't connect to the admin server I think that I missed something changing the IP. Is th

[389-users] change IP of admin server

2011-12-06 Thread Ellsworth, Josh
What do I need to do to change the IP of the admin server? I brought up an instance from an image of a working 389 install and now I can't connect to the admin server I think that I missed something changing the IP. Is there a special process that should be run? Josh -- 389 users mailing list

[389-users] migrating from openLDAP

2011-09-20 Thread Ellsworth, Josh
We are working on consolidating our diverse LDAP systems onto 389DS, but we are having some trouble with openLDAP. The designers of a particular software package are using a custom openLDAP schema and we aren't sure how to get it into 389. When we simply copy the .ldif file into the /schema folder

Re: [389-users] problem with admin client

2011-09-16 Thread Ellsworth, Josh
discussion list for the 389 Directory server project. Cc: Ellsworth, Josh Subject: Re: [389-users] problem with admin client On 09/14/2011 09:09 AM, Ellsworth, Josh wrote: A colleague set up 389DS and used the IP address as the hostname during the setup. I am having trouble connecting to the admin

Re: [389-users] slapd only listening on IPv6

2011-01-19 Thread Ellsworth, Josh
with ^z. Subsequent investigations led me to believe that the cause was nsslapd only listening on ipv6. From: Rich Megginson [mailto:rmegg...@redhat.com] Sent: Wednesday, January 19, 2011 1:52 PM To: Ellsworth, Josh Subject: Re: [389-users] slapd only listening on IPv6 On 01/19/2011 10:23 AM, Ellsworth,

[389-users] slapd only listening on IPv6

2011-01-19 Thread Ellsworth, Josh
I am working on a test 389DS instance and yesterday it started giving me trouble. The admin server would not start up correctly. I think that the problem is because slapd is not listening on IPv4. [root@ldaptest ~]# netstat -aunt Active Internet connections (servers and established) Proto Re