Home › Forums › OS X Server and Client Discussion › Open Directory › Creating Open Directory Replica behind gateway
- This topic has 1 reply, 1 voice, and was last updated 17 years, 9 months ago by
lucas_mat.
-
AuthorPosts
-
January 26, 2009 at 10:32 am #375223
lucas_mat
ParticipantI’m trying to re-organise our network config to an ODM with 4 ODR’s, one at each site. However, the ODM is out on the internet with a public IP address, and the potential replicas are behind the Gateway’s public IP on our private network.
I have tried to set the replica up, and it goes through the whole process, confirms it is now a replica, but when I go back into Open Directory in Server Manager it reports it is a Standalone. Likewise the master has no record of any replicas.
I heard that you needed to allow SSH traffic through the router, so set that up on a port-forward basis – port 22 TCP incoming pointing to the replica IP also on port 22 but to no avail. I also tried it on one of the other potential replicas with the same result. The only difference was that on one I couldn’t set up port forwarding (only having a limited number of port forward slots available and all of them used) so had to just open port 22 TCP. That one reported in the Open Directory error log:
2009-01-23 10:10:07 +0000 – ssh command failed with status 1
2009-01-23 10:10:07 +0000 – Removing replica due to an error copying LDAP database. (error = 69)
2009-01-23 10:10:07 +0000 – command: ssh root@85.113.82.31 /usr/sbin/slapconfig -removereplica 192.168.1.11 diradmin
2009-01-23 10:10:10 +0000 – command: ssh root@85.113.82.31 /usr/sbin/slapconfig -startldapserver
2009-01-23 11:05:15 +0000 – slapconfig -setmacosxodpol2009-01-23 11:05:15 +0000 – command: ssh root@85.112.82.31 /usr/sbin/slapconfig -checkmaster diradmin 0 4 4
2009-01-23 11:06:31 +0000 – ssh command failed with status 255
2009-01-23 11:06:31 +0000 – (error = 255)
2009-01-23 11:08:15 +0000 – slapconfig -createreplica
2009-01-23 11:08:15 +0000 – command: ssh root@85.113.82.31 /usr/sbin/slapconfig -checkmaster diradmin 0 4 4
2009-01-23 11:08:18 +0000 – Warning: An error occurred while disabling GSSAPI binding.
2009-01-23 11:08:18 +0000 – 1 Updating master’s configuration
2009-01-23 11:08:18 +0000 – command: ssh root@85.113.82.31 /usr/sbin/slapconfig -addreplica 192.168.1.11
2009-01-23 11:08:21 +0000 – 2 Stopping master LDAP server
2009-01-23 11:08:21 +0000 – command: ssh root@85.113.82.31 /usr/sbin/slapconfig -stopldapserver
2009-01-23 11:08:24 +0000 – command: ssh root@85.113.82.31 /usr/bin/db_recover -h /var/db/openldap/openldap-data ; /usr/sbin/slapcat -l /var/db/openldap/openldap-data/backup.ldif
2009-01-23 11:08:29 +0000 – ssh command output:
# no data for entry id=00000001The other (that I allowed port-forwarding on) didn’t log any OD errors at all, but still didn’t work.
I don’t really know what any of that means, lol. Anybody shed any light on it?
Thanks in advance.
January 26, 2009 at 3:07 pm #375231lucas_mat
ParticipantYes, I’ve done that – used local root to ssh into the Master and perform commands as root on that machine – all fine. Have just updated the local server to 10.5.6 to match the master. Going to give it another go. Also port-forwarded LDAP (389) on the router to the local server which I hadn’t done before.
Will test that now.
No, still no joy. Exactly the same, with no errors reported or anything.
-
AuthorPosts
- You must be logged in to reply to this topic.