Home › Forums › OS X Server and Client Discussion › Questions and Answers › manually configured clone not syncing
- This topic has 1 reply, 2 voices, and was last updated 22 years, 9 months ago by
Anonymous.
-
AuthorPosts
-
September 23, 2003 at 1:25 am #356454
ad_agent
ParticipantNetinfo clone works in that it perfectly mirrors the master at moment of its creation. Also, after restart it seems to be synchronized.
However, it does not dynamically sync as changes are made to master. If there is a delay it is one of hours.
I understand this sort of problem requires close analysis. I am learning (I hope!) but could use some assistance.
Below I present output from nidump commands issued on all three levels of the Netinfo hierarchy in question. These nidumps were executed from Terminal prompt on machine “client1”.
(Some data is omitted. If I have omitted too much, please say.)
COMPANY (top level)
[localhost:~] local% sudo nidump -r / -t xxx.xxx.xxx.195/network
Password:
{
“master” = ( “company/network” );
“port” = ( “985” );
“promote_admins” = ( );
CHILDREN = (
{
“name” = ( “machines” );
CHILDREN = (
{
“name” = ( “company” );
“ip_address” = ( “xxx.xxx.xxx.195” );
“serves” = ( “./network”, “company/local” );
},
{
“ip_address” = ( “xxx.xxx.xxx.214” );
“name” = ( “department” );
“serves” = ( “department/network”, “department/local” );
}
)
},
)
}DEPARTMENT (middle level)
[localhost:~] local% sudo nidump -r / -t
department.salesupinc.com/network
Password:
{
“master” = ( “localhost/network” );
CHILDREN = (
{
“name” = ( “machines” );
CHILDREN = (
{
“name” = ( “department” );
“serves” = ( “department/local”, “./network” );
“ip_address” = ( “xxx.xxx.xxx.214” );
},
{
“ip_address” = ( “xxx.xxx.xxx.220” );
“name” = ( “client2” );
“serves” = ( “./network”, “client2/local” );
},
{
“ip_address” = ( “xxx.xxx.xxx.213” );
“name” = ( “client1” );
“serves” = ( “./network”, “client1/local” );
},
{
“ip_address” = ( “xxx.xxx.xxx.195” );
“name” = ( “company” );
“serves” = ( “../network” );
},
{
“ip_address” = ( “xxx.xxx.xxx.214” );
“name” = ( “localhost” );
“serves” = ( “department/local”, “./network” );
}
)
},
)
}CLONE
[localhost:~] local% sudo nidump -r / -t 127.0.0.1/network
Password:
{
“master” = ( “localhost/network” );
CHILDREN = (
{
“name” = ( “machines” );
CHILDREN = (
{
“name” = ( “department” );
“serves” = ( “department/local”, “./network” );
“ip_address” = ( “xxx.xxx.xxx.214” );
},
{
“ip_address” = ( “xxx.xxx.xxx.220” );
“name” = ( “client2” );
“serves” = ( “./network”, “client2/local” );
},
{
“ip_address” = ( “xxx.xxx.xxx.213” );
“name” = ( “client1” );
“serves” = ( “./network”, “client1/local” );
},
{
“ip_address” = ( “xxx.xxx.xxx.195” );
“name” = ( “company” );
“serves” = ( “../network” );
},
{
“ip_address” = ( “xxx.xxx.xxx.214” );
“name” = ( “localhost” );
“serves” = ( “department/local”, “./network” );
}
)
},
)
}CLIENT (bottom level)
[localhost:~] local% sudo nidump -r / -t 127.0.0.1/local
Password:
{
“master” = ( “localhost/local” );
“trusted_networks” = ( );
CHILDREN = (
{
“name” = ( “machines” );
CHILDREN = (
{
“ip_address” = ( “127.0.0.1” );
“name” = ( “localhost” );
“serves” = ( “./local” );
},
{
“name” = ( “broadcasthost” );
“ip_address” = ( “255.255.255.255” );
“serves” = ( “../network” );
},
{
“ip_address” = ( “xxx.xxx.xxx.213” );
“name” = ( “client1” );
“serves” = ( “./local”, “client1/network” );
}
)
},
{
“name” = ( “networks” );
CHILDREN = (
{
“name” = ( “loopback”, “loopback-net” );
“address” = ( “127” );
}
)
},
{
“name” = ( “MacOSXDupSuppress” );
CHILDREN = (
{
“name” = ( “1985731099;1985731099;1441689549;-1210511182” );
}
)
}
)
}NOTE:
Client2, being configured identically to client1 and having a clone of same master, is omitted here. There is one difference: client2 does not have a “MacOSXDupSuppress” subdirectory in its local domain.Both client’s clones have the exact same problem.
As for other relevant information, see below. Thanks again to anyone willing to review all this.
FURTHER DETAILS
Only the top level domain exists on a machine running Mac OS X Server. Client OS is running in all other cases.
DNS hostnames match machine names. “salesupinc.com” is a Search Domain specified in System Preferences on all machines.
OpenLDAP Distinguished Name suffixes are not present in any case. I’m using the default configuration file for slapd on all machines.
A “ps” shows that the network domains on clients are, indeed, clones. Again, though, synching seems to fail.
“Parent” links between domain windows in Netinfo Manager function as expected. Clients bind statically to Department.
Titles of Netinfo domain windows are as follows:
Company: network @ company.salesupinc.com – /
Department: network @ department.salesupinc.com – /department
Client1 (local domain): local @ 127.0.0.1 – /department/department
Client1 (network domain or clone): network @ department.salesupinc.com –
/departmentI have not exhausted my own ideas on this. For example, next I intend to simplify the hierarchy diagnostically.
Nevertheless, I would welcome any angle on this problem. Thanks in advance.
Graham Young
Art Dept Mgr
Sales Up, Inc.
McLean VA USAOctober 5, 2003 at 12:10 am #356529Anonymous
ParticipantStupid question im sure but when u say clone do u mean the whole contents of the server/client or only the info in netinfo? Im looking for a cloning procedure for contents cloning to two server..
Thx.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed