Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Error 672 dsrepair
- Thread starter keifer1
- Start date
how many servers do you have?
how far out is the timestamps?
how many partitions do you have ?
how many replicas of each do you have ?
is 672 on one specific server?
can you post the dsrepair log - cx server names if so desired
what ds version
how far out is the timestamps?
how many partitions do you have ?
how many replicas of each do you have ?
is 672 on one specific server?
can you post the dsrepair log - cx server names if so desired
what ds version
- Thread starter
- #3
marvhuffaker
MIS
Is the current time on the server correct right now? You say it says 2010??
Before you mess with ANYTHING in dsrepair to try to correct, you need to make sure your time is actually the time it is supposed to be.
Do a "TIME" at the console prompt.. What does it show? And does it say it's Synchronized or not synchronized? What are your time sources?
Make sure the time is correct and reporting synchronized, and then wait and see if you get any other errors like "Synthetic Time"..
I think some people in general overuse the "Repair Timestamps and declare new epoch" function. Honestly I've only used it 2-3 times in my career. If everything else is healthy, you shouldn't have to mess with it.
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
Before you mess with ANYTHING in dsrepair to try to correct, you need to make sure your time is actually the time it is supposed to be.
Do a "TIME" at the console prompt.. What does it show? And does it say it's Synchronized or not synchronized? What are your time sources?
Make sure the time is correct and reporting synchronized, and then wait and see if you get any other errors like "Synthetic Time"..
I think some people in general overuse the "Repair Timestamps and declare new epoch" function. Honestly I've only used it 2-3 times in my career. If everything else is healthy, you shouldn't have to mess with it.
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
solid advise
there arent many command in netware that scare me but this is one.
check time is really 2010 - if it is then you will need to declare an epoch with it that far ahead
reason i was asking how many is - declaring a new epoch will not work if you have more than 3 replicas of a partition
although i could be wrong but if the server was fast forwarded that far - you shouldnt actually get a ds error except obviously the synthetic time
has someone added or removed a server unsuccessfully to this tree to cause the 672?
one peace of advise i dont say this often - if the tree is clean and the server was definately 2010 and then changed back to current then my all means declare the epoch
IF AFTER this you have any errors - dont muddle with it spend the £200 or whatever it is and get novell to dial in
and do a dsrepair -rc first
there arent many command in netware that scare me but this is one.
check time is really 2010 - if it is then you will need to declare an epoch with it that far ahead
reason i was asking how many is - declaring a new epoch will not work if you have more than 3 replicas of a partition
although i could be wrong but if the server was fast forwarded that far - you shouldnt actually get a ds error except obviously the synthetic time
has someone added or removed a server unsuccessfully to this tree to cause the 672?
one peace of advise i dont say this often - if the tree is clean and the server was definately 2010 and then changed back to current then my all means declare the epoch
IF AFTER this you have any errors - dont muddle with it spend the £200 or whatever it is and get novell to dial in
and do a dsrepair -rc first
- Thread starter
- #6
Here is some further info.. Thankx in advance, I am showing 11 time stamp errors and think it is connected to a license error.
/****************************************************************************/
Netware 5.00 Directory Services Repair 5.26 , DS 7.51
Log file for server ".JIPSD1.Dept" in tree "JIPSD"
Display Replica Ring Information
Start: Tuesday, December 9, 2003 2:47:36 pm Local Time
/********** Partition Information and Servers in the Replica Ring **********Replica Name: T=JIPSD.
Replica id: 00000004
Replica rootEntryID: A50000C4
Replica replicaType: 00000000, Master
Replica state: 00000000, On
Replica flags: 00000000
Timestamp: 9-25-2010 10:52:04 pm; rep# = 0001; event = 058B
Replica Name: T=JIPSD.
Server Name: E90000C7, CN=JIPSD1.O=Dept.T=JIPSD. ** THIS SERVER
Server Class: NCP Server
Server Status: 00000002, UP
Server Flags: 00000001
Replica Record: Present
Replica Type: 0000, Master
Replica State: 0000, On
Replica Number: 00000001
RemoteID: A50000C4
referral-count: = 3
referral[0]-type = 00000009, (TCP)
referral[0]-size = 00000006
referral[0]-data[06] = 192.168.0.3:524
referral[1]-type = 00000000, (IPX)
referral[1]-size = 0000000C
referral[1]-data[12] = 0E 8A B0 CA 00 00 00 00 00 01 04 51
referral[2]-type = 00000008, (UDP)
referral[2]-size = 00000006
referral[2]-data[06] = 192.168.0.3:524
Timestamp: 9-25-2010 10:52:03 pm; rep# = 0001; event = E17D
*** END ***
/****************************************************************************/
Netware 5.00 Directory Services Repair 5.26 , DS 7.51
Log file for server ".JIPSD1.Dept" in tree "JIPSD"
Display Replica Ring Information
Start: Tuesday, December 9, 2003 2:47:36 pm Local Time
/********** Partition Information and Servers in the Replica Ring **********Replica Name: T=JIPSD.
Replica id: 00000004
Replica rootEntryID: A50000C4
Replica replicaType: 00000000, Master
Replica state: 00000000, On
Replica flags: 00000000
Timestamp: 9-25-2010 10:52:04 pm; rep# = 0001; event = 058B
Replica Name: T=JIPSD.
Server Name: E90000C7, CN=JIPSD1.O=Dept.T=JIPSD. ** THIS SERVER
Server Class: NCP Server
Server Status: 00000002, UP
Server Flags: 00000001
Replica Record: Present
Replica Type: 0000, Master
Replica State: 0000, On
Replica Number: 00000001
RemoteID: A50000C4
referral-count: = 3
referral[0]-type = 00000009, (TCP)
referral[0]-size = 00000006
referral[0]-data[06] = 192.168.0.3:524
referral[1]-type = 00000000, (IPX)
referral[1]-size = 0000000C
referral[1]-data[12] = 0E 8A B0 CA 00 00 00 00 00 01 04 51
referral[2]-type = 00000008, (UDP)
referral[2]-size = 00000006
referral[2]-data[06] = 192.168.0.3:524
Timestamp: 9-25-2010 10:52:03 pm; rep# = 0001; event = E17D
*** END ***
how confident are you ?
let me get my mind totally around this
you have one server - so assume it's just got a master partition with no childs
time went forward to 2010
time was corrected
server start saying synthetic time and declare epoch
you try this but you get a 672
if you're confident you can try some repairs
but if not and with only one server so no easy way to recover nds - my advise get a novell dial in
i think it's about $200
time is funny - i've seen this once and it took some serious novell time but this was in a large tree with lots of replicas and partitions and a nice day of 1st jan 2032
let me get my mind totally around this
you have one server - so assume it's just got a master partition with no childs
time went forward to 2010
time was corrected
server start saying synthetic time and declare epoch
you try this but you get a 672
if you're confident you can try some repairs
but if not and with only one server so no easy way to recover nds - my advise get a novell dial in
i think it's about $200
time is funny - i've seen this once and it took some serious novell time but this was in a large tree with lots of replicas and partitions and a nice day of 1st jan 2032
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question