Re: [389-users] Upgrading DS 389 via RPM
I was actually going to use yum update so I am not sure if that does that same as an rpm –U or if I need to re-run the install scripts. Chris Chris Taylor System Administrator Internet Eastlink chris.tay...@corp.eastlink.camailto:%20chris.tay...@corp.eastlink.caT: 519.773.1287 From: 389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Noriko Hosoi Sent: Monday, September 08, 2014 4:42 PM To: 389-users@lists.fedoraproject.org Subject: Re: [389-users] Upgrading DS 389 via RPM If you upgraded with rpm -U ..., it should have been taken care of. If you restart the server, what version string is logged in your /var/log/dirsrv/slapd-ID/errors? Thanks, --noriko Chris Taylor wrote: I am running DC 389 version 1.2.11.15 release 32.el6_5 and want to upgrade via RPM to 34.el6_5. After I run the RPM is there anything else I need to do? Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.orgmailto:389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] Stuck in read only mode
I am having an issue where I have two 389-ds servers stuck in read only mode. I am running version 1.2.11.15 in an MMR setup. I had created a new OU and imported a bunch of user accounts via ldif file which was successful. Then I went and tried to create a create a browsing index (via the GUI console). This eventually timed out and I had to manually close the window. I then went and did the same thing on my other server not thinking anything of it. I now see that both systems are stuck in read only mode. I can't seem to put them in write mode via the GUI and the only thing that I have in the error logs is the following. Backend instance: 'userRoot' is already in the middle of another task and cannot be disturbed. What are my next steps? Do I just restart slapd, go back in and turn off read only mode (if possible). Or is there a way to kill this hung-up index task. Any help would be appreciated. Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] Upgrading DS 389 via RPM
I am running DC 389 version 1.2.11.15 release 32.el6_5 and want to upgrade via RPM to 34.el6_5. After I run the RPM is there anything else I need to do? Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Errors after upgrade
I have seen this before you need to edit the entries to change the format your data is in. I had the same issue and was able to fix it by change the data format to the errored entries. Chris -Original Message- From: 389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Vesa Alho Sent: Friday, June 27, 2014 8:36 AM To: 389-users@lists.fedoraproject.org Subject: Re: [389-users] Errors after upgrade On 06/25/2014 04:51 PM, Ted Strother wrote: We upgraded from fedora-ds-base-1.1.3-2 to 389-ds-base-1.2.11.29-2 And are getting the following errors on startup, does anyone have any advice?: Looks like schema syntax has changed. You need to check schema files manually. -Vesa -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] Replication between different admin servers
I currently have two instances of LDAP setup the first is a set of CentOS-DS servers in an MMR setup running version Version: 8.2.8 Build Number: 2012.041.1227. I am trying to transition to an new setup that will be running Version:1.2.11.15 Build number:2014.072.1937. My question is that since these running different versions on different admin servers is it possible to setup replication between the two? Or would it just be best to do an export/import of the data and cut over to the new systems? Any guidance would be appreciated. Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] Custom schema in 389-ds version 1.1
I am just looking to replace my older 8.2 ds servers with the new 389-ds version 1.1, my only hang up is that I have some custom schema files used for RADIUS and FTP. I have read the docs and it looks like it's the same process, just have the custom ldif files located in the /etc/dirsrv/slapd-servername/schema is this correct or am I off base. Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Best way to upgrade DS servers
So if I follow this discussion correctly I should do the following steps. 1. Build my new server with OS and DS package 2. Edit the schema for my custom attributes 3. Setup a replication between my old server and the new server (as MMR) 4. Create a replication agreement between the two new servers (as MMR) 5. Remove the replication agreement between the old and new server 6. Run CLEANALLRUV to remove the old replication agreements Does this sound about right? Chris From: 389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Rich Megginson Sent: Wednesday, August 21, 2013 3:40 PM To: Michael Lang Cc: General discussion list for the 389 Directory server project. Subject: Re: [389-users] Best way to upgrade DS servers On 08/21/2013 01:36 PM, Michael Lang wrote: Am 21.08.2013 21:31, schrieb Rich Megginson: On 08/21/2013 01:03 PM, Michael Lang wrote: Am 21.08.2013 19:25, schrieb Chris Taylor: I am looking at replacing our two CentOS DS servers which are 5.9 with some on the 6.4 channel. What is the best way to transition all the data over? Should I build them separately and import everything via ldif files, or can I add them as consumers or in our setup as another master in our MMR setup. Chris, what I've been expirencing until now, unless you replace the DS with exactly the same machine (name, ...) Why? you should try an LDIF export first and use a VirtualMachine to import your content to see any possible problems (schema violations,...) Why not install the new servers on the new machines as replication masters and replicate the data to them? you would also need to remove the replication later on (not only in the GUI, the DS keeps a lot of logs and traces for every replication you setup) Yes, that's what CLEANALLRUV is for - http://port389.org/wiki/Howto:CLEANRUV beside, I would also consider the ACL's an other Database related settings which will not be exported by a LDIF dump and will only be copied if you can use the Backup functionality. ? for the consumer setup you would still need to extend the schema first if you customized it ... Yes. regards mIke To add a little complexity I have also added some RADIUS attributes to the schema so I am assuming that, those will need to be added before I setup any replication. Any advice would be great. Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.orgmailto:389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.orgmailto:389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] Best way to upgrade DS servers
I am looking at replacing our two CentOS DS servers which are 5.9 with some on the 6.4 channel. What is the best way to transition all the data over? Should I build them separately and import everything via ldif files, or can I add them as consumers or in our setup as another master in our MMR setup. To add a little complexity I have also added some RADIUS attributes to the schema so I am assuming that, those will need to be added before I setup any replication. Any advice would be great. Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] MMR not working after upgrade to 8.2
Hi I have two servers in an MMR setup I upgraded them from 8.1 to 8.2 as per the guide but now replication isn't working. I even went so far as to rebuild the agreements, but when I did that only the initial consumer initialize seemed to have worked but did generate this any updates after that failed with the errors below. [28/Feb/2013:10:40:41 -0400] - CentOS-Directory/8.2.8 B2012.041.1227 starting up [28/Feb/2013:10:40:41 -0400] - slapd started. Listening on All Interfaces port 389 for LDAP requests [28/Feb/2013:10:42:10 -0400] NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica dc=domain,dc=ca: 32 [28/Feb/2013:10:42:56 -0400] NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica dc=domain,dc=ca: 32 [28/Feb/2013:10:43:50 -0400] NSMMReplicationPlugin - agmt=cn=web-ldap02.eastlink.ca (web-ldap02:389): Unable to acquire replica: there is no replicated area dc=eastlink,dc=ca on the consumer server. Replication is aborting. [28/Feb/2013:10:43:50 -0400] NSMMReplicationPlugin - agmt=cn=web-ldap02.domain.ca (web-ldap02:389): Incremental update failed and requires administrator action [28/Feb/2013:10:46:03 -0400] NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica dc=domain,dc=ca: 32 [28/Feb/2013:10:48:42 -0400] NSMMReplicationPlugin - Beginning total update of replica agmt=cn=web-ldap02.domain.ca (web-ldap02:389). [28/Feb/2013:10:49:06 -0400] NSMMReplicationPlugin - Finished total update of replica agmt=cn=web-ldap02.domain.ca (web-ldap02:389). Sent 54794 entries. This was off the first master after I force an update NSMMReplicationPlugin - Replication agreement for agmt=cn=web-ldap02.domain.ca (web-ldap02:389) could not be updated. For replication to take place, please enable the suffix and restart the server I checked under the data container there is a check mark where it says enable this suffix. What should I be looking for? Why would I be able to do an initialize consumer and have it work then have later updates fail. Any help would be appreciated Thanks, Chris -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
