Re: Add R/W Replica from 8.7 to 8.8 give Error -603 and -608
a...@novell.com
Hash: SHA1
Is your schema synchronized? Depending on your familiarity with
eDirectory you may be more comfortable speaking with somebody on this but
you could cancel this add, clean up the partition's replica ring, then
force a schema sync from ndstrace:
sudo /opt/novell/eDirectory/bin/ndstrace
set dstrace=nodebug
dstrace +scma +scmd #as I recall from NetWare
set dstrace=*ss
Watch for All processed=yes or something similar... post the trace output
if nothing else.
That's a bit of an action for a given problem.... you could also verify
that is an issue using iMonitor to compare schema between replicas. You
could also watch the +sync and +sklk filters in ndstrace to see which
objects are throwing the -603 and -608 and that could be very helpful.
These should probably be tried first to see what the problem is before
trying to fix it.
Good luck.
reiss wrote:
> Hi,
>
> for implement a OES2SP2 Cluster i need a R/W Replica from my Partition
> on all OES2 Clusternodes.
>
> - My eDirectory Master is on a Netware 6.5 SP7 Server with DS Version
> 10553.73
> - My OES2SP2 Nodes have latest Patchlevel and DS Version 20501.00
>
> All Times are in Sync.
> Installation was fine and Schema was updated for at Installtime with
> Admin Right.
> In IManager i put a New R/W Replica to my first OES2SP2 Node with Name
> "lc01".
> Masterreplica stay on Netware Node with name "nc01"
>
> But now my Replication is not in Syc anymore.
> There are Error Codes -603 for OES2 Node and -608 on other older
> Netware Nodes.
>
> Here some Infos from my oes2 Node
>
> ##########################################################
>
> lc01:~ # ndsrepair -P
>
> [1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:
> lc01.O=TKH.TKH_01
> Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20501.00
> DS Version 20501.00 Tree name: TKH_01
> Server name: .lc01.TKH
>
> Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 91182 bytes.
>
> This list shows information for each replica stored on this server.
> Select a replica to display an options menu.
> Finding all replicas on this server
> Please Wait...
> Total number of replicas = 1
>
> PARTITION NAME REPLICA TYPE REPLICA
> STATE
> (1).[Root]. Read/Write New Replica
>
> Enter 'q' to escape the operation.
> Enter a replica number(1-1)?1
>
> REPLICA OPTIONS
> 1. Repair all replicas
> 2. Repair selected replica
> 3. Schedule immediate synchronization
> 4. Cancel partition operation
> 5. Designate this server as the new master replica
> 6. Report Synchronization status of all servers
> 7. Synchronize the replica on all servers
> 8. Repair Ring, all replicas
> 9. Repair Ring, selected replica
> 10. View Replica Ring
> 11. View entire partition name
> 12. Return to Replica List
>
>
> Enter 'q' to escape the operation.
> Enter a replica option(1-12)?10
> Finding all servers with replicas
> Please Wait...
> Replicas Of Partition: .[Root].
> Total number of servers in the replica ring = 4
> SERVER NAME REPLICA TYPE REPLICA STATE
> (1).NC01.TKH Master On
> (2).NC02.TKH Read/Write On
> (3).TKH-DISASTER.TKH Read/Write On
> (4).lc01.TKH Read/Write New Replica
> (5)Return to Replica Options
>
> Enter 'q' to escape the operation.
> Enter a server number(1-5)?q
> NDSRepair process completed.
> lc01:~ # ndsrepair -E
>
> [1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:
> lc01.O=TKH.TKH_01
> Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20501.00
> DS Version 20501.00 Tree name: TKH_01
> Server name: .lc01.TKH
>
> Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 91182 bytes.
>
> Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
> Please Wait...
> Collecting replica synchronization status
> Start: Thursday, November 26, 2009 10:21:54 Local Time
> Retrieve replica status
>
> Partition: .[Root].
> Replica on server: .lc01.TKH
> Replica: .lc01.TKH ********** ******** -603
> Replica on server: .TKH-DISASTER.TKH
> Replica: .TKH-DISASTER.TKH 11-26-2009 10:21:41
> Server: CN=lc01.O=TKH 11-26-2009 10:21:46 -608
> Remote
> Object: CN=NC01.O=TKH
> Replica on server: .NC02.TKH
> Replica: .NC02.TKH 11-26-2009 10:21:43
> Server: CN=lc01.O=TKH 11-26-2009 10:21:48 -608
> Remote
> Object: CN=NC01.O=TKH
> Replica on server: .NC01.TKH
> Replica: .NC01.TKH 11-26-2009 10:21:45
> Server: CN=lc01.O=TKH 11-26-2009 10:21:50 -608
> Remote
> Object: CN=NC01.O=TKH
>
> Finish: Thursday, November 26, 2009 10:21:54 Local Time
>
> Total errors: 3
> NDSRepair process completed.
>
> ################################################
>
> I run DSRepair.nlm on Netware node, but now it stuck with Screen
> "Waiting for Directory Service to release the local database file" and
> do nothing.
>
> Have anyone a Idea what i do wrong?
> Any Tipps to resolve this Issue?
>
> Thomas
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLDr7pAAoJEF+XTK08PnB5NoMP/1Jzk6azf27gWqgJQ4Z1yF/Y
PuXE+q9GpytGGnfqim24pqtLopN2FzuFhtK2FHJaVg+ERI08PU9pS94OYPUM/QEM
NPQ92Muu3/7KgZd2IEibM0+k4kEG9XXJveZ03uogNTRy1BOEVOR65oTekVi4Gahe
e59HrukcXV94taSD8DBZs83fMWle4tLoMDHvhnyQ3nFP+GzJLWtAWDdo2n7f3kLJ
FxZmSl32v3Rfa/93OR7QupX0o2XzfH4JaRuBxlALkBs1W77vf6S7daFS5hZ1grlc
lldC9SGwdPKgXOp+HlzzPyGZaxVVv42AoB2YGufU4mc3XBMapkNXZ1yr71z/65nI
FiAZ0zw1UTmg1ga4iBybKU2zGI7qlqmw4BmedhlfwvxI9baqMmmEiLc2LDavIOTd
I1VTjhZItmaYvomPd6AEadFClaEfnoPGRKTqDGxe2qpTb+S/B63UxjrFliDgDP2O
LVhr9h9Fs3vvD4qKvRq719zm6Zo/Ga0KyA0UI9ZEfDd8nQJqyAMZ75QPNIv4GcB0
T/uCWyC5y7RyEtWflo/Kpdxz8Mjq48I6xpOMVFELz5U+Us3Y3sUQkOJkm3AXw1Dl
EccAl8wFloAOpaRgPUTR57Py/vIhJXNay3FBP4hggs4x6f1scTKCoEBweJ4mBGXb
kzUgaXkdrwRfbhRH4XQu
=ChdE
-----END PGP SIGNATURE-----
Thomas Reiß
> Hmm, that's to heavy for me at the Moment.
>
> I opend a Call to Novell, they take a look at it and give you
> feedback.
>
> Thank you
> Thomas
>
>
Just for Info.
Remote Support does a havy Job with dsrepair Options, where i doesn't
understand 8-)
But everything is fine now.
Thanks for looking at this.
Thomas
a...@novell.com
Hash: SHA1
To follow up on this I heard a rumor of OES 2 SP2's schema extension tool
having an issue that can cause this and it seems to be specific to
clusters. I do not have details yet except for Bug# 559518 and TID# 7004947.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLGSxWAAoJEF+XTK08PnB5cKIQAMc4LVtXlPY//duUH3rgp1wQ
LrGex2YarG1MJFXDaIdHCWvnUQZB8RR9xqV2zCoZLmi9w6/Ncuy1wu0OCHrZ/j1b
DwYG9RpMw6IuVroqHgy1M1OVAvbolQGl5t1AOPVPop0uN0h6v/+sOJX47fj/Y16/
1e+zrZystsY7dGJi9KKiE5UteiLKN5zgge7cdiPIzydFLVI/BwBet6ehVB5Noy81
nFMBj7WfthyI0iMRH9YcFBB+wGb2O8OG4Y4hWwPzf1OmRR1FVwALtTDiN8Gg0JOJ
gvfKfm2AJcaboHk1siRu8SLkKY0h0dyK2mTCM7twImcrI0qji6QG0/zaEoOqExs7
dQuhyWokGDh5HFpToMZDv1DxUXCpeb1KuipcztTla7clA0jsNZ9X6RyslSLN/6Ju
9LUKVkBD+/HcMwFc2iPub45WWF2JqAQsacgzS2E8869QtMPvdW9nUQMT2Pfr3nKD
RTha+OT7A9oDmumDhx1X3Snf1vLSvsjR7LaswGdSrrqO12+CipXctwQihCfSJREq
vZ2U25BLErwI+0tkbnohtZDNaplbPc/upesgQ+I4wmW178pwbiYBbtj1fncQdN6K
cBr4C9y5gxqJPQagNPU4su3xyqAhnlAkZ2+kmKn8jlE/jV+gGJCCskmS8FeBe86G
kdSC4XAnvrSfgq/nBUkq
=tk5+
-----END PGP SIGNATURE-----
Thomas Reiß
Thx for Info.
Seems to be possible that this was my Problem.
But, yesterday i've got a Problem on one node Back.
When i login in Explicit on this Node, i got a Error with my Loginskript
(missing Searchpath on other Server).
This could be a Problem with the latest Patches from Patchchannel where
i have installed.
ndscheck tells me Time is in sync, replica's are all in State "UP" and
in sync.
But in iMonitor i see replica on this Node have lower "Subordinates"
than replicas on other Nodes and show some unknown Objects!
But before i run a unattend ndsrepair by myself on this Node, i ask
Novell again...
Thomas
a...@novell.com
Hash: SHA1
Do not, ever, run an unattended repair.
If you need to run a repair then run it with the options you know will
help fix the issue you are trying to repair. If you do not know the
options to use then ask here and we will do our best to help. Calling
Support is also an option.
Having objects look strange in a Subordinate-Reference replica sometimes
happens.... they are not "real" (full) replicas though so they are not
used for much except to keep a link from a parent partition to any child
partitions that are not otherwise on the same server as "real" replicas.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJLGooDAAoJEF+XTK08PnB51UwP+QGdj1/hujaI/vrLb3e2wbNP
fgotvE6/uGdmA5kv99V62VtLCjN9CpqfgtiWF/vAzOBon7Ip8zDSzZScNZnKIL9o
qVR9I97iLqkPKs0Zl0X6SlPdytBsQxaiqBp1SEgYIHF+nUVrL8eNwfeyuu1oBRqZ
Faeom42Zubgvhg2fcDL2NQ8TBb9ABY+Se3efldHfggX55CKnwcWCbYCcWimxcSji
PE79uDQofoHXk4aS+wWI4CCk2wpDZVC+i1psqOBntPVy8S75QswTjzTm1yY6D1jr
+aPkY1h++HSFcHtJjlXRMYOHGwqKzD97fxo/o5q57133IRMQg/77dbIXNdv17hSX
bfswVR5tTuV+WjsrXjjDhk0aODql7meeIBB8kGdKzoGwJqlfy6lmU6877kMQobor
Y1jEn8ple3dOrJ0o2GjjRpoxWmY2xbZLM10NegpJVRIGxqV70OgRp3zfH/SiRvF+
886xeLrWxns+VbNuNvgHSW8IVHeq3oZ26HLt8+lqFct+2Imb2g3luvMHAXo47+Aj
kKDfi/52agFynqArYfblSKP21j0XExCt8xGvtIS0PQ/5BYvYQMuWMRQbv61KZLia
eTymoTyWsYHl9qokG02THT4WY6jrv0CXTTLeWg2/1LsGGOs2kO4s5/snRQyqfewk
QJTz36T5zhJ1UIjAJuE7
=rnYD
-----END PGP SIGNATURE-----
a...@novell.com
Hash: SHA1
Some big changes are coming to help prevent future customers from seeing
this (Bug# 559518) in the future. Having been asked to reach out to
customers updating this thread seemed appropriate. For those going to OES
2 SP2 the documentation states to extend schema
(http://www.novell.com/documentation/oes2/clus_admin_lx/data/bfkqbhf.html).
For now do NOT do this, and if you do or already have, do NOT run a
repair. A TID will be released about this shortly besides other changes
to help prevent this.
Good luck.
iQIcBAEBAgAGBQJLIT+1AAoJEF+XTK08PnB5LbMQAMQKFJbLA4T1JYsMYZCCEA7o
D5vmQW/S0N/ZxKx19rMMrLSykp/G2Y87AlqeOTNvOvolYVdFk3F540o8cYNDYMgi
HXKCwDXXygjsAiJOGBWp16PJ0wjwoWvfZXgcKu0q96k6xAho0T8l0nIqco2YIXlj
FTsrFSldQrTNCbQx/Qlb0in4weJlZeHAIuPvCFLOTmH8utHKjUS77haHvJoku/Jy
hhK8wPOklQ2Klfdmxfp5llQRPX84cG9f5IdjHvVQHuLqXC6NPx7K9hujNHGzvGxh
GQ699zPeUxPEuk3G+kVHA1vu5gALa2rSuT4vmRy5lik6l1FQ8+VmwvfqN6QD6X5z
ofpNKR9LKlkNMJSDAdiGstDx4JUo2A+aoigndjWKmdVIFMQcev2U3ud20FoBlQa7
sS1uoEoDDeeu6nJVxi4Y+Z2wf9eMqqp9uXLUguekOa9eRg2apSe+ua4FvHjgXrBr
47sYPBpE1X1dKuQ2uCWmFtInXStsjgq0Sk9PQjeADz1+e+8+KxFfkUxZ8l1sb8ts
lgtNmOEsesB51o0rdpRUkxP6GZqpOS2Q2bsmJuv1EsY90E3v8k62nSFJ00a4iN25
GAFM3nkriU1X/0KIGOYl0qmHiW+Mde/dqdKDKSJBzQ2bRN1iA+H39605K4flUufO
Y5apI6kv1kDzSYCrKaB8
=omAN
-----END PGP SIGNATURE-----
Thomas Reiß
That was my Problem.
Novell Support found the Problem and repair it.
TID: 7004947
Thomas