[861] | 1 | To set up a new LDAP server: |
---|
| 2 | |
---|
[1680] | 3 | - Install the RPM 389-ds-base with yum (these are installed by kickstart |
---|
| 4 | these days, so these two steps are probably not necessary) |
---|
[1645] | 5 | root# yum install -y 389-ds-base |
---|
[1680] | 6 | root# yum install -y policycoreutils-python |
---|
| 7 | root# yum install -y ldapvi |
---|
[1645] | 8 | - We want to run the directory server as its own user, so create fedora-ds |
---|
[1680] | 9 | root# useradd -r -d /var/lib/dirsrv fedora-ds |
---|
[1677] | 10 | - Temporarily move away the existing slapd-scripts folder |
---|
| 11 | root# mv /etc/dirsrv/slapd-scripts{,.bak} |
---|
[861] | 12 | - root# /usr/sbin/setup-ds.pl |
---|
| 13 | - Choose a typical install |
---|
| 14 | - Tell it to use the fedora-ds user and group |
---|
| 15 | - Directory server identifier: scripts |
---|
[1645] | 16 | Needed to remove this from the config file first |
---|
[861] | 17 | - Suffix: dc=scripts,dc=mit,dc=edu |
---|
| 18 | - Input directory manager password |
---|
[1645] | 19 | (this can be found in ~/.ldapvirc) |
---|
[1677] | 20 | - Move the schema back |
---|
| 21 | root# cp -R /etc/dirsrv/slapd-scripts.bak/{.svn,*} /etc/dirsrv/slapd-scripts |
---|
| 22 | root# rm -Rf /etc/dirsrv/slapd-scripts.bak |
---|
[1680] | 23 | - Turn dirsrv off: service dirsrv stop |
---|
[1645] | 24 | - Apply the following configuration changes. If you're editing |
---|
| 25 | dse.ldif, you don't want dirsrv to be on, otherwise it will |
---|
| 26 | overwrite your changes. [XXX: show how to do these changes with |
---|
| 27 | dsconf, which is the "blessed" method] |
---|
| 28 | |
---|
| 29 | # Inside cn=config. These changes definitely require a restart. |
---|
[1818] | 30 | nsslapd-ldapifilepath: /var/run/slapd-scripts.socket |
---|
[1645] | 31 | nsslapd-ldapilisten: on |
---|
[1698] | 32 | nsslapd-syntaxcheck: off |
---|
[1645] | 33 | |
---|
| 34 | # Add these blocks |
---|
| 35 | |
---|
| 36 | # mapname, mapping, sasl, config |
---|
| 37 | # This is the most liberal mapping you can have for SASL: you can |
---|
| 38 | # basically add authentication for any given GSSAPI mechanism by |
---|
| 39 | # explicitly creating the UID for that SASL string. |
---|
| 40 | dn: cn=mapname,cn=mapping,cn=sasl,cn=config |
---|
| 41 | objectClass: top |
---|
| 42 | objectClass: nsSaslMapping |
---|
| 43 | cn: mapname |
---|
| 44 | nsSaslMapRegexString: \(.*\) |
---|
| 45 | nsSaslMapBaseDNTemplate: uid=\1,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 46 | nsSaslMapFilterTemplate: (objectClass=posixAccount) |
---|
| 47 | |
---|
| 48 | - Put LDAP keytab (ldap/hostname.mit.edu) in /etc/dirsrv/keytab. Make |
---|
| 49 | sure you chown/chgrp it to be readable by fedora-ds |
---|
| 50 | - Uncomment and modify in /etc/sysconfig/dirsrv: KRB5_KTNAME=/etc/dirsrv/keytab ; export KRB5_KTNAME |
---|
| 51 | - chown fedora-ds:fedora-ds /var/run/dirsrv |
---|
[1698] | 52 | - chown fedora-ds /etc/dirsrv/keytab |
---|
[1677] | 53 | - /sbin/service dirsrv start |
---|
| 54 | - Use ldapvi -b cn=config to add these indexes (8 of them): |
---|
[861] | 55 | |
---|
[880] | 56 | add cn=apacheServerName, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 57 | objectClass: top |
---|
| 58 | objectClass: nsIndex |
---|
| 59 | cn: apacheServerName |
---|
| 60 | nsSystemIndex: false |
---|
| 61 | nsIndexType: eq |
---|
| 62 | nsIndexType: pres |
---|
| 63 | |
---|
| 64 | add cn=apacheServerAlias, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 65 | objectClass: top |
---|
| 66 | objectClass: nsIndex |
---|
| 67 | cn: apacheServerAlias |
---|
| 68 | nsSystemIndex: false |
---|
| 69 | nsIndexType: eq |
---|
| 70 | nsIndexType: pres |
---|
| 71 | |
---|
[1473] | 72 | add cn=scriptsVhostName, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 73 | objectClass: top |
---|
| 74 | objectClass: nsIndex |
---|
| 75 | cn: scriptsVhostName |
---|
| 76 | nsSystemIndex: false |
---|
| 77 | nsIndexType: eq |
---|
| 78 | nsIndexType: pres |
---|
[880] | 79 | |
---|
[1473] | 80 | add cn=scriptsVhostAlias, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 81 | objectClass: top |
---|
| 82 | objectClass: nsIndex |
---|
| 83 | cn: scriptsVhostAlias |
---|
| 84 | nsSystemIndex: false |
---|
| 85 | nsIndexType: eq |
---|
| 86 | nsIndexType: pres |
---|
| 87 | |
---|
[1532] | 88 | add cn=scriptsVhostAccount, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 89 | objectClass: top |
---|
| 90 | objectClass: nsIndex |
---|
| 91 | cn: scriptsVhostAccount |
---|
| 92 | nsSystemIndex: false |
---|
| 93 | nsIndexType: eq |
---|
| 94 | nsIndexType: pres |
---|
| 95 | |
---|
[1473] | 96 | add cn=memberuid, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 97 | objectClass: top |
---|
| 98 | objectClass: nsIndex |
---|
| 99 | cn: memberuid |
---|
| 100 | nsSystemIndex: false |
---|
| 101 | nsIndexType: eq |
---|
| 102 | nsIndexType: pres |
---|
| 103 | |
---|
| 104 | add cn=uidnumber, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 105 | objectClass: top |
---|
| 106 | objectClass: nsIndex |
---|
| 107 | cn: uidnumber |
---|
| 108 | nsSystemIndex: false |
---|
| 109 | nsIndexType: eq |
---|
| 110 | nsIndexType: pres |
---|
| 111 | |
---|
| 112 | add cn=gidnumber, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=config |
---|
| 113 | objectClass: top |
---|
| 114 | objectClass: nsIndex |
---|
| 115 | cn: gidnumber |
---|
| 116 | nsSystemIndex: false |
---|
| 117 | nsIndexType: eq |
---|
| 118 | nsIndexType: pres |
---|
| 119 | |
---|
| 120 | - Build the indexes for all the fields: |
---|
| 121 | |
---|
| 122 | /usr/lib64/dirsrv/slapd-scripts/db2index.pl -D "cn=Directory Manager" -j /etc/signup-ldap-pw -n userRoot |
---|
| 123 | |
---|
[1645] | 124 | (/etc/signup-ldap-pw is the LDAP root password, make sure it's |
---|
| 125 | chmodded correctly and chowned to signup. Also, make sure it doesn't |
---|
| 126 | have a trailing newline!) |
---|
| 127 | |
---|
[1473] | 128 | - Watch for the indexing operations to finish with this command: |
---|
| 129 | |
---|
| 130 | ldapsearch -x -y /etc/signup-ldap-pw -D 'cn=Directory Manager' -b cn=tasks,cn=config |
---|
| 131 | |
---|
[1645] | 132 | (look for nktaskstatus) |
---|
| 133 | |
---|
| 134 | - Set up replication. |
---|
| 135 | |
---|
| 136 | We used to tell people to go execute |
---|
| 137 | http://directory.fedoraproject.org/sources/contrib/mmr.pl manually |
---|
| 138 | (manually because that script assumes only two masters and we have |
---|
| 139 | every one of our servers set up as a master.) However, those |
---|
| 140 | instructions are inaccurate, because we use GSSAPI, not SSL and |
---|
| 141 | because the initializing procedure is actually prone to a race |
---|
| 142 | condition. Here are some better instructions. |
---|
| 143 | |
---|
| 144 | LDAP replication is based around producers and consumers. Producers |
---|
| 145 | push changes in LDAP to consumers: these arrangements are called |
---|
| 146 | "replication agreements" and the producer will hold a |
---|
| 147 | nsDS5ReplicationAgreement object that represents this commitment, |
---|
| 148 | as well as some extra configuration to say who consumers will accept |
---|
| 149 | replication data from (a nsDS5Replica). |
---|
| 150 | |
---|
| 151 | The procedure, at a high level, is this: |
---|
| 152 | |
---|
| 153 | 1. Pick an arbitrary existing master. The current server will |
---|
| 154 | be configured as a slave to that master. Initialize a changelog, |
---|
| 155 | then request a replication to populate our server with |
---|
| 156 | information. |
---|
| 157 | |
---|
| 158 | M1 <---> M2 ---> S |
---|
| 159 | |
---|
| 160 | 2. Configure the new server to be replicated back. |
---|
| 161 | |
---|
| 162 | M1 <---> M2 <---> S |
---|
| 163 | |
---|
[1983] | 164 | 3. Set up the rest of the replication agreements. |
---|
[1645] | 165 | |
---|
| 166 | M1 <---> M2 |
---|
| 167 | ^ ^ |
---|
| 168 | | | |
---|
| 169 | +--> S <--+ |
---|
| 170 | |
---|
[1983] | 171 | 4. Push a change from every existing server (to the new server), and |
---|
| 172 | then a change from the new server to (all) the existing servers. |
---|
| 173 | In addition to merely testing that replication works, this will |
---|
| 174 | set up the servers' changelogs properly. |
---|
| 175 | |
---|
[1986] | 176 | If this step is not completed before any server's LDAP server |
---|
| 177 | shuts down, then the replication agreements will fall apart the |
---|
| 178 | next time a change is made. You may wish to intentionally reboot |
---|
| 179 | any servers that look like they want to crash _before_ beginning |
---|
| 180 | this process. |
---|
[1983] | 181 | |
---|
[1645] | 182 | Here's how you do it. |
---|
| 183 | |
---|
[1986] | 184 | 0. Tell -c scripts not to go off and reboot servers until you're |
---|
| 185 | done (or to get any rebooting done with first). |
---|
[1983] | 186 | |
---|
[1645] | 187 | 1. Pull open the replication part of the database. It's fairly empty |
---|
| 188 | right now. |
---|
| 189 | |
---|
[1680] | 190 | ldapvi -b cn=\"dc=scripts,dc=mit,dc=edu\",cn=mapping\ tree,cn=config |
---|
[1645] | 191 | |
---|
| 192 | 2. Configure the server $SLAVE (this server) to accept $MASTER |
---|
| 193 | replications by adding the following LDAP entries: |
---|
| 194 | |
---|
| 195 | add cn=replica, cn="dc=scripts,dc=mit,dc=edu", cn=mapping tree, cn=config |
---|
| 196 | objectClass: top |
---|
| 197 | objectClass: nsDS5Replica |
---|
| 198 | cn: replica |
---|
| 199 | nsDS5ReplicaId: $REPLICA_ID |
---|
| 200 | nsDS5ReplicaRoot: dc=scripts,dc=mit,dc=edu |
---|
| 201 | nsDS5Flags: 1 |
---|
| 202 | nsDS5ReplicaBindDN: uid=ldap/bees-knees.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 203 | nsDS5ReplicaBindDN: uid=ldap/busy-beaver.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 204 | nsDS5ReplicaBindDN: uid=ldap/cats-whiskers.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 205 | nsDS5ReplicaBindDN: uid=ldap/pancake-bunny.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 206 | nsDS5ReplicaBindDN: uid=ldap/whole-enchilada.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 207 | nsDS5ReplicaBindDN: uid=ldap/real-mccoy.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
[1677] | 208 | nsDS5ReplicaBindDN: uid=ldap/better-mousetrap.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 209 | nsDS5ReplicaBindDN: uid=ldap/old-faithful.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
[1698] | 210 | nsDS5ReplicaBindDN: uid=ldap/shining-armor.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
[1645] | 211 | nsds5ReplicaPurgeDelay: 604800 |
---|
| 212 | nsds5ReplicaLegacyConsumer: off |
---|
| 213 | nsDS5ReplicaType: 3 |
---|
| 214 | |
---|
| 215 | $REPLICA_ID is the scripts$N number (stella $HOSTNAME to find |
---|
| 216 | out.) You might wonder why we are binding to all servers; |
---|
| 217 | weren't we going to replicate from only one server? That is |
---|
| 218 | correct, however, simply binding won't mean we will receive |
---|
[1677] | 219 | updates; we have to setup the $MASTER to send data $SLAVE. |
---|
[1645] | 220 | |
---|
| 221 | 3. Although we allowed those uids to bind, that user information |
---|
| 222 | doesn't exist on $SLAVE yet. So you'll need to create the entry |
---|
| 223 | for just $MASTER. |
---|
| 224 | |
---|
| 225 | add uid=ldap/$MASTER,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 226 | uid: ldap/$MASTER |
---|
| 227 | objectClass: account |
---|
| 228 | objectClass: top |
---|
| 229 | |
---|
| 230 | 4. Though our $SLAVE will not be making changes to LDAP, we need to |
---|
| 231 | initialize the changelog because we intend to be able to do this |
---|
| 232 | later. |
---|
| 233 | |
---|
| 234 | add cn=changelog5,cn=config |
---|
| 235 | objectclass: top |
---|
| 236 | objectclass: extensibleObject |
---|
| 237 | cn: changelog5 |
---|
| 238 | nsslapd-changelogdir: /etc/dirsrv/slapd-scripts/changelogdb |
---|
| 239 | |
---|
| 240 | 5. Ok, now go to your $MASTER server that you picked (it should have |
---|
| 241 | been one of the hosts mentioned in nsDS5ReplicaBindDN) and tell |
---|
| 242 | it to replicate to $SLAVE. |
---|
| 243 | |
---|
[1680] | 244 | The last line runs the replication. This is perhaps the most |
---|
| 245 | risky step of the process; see below for help debugging problems. |
---|
| 246 | |
---|
[1677] | 247 | WARNING: There is a known bug doing full updates from 1.2.6 to |
---|
| 248 | 1.2.6, see https://bugzilla.redhat.com/show_bug.cgi?id=637852 |
---|
| 249 | |
---|
[1645] | 250 | add cn="GSSAPI Replication to $SLAVE", cn=replica, cn="dc=scripts,dc=mit,dc=edu", cn=mapping tree, cn=config |
---|
| 251 | objectClass: top |
---|
| 252 | objectClass: nsDS5ReplicationAgreement |
---|
| 253 | cn: "GSSAPI Replication to $SLAVE" |
---|
| 254 | cn: GSSAPI Replication to $SLAVE |
---|
| 255 | nsDS5ReplicaHost: $SLAVE |
---|
| 256 | nsDS5ReplicaRoot: dc=scripts,dc=mit,dc=edu |
---|
| 257 | nsDS5ReplicaPort: 389 |
---|
| 258 | nsDS5ReplicaTransportInfo: LDAP |
---|
[1680] | 259 | nsDS5ReplicaBindDN: uid=ldap/$MASTER,ou=People,dc=scripts,dc=mit,dc=edu |
---|
[1645] | 260 | nsDS5ReplicaBindMethod: SASL/GSSAPI |
---|
| 261 | nsDS5ReplicaUpdateSchedule: "0000-2359 0123456" |
---|
| 262 | nsDS5ReplicaTimeout: 120 |
---|
| 263 | nsDS5BeginReplicaRefresh: start |
---|
| 264 | |
---|
| 265 | 5. Check that the replication is running; the status will be stored |
---|
| 266 | in the object we've been mucking around with. |
---|
| 267 | |
---|
| 268 | If it fails with LDAP Error 49, check /var/log/dirsrv on $MASTER |
---|
| 269 | for more information. It might be because fedora-ds can't read |
---|
| 270 | /etc/dirsrv/keytab |
---|
| 271 | |
---|
| 272 | 6. Replicate in the other direction. On $MASTER, add $SLAVE |
---|
| 273 | as a nsDS5ReplicaBindDN in cn=replica,cn="dc=scripts,dc=mit,dc=edu",cn=mapping tree,cn=config |
---|
| 274 | Also, add an account for $SLAVE |
---|
| 275 | |
---|
| 276 | add uid=ldap/$SLAVE,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 277 | uid: ldap/$SLAVE |
---|
| 278 | objectClass: account |
---|
| 279 | objectClass: top |
---|
| 280 | |
---|
| 281 | On $SLAVE, |
---|
| 282 | |
---|
| 283 | add cn="GSSAPI Replication to $MASTER", cn=replica, cn="dc=scripts,dc=mit,dc=edu", cn=mapping tree, cn=config |
---|
| 284 | objectClass: top |
---|
| 285 | objectClass: nsDS5ReplicationAgreement |
---|
| 286 | cn: "GSSAPI Replication to $MASTER" |
---|
| 287 | cn: GSSAPI Replication to $MASTER |
---|
| 288 | nsDS5ReplicaHost: $MASTER |
---|
| 289 | nsDS5ReplicaRoot: dc=scripts,dc=mit,dc=edu |
---|
| 290 | nsDS5ReplicaPort: 389 |
---|
| 291 | nsDS5ReplicaTransportInfo: LDAP |
---|
| 292 | nsDS5ReplicaBindDN: uid=ldap/$SLAVE,ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 293 | nsDS5ReplicaBindMethod: SASL/GSSAPI |
---|
| 294 | nsDS5ReplicaUpdateSchedule: "0000-2359 0123456" |
---|
| 295 | nsDS5ReplicaTimeout: 120 |
---|
| 296 | |
---|
| 297 | If you get a really scary internal server error, that might mean you |
---|
| 298 | forgot to initialize the changelog. Remove the replication |
---|
| 299 | agreement (you'll need to turn off dirsrv), add the changelog, and |
---|
| 300 | then try again. |
---|
| 301 | |
---|
[1983] | 302 | 7. Repeat step 6 to complete the graph of replications (i.e., from |
---|
| 303 | every other server to the new server, and from the new server to |
---|
| 304 | every other server). |
---|
| 305 | |
---|
| 306 | Note the only difference between steps 5 and 6 is the lack of |
---|
| 307 | nsDS5ReplicaRefresh: start. That only needs to be done once, to the |
---|
| 308 | new server. |
---|
| 309 | |
---|
| 310 | 8. If at this point you look at the new server's changelog with |
---|
| 311 | cl-dump (preferably /mit/scripts/admin/cl-dump.pl, to not prompt you |
---|
| 312 | for a password), you won't see the servers you added in step 7. So, |
---|
| 313 | from each of those servers, make a change to some record so it gets |
---|
| 314 | propagated to the new server, and then one from the new server so it |
---|
| 315 | gets propagated to all the existing servers' changelogs. This is |
---|
| 316 | also good for making sure the replication agreements actually work. |
---|
| 317 | |
---|
[1672] | 318 | Troubleshooting |
---|
| 319 | =============== |
---|
| 320 | |
---|
[1677] | 321 | LDAP multimaster replication can fail in a number of colorful ways; |
---|
| 322 | combine that with GSSAPI authentication and it goes exponential. |
---|
| 323 | |
---|
| 324 | If authentication is failing with LDAP error 49, check if: |
---|
| 325 | |
---|
| 326 | * /etc/dirsrv/keytab |
---|
| 327 | * fedora-ds is able to read /etc/dirsrv/keytab |
---|
| 328 | * /etc/hosts has not been modified by Network Manager (you |
---|
| 329 | /did/ uninstall it, right? Right?) |
---|
| 330 | |
---|
[1672] | 331 | If the failure is local to a single master, usually you can recover |
---|
| 332 | by asking another master to refresh that master with: |
---|
| 333 | |
---|
| 334 | nsDS5BeginReplicaRefresh: start |
---|
| 335 | |
---|
| 336 | In practice, we've also had problems with this technique. Some of them |
---|
| 337 | include: |
---|
| 338 | |
---|
| 339 | * Something like https://bugzilla.redhat.com/show_bug.cgi?id=547503 |
---|
| 340 | on Fedora 11 ns-slapd, where replication is turned off to do the |
---|
| 341 | replication, but then it wedges and you need to forcibly kill the |
---|
| 342 | process. |
---|
| 343 | |
---|
| 344 | * Failed LDAP authentication because another master attempted to do |
---|
| 345 | an incremental update. |
---|
| 346 | |
---|
| 347 | * Repropagation of the error because the corrupt master thinks it still |
---|
| 348 | should push updates. |
---|
| 349 | |
---|
| 350 | So the extremely safe method to bring up a crashed master is as follows: |
---|
| 351 | |
---|
| 352 | 1. Disable all incoming and outgoing replication agreements by editing |
---|
| 353 | /etc/dirsrv/slapd-scripts/dse.ldif. You'll need to munge: |
---|
| 354 | |
---|
| 355 | nsDS5ReplicaBindDN in cn=replica,cn=dc\3Dscripts\2Cdc\3Dmit\2Cdc\3Dedu,cn=mapping tree,cn=config |
---|
| 356 | |
---|
| 357 | and all of the push agreements. Deleting them outright works, but |
---|
| 358 | means you'll have to reconstruct all of the agreements from scratch. |
---|
| 359 | |
---|
| 360 | 2. Bring up the server. |
---|
| 361 | |
---|
| 362 | 3. Accept incoming replication data from a single server. |
---|
| 363 | |
---|
| 364 | 4. Initiate a full update from that server. |
---|
| 365 | |
---|
| 366 | 5. Finish setting up replication as described above. |
---|
| 367 | |
---|
| 368 | If your database gets extremely fucked, other servers may not be able |
---|
| 369 | to authenticate because your authentication information has gone missing. |
---|
| 370 | In that case, the minimal set of entries you need is: |
---|
| 371 | |
---|
| 372 | add dc=scripts,dc=mit,dc=edu |
---|
| 373 | objectClass: top |
---|
| 374 | objectClass: domain |
---|
| 375 | dc: scripts |
---|
| 376 | |
---|
| 377 | add ou=People,dc=scripts,dc=mit,dc=edu |
---|
| 378 | objectClass: top |
---|
| 379 | objectClass: organizationalunit |
---|
| 380 | ou: People |
---|
| 381 | |
---|
[1677] | 382 | add uid=ldap/whole-enchilada.mit.edu,ou=People,dc=scripts,dc=mit,dc=edu |
---|
[1672] | 383 | objectClass: account |
---|
| 384 | objectClass: top |
---|
[1677] | 385 | uid: ldap/whole-enchilada.mit.edu |
---|