Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
MarkHofland Absent Member.
Absent Member.
1835 views

ndsrepair -E gives a -603 remote error

Hi all,

We have three OES2 sp1 servers, SERVER_A Master, SERVER_B read/write SERVER_C read/write replica . If I do a ndsrepair -E on SERVER_A I get the following errors:

SERVER_A:~ # ndsrepair -E

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: EDREMIA01.O=SERVERS.REMIACV
Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20505.00
DS Version 20505.03 Tree name: TEST-TREE
Server name: .SERVER_A.SERVERS

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 675145 bytes.

Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
Please Wait...
Collecting replica synchronization status
Start: Thursday, September 26, 2013 10:22:02 Local Time
Retrieve replica status

Partition: .[Root].
Replica on server: .SERVER_B.SERVERS
Replica: .SERVER_B.SERVERS 09-26-2013 10:15:19
Replica on server: .SERVER_C.SERVERS
Replica: .SERVER_C.SERVERS 09-18-2013 10:52:51
Server: CN=SERVER_B.O=SERVERS 09-26-2013 10:20:30 -603 Remote
Object: O=SERVERS
Server: CN=SERVER_A.O=SERVERS 09-26-2013 10:21:19 -603 Remote
Object: O=SERVERS
Replica on server: .SERVER_A.SERVERS
Replica: .SERVER_A.SERVERS 09-26-2013 10:15:19
All servers synchronized up to time: 09-18-2013 10:52:51 Warning

Finish: Thursday, September 26, 2013 10:22:02 Local Time

Total errors: 2
NDSRepair process completed.

I get the same results on SERVER_B and SERVER_C
I can't find any documentation about a -603 error in this context. It has something to do with the SERVERS object, but I don't know what.

Any clues?

Regards,

Mark

PS I'm not available next week, so I can't respond on any questions
Labels (2)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: ndsrepair -E gives a -603 remote error

MarkHofland;2284501 wrote:
...
I get the same results on SERVER_B and SERVER_C
I can't find any documentation about a -603 error in this context. It has something to do with the SERVERS object, but I don't know what.

Any clues?

Regards,

Hi Mark,

Not sure, but the 603 error indicates some missing attribute. My first thought would be something is amiss with the sync with/to Server_C.
In any case, tread carefully (don't run any repair actions yet) and try to look if there is more info on what's stuck using iMonitor viewing the state reported on/of each server's replica.

Do you know of anything specific happening on (or around) 09-18-2013?

Just for more general "feel", I'm also curious to the output of "ndsrepair -T", "ndsrepair -N" & "ndsrepair -C -Ad -A" on each server.


-Willem
Highlighted
MarkHofland Absent Member.
Absent Member.

Re: ndsrepair -E gives a -603 remote error

Below the -T option, btw, SERVER_A, SERVER_B and SERVER_c are OES2 sp1 servers as mentioned before with replica's on it.

SERVER_D, SERVER_E and SERVER_F are new servers OES11 sp1 servers without any replica's.

SERVER_A:~ # ndsrepair -T

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: SERVER_A.O=SERVERS.TEST-TREE
Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20505.00
DS Version 20505.03 Tree name: TEST-TREE
Server name: .SERVER_A.SERVERS

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 677038 bytes.

Building server list
Please Wait...
Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
Please Wait...
Collecting time synchronization and server status
Time synchronization and server status information
Start: Thursday, September 26, 2013 12:45:52 Local Time

---------------------------+---------+---------+-----------+--------+-------
DS Replica Time Time is Time
Server name Version Depth Source in sync +/-
---------------------------+---------+---------+-----------+--------+-------
Processing server: .SERVER_D.SERVERS
.SERVER_D.SERVERS 20705.00 -1 Non-NetWare Yes 0
Processing server: .SERVER_E.SERVERS
.SERVER_E.SERVERS 20705.00 -1 Non-NetWare Yes 0
Processing server: .SERVER_F.SERVERS
.SERVER_F.SERVERS 20705.00 -1 Non-NetWare Yes 0
Processing server: .SERVER_B.SERVERS
.SERVER_B.SERVERS 20505.03 0 Non-NetWare Yes 0
Processing server: .SERVER_C.SERVERS
.SERVER_C.SERVERS 20505.03 0 Non-NetWare Yes 0
Processing server: .SERVER_A.SERVERS
.SERVER_A.SERVERS 20505.03 0 Non-NetWare Yes 0
---------------------------+---------+---------+-----------+--------+-------
Total errors: 0
NDSRepair process completed.

Below the -N option

SERVER_A:~ # ndsrepair -N

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: SERVER_A.O=SERVERS.TEST-TREE
Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20505.00
DS Version 20505.03 Tree name: TEST-TREE
Server name: .SERVER_A.SERVERS

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 679264 bytes.

This list shows each server found in the local database. Select a server to display an options menu.
Building server list
Please Wait...
Total number of servers found = 6


SERVER NAME LOCAL STATUS LOCAL ID
(1)SERVER_A.SERVERS Up 00008068
(2)SERVER_C.SERVERS Up 00008B40
(3)SERVER_B.SERVERS Up 00008D8B
(4)SERVER_F.SERVERS Up 0000954F
(5)SERVER_E.SERVERS Up 000094F2
(6)SERVER_D.SERVERS Up 0000943F


Below With the -C -Ad -A option running from the SERVER_A where the Master replica is hosted

SERVER_A:~ # ndsrepair -C -Ad -A

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: SERVER_A.O=SERVERS.TEST-TREE
Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20505.00
DS Version 20505.03 Tree name: TEST-TREE
Server name: .SERVER_A.SERVERS

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 679264 bytes.

Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
Please Wait...
External Reference Check
External Reference Check
Start: Thursday, September 26, 2013 13:45:31 Local Time

Checked 0 external references
Found: 0 total obituaries in this DIB,
0 Unprocessed obits, 0 Purgeable obits,
0 OK_To_Purge obits, 0 Notified obits
Total errors: 0
NDSRepair process completed.

Below With the -C -Ad -A option running from the SERVER_C where a Read/Write replica is hosted

SERVER_C:~ # ndsrepair -C -Ad -A

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: SERVER_C.O=SERVERS.TEST-TREE
Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20505.00
DS Version 20505.03 Tree name: REMIACV
Server name: .SERVER_C.SERVERS

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 655695 bytes.

Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
Please Wait...
External Reference Check
External Reference Check
Start: Thursday, September 26, 2013 14:12:27 Local Time

(1) Found obituary for: EID: 00008ba2, DN: CN=pcd231.CN=test_lan.O=SERVERS.T=TEST-TREE
Value CTS : 09-23-2013 08:50:17 R = 0006 E = 0001
Value MTS = 09-23-2013 08:50:17 R = 0006 E = 0001, Type = 0001 DEAD,
Flags = 0000


(2) Found obituary for: EID: 00008ba2, DN: CN=pcd231.CN=test_lan.O=SERVERS.T=TEST-TREE
Value CTS : 09-23-2013 08:50:17 R = 0006 E = 0002
Value MTS = 09-23-2013 08:50:17 R = 0006 E = 0002, Type = 0006 BACKLINK,
Flags = 0000

Backlink: Type = 00000001 DEAD, RemoteID = ffffffff,
ServerID = 000084d3, CN=SERVER_A.O=SERVERS.T=TEST-TREE

(3) Found obituary for: EID: 00008ba2, DN: CN=pcd231.CN=test_lan.O=SERVERS.T=TEST-TREE
Value CTS : 09-23-2013 08:50:17 R = 0006 E = 0003
Value MTS = 09-23-2013 08:50:17 R = 0006 E = 0003, Type = 0006 BACKLINK,
Flags = 0000

Backlink: Type = 00000001 DEAD, RemoteID = ffffffff,
ServerID = 000089f7, CN=SERVER_B.O=SERVERS.T=TEST-TREE

(4) Found obituary for: EID: 00008e69, DN: CN=Failover.CN=DHCP-Range.O=SERVERS.T=TEST-TREE
Value CTS : 09-23-2013 10:11:01 R = 0006 E = 0007
Value MTS = 09-23-2013 10:31:34 R = 0004 E = 0002, Type = 0001 DEAD,
Flags = 0004
PURGEABLE


(5) Found obituary for: EID: 00008e69, DN: CN=Failover.CN=DHCP-Range.O=SERVERS.T=TEST-TREE
Value CTS : 09-23-2013 10:11:01 R = 0006 E = 0008
Value MTS = 09-23-2013 10:11:01 R = 0006 E = 0008, Type = 0006 BACKLINK,
Flags = 0000

Backlink: Type = 00000001 DEAD, RemoteID = ffffffff,
ServerID = 000084d3, CN=SERVER_A.O=SERVERS.T=TEST-TREE

(6) Found obituary for: EID: 00008e6a, DN: CN=Failover.CN=DHCP-Range1.O=SERVERS.T=TEST-TREE
Value CTS : 09-23-2013 10:18:49 R = 0006 E = 0008
Value MTS = 09-23-2013 10:31:44 R = 0004 E = 0002, Type = 0001 DEAD,
Flags = 0004
PURGEABLE


(7) Found obituary for: EID: 00008e6a, DN: CN=Failover.CN=DHCP-Range1.O=SERVERS.T=TEST-TREE
Value CTS : 09-23-2013 10:18:49 R = 0006 E = 0009
Value MTS = 09-23-2013 10:18:49 R = 0006 E = 0009, Type = 0006 BACKLINK,
Flags = 0000

Backlink: Type = 00000001 DEAD, RemoteID = ffffffff,
ServerID = 000084d3, CN=SERVER_A.O=SERVERS.T=TEST-TREE

(8) Found obituary for: EID: 000091c4, DN: CN=1_6.O=SERVERS.T=TEST-TREE
Value CTS : 09-18-2013 11:51:07 R = 0006 E = 0006
Value MTS = 09-18-2013 11:51:07 R = 0006 E = 0006, Type = 0005 NEW_RDN,
Flags = 0000

RDN: CN=1_6

(9) Found obituary for: EID: 000091c4, DN: CN=1_6.O=SERVERS.T=TEST-TREE
Value CTS : 09-18-2013 11:51:07 R = 0006 E = 0007
Value MTS = 09-18-2013 11:51:07 R = 0006 E = 0007, Type = 0006 BACKLINK,
Flags = 0000

Backlink: Type = 00000005 NEW_RDN, RemoteID = ffffffff,
ServerID = 000084d3, CN=SERVER_A.O=SERVERS.T=TEST-TREE

(10) Found obituary for: EID: 000091c4, DN: CN=1_6.O=SERVERS.T=TEST-TREE
Value CTS : 09-18-2013 11:51:07 R = 0006 E = 0008
Value MTS = 09-18-2013 11:51:07 R = 0006 E = 0008, Type = 0006 BACKLINK,
Flags = 0000

Backlink: Type = 00000005 NEW_RDN, RemoteID = ffffffff,
ServerID = 000089f7, CN=SERVER_B.O=SERVERS.T=ETST-TREE

Checked 0 external references
Found: 10 total obituaries in this DIB,
8 Unprocessed obits, 2 Purgeable obits,
0 OK_To_Purge obits, 0 Notified obits
Total errors: 0
NDSRepair process completed.

Below With the -C -Ad -A option running from the SERVER_B where a Read/Write replica is hosted

SERVER_B:~ # ndsrepair -C -Ad -A

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: SERVER_B.O=SERVERS.TEST-TREE
Repair utility for Novell eDirectory 8.8 - 8.8 SP5 v20505.00
DS Version 20505.03 Tree name: TEST-TREE
Server name: .SERVER_B.SERVERS

Size of /var/opt/novell/eDirectory/log/ndsrepair.log = 369333 bytes.

Preparing Log File "/var/opt/novell/eDirectory/log/ndsrepair.log"
Please Wait...
External Reference Check
External Reference Check
Start: Thursday, September 26, 2013 14:49:57 Local Time

Checked 0 external references
Found: 0 total obituaries in this DIB,
0 Unprocessed obits, 0 Purgeable obits,
0 OK_To_Purge obits, 0 Notified obits
Total errors: 0
NDSRepair process completed.

It look like something is wrong with the SERVER_C replica. I can see, a lot of obutaries has to do with a deleted DHCP server on one of our OES11 servers (SERVER_B). We deleted this server because of some errors. The strange thing was, I deleted the most of the stuff in de Java Console and just stopped the rcnovell-dhpcd on that server. But on our main DHCP server I got still errors about the failover while it was deleted. But after starting iManager, the failover and some other stuff was still there! So I deleted them again and restarted our main DHCP server on SERVER_A, and the errors where gone.

Mark
0 Likes
Knowledge Partner
Knowledge Partner

Re: ndsrepair -E gives a -603 remote error

MarkHofland;2284548 wrote:
...It look like something is wrong with the SERVER_C replica. I can see, a lot of obutaries has to do with a deleted DHCP server on one of our OES11 servers (SERVER_B).


That explains the 1_X objects you where seeing....

MarkHofland;2284548 wrote:

We deleted this server because of some errors. The strange thing was, I deleted the most of the stuff in de Java Console and just stopped the rcnovell-dhpcd on that server. But on our main DHCP server I got still errors about the failover while it was deleted. But after starting iManager, the failover and some other stuff was still there! So I deleted them again and restarted our main DHCP server on SERVER_A, and the errors where gone.


A little tricky for me to say how you can best proceed with this. I do have a direction in mind and the trick is indeed to get the replica SERVER_C running correctly again, but it's safest to open an SR with Novell (if you have that option, with an active maintenance contract it should be free of charge) and have them take a closer look. Is that an option for you?

Cheers,
Willem
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.