Ian-M Super Contributor.
Super Contributor.
527 views

OBIT problem Backlink: Type = 00000005 NEW_RDN


Hi,
Due to circumstances beyond our control, we've had one of our servers
that was fire-walled off from all but one of our other servers for some
time and could only sync to that one server.
A large number of OBITs built up during that time and now that issue
has been resolved for about a week, I'm left with a number of obits on
some servers (there is a mixture of OES2SP2 & NW6.5SP8 servers).

The Master replica is free of OBITS, all servers are communicating &
time is in sync (ndsrepair -E & ndsrepair -T show no errors). The RW
replics have varying numbers of OBITs still on them which are all Type =
0001 DEAD, Type = 0006 BACKLINK and Type = 00000005 NEW_RDN.
Most of the OBITs seem to be SLP objects.

It's the Type = 00000005 NEW_RDN enrty that I'm not sure how to tackle.
Here's an example:

(1) Found obituary for: EID: 0000bd09, DN: CN=service
ksysguardd_kde:__hamfp01v_hamcoll_sa_edu_au:3112.SU=SLP-HAM.OU=SLP_SCOPE.O=Hamilton.T=ROOT

Value CTS : 07-20-2011 15:46:08 R = 0004 E = 0096
Value MTS = 07-21-2011 10:32:19 R = 0003 E = 0086, Type =
0006 BACKLINK,
Flags = 0001
NOTIFIED

Backlink: Type = 00000005 NEW_RDN, RemoteID = ffffffff,
ServerID = 0000940c, CN=HAMILTON.O=Hamilton.T=ROOT

(2) Found obituary for: EID: 0000bd09, DN: CN=service
ksysguardd_kde:__hamfp01v_hamcoll_sa_edu_au:3112.SU=SLP-HAM.OU=SLP_SCOPE.O=Hamilton.T=ROOT

Value CTS : 07-20-2011 15:46:08 R = 0004 E = 0098
Value MTS = 07-21-2011 10:32:19 R = 0003 E = 0087, Type =
0006 BACKLINK,
Flags = 0001
NOTIFIED

Backlink: Type = 00000005 NEW_RDN, RemoteID = ffffffff,
ServerID = 0000a4ac, CN=HAMIDM01V.O=Hamilton.T=ROOT

(3) Found obituary for: EID: 0000bd09, DN: CN=service
ksysguardd_kde:__hamfp01v_hamcoll_sa_edu_au:3112.SU=SLP-HAM.OU=SLP_SCOPE.O=Hamilton.T=ROOT

Value CTS : 07-20-2011 15:46:08 R = 0004 E = 0097
Value MTS = 07-21-2011 10:32:19 R = 0003 E = 0088, Type =
0006 BACKLINK,
Flags = 0001
NOTIFIED

Backlink: Type = 00000005 NEW_RDN, RemoteID = ffffffff,
ServerID = 00009407,
CN=ADMIN-SERVER.O=Hamilton.T=ROOT

(4) Found obituary for: EID: 0000bd09, DN: CN=service
ksysguardd_kde:__hamfp01v_hamcoll_sa_edu_au:3112.SU=SLP-HAM.OU=SLP_SCOPE.O=Hamilton.T=ROOT

Value CTS : 07-29-2011 00:18:33 R = 0001 E = 0001
Value MTS = 07-29-2011 00:18:58 R = 0004 E = 0003, Type =
0001 DEAD,
Flags = 0004
PURGEABLE

Should I try timestamping them in iMonitor?

Cheers,
Ian


--
imoore
------------------------------------------------------------------------
imoore's Profile: http://forums.novell.com/member.php?userid=932
View this thread: http://forums.novell.com/showthread.php?t=449356

Labels (1)
0 Likes
5 Replies
ataubman Absent Member.
Absent Member.

Re: OBIT problem Backlink: Type = 00000005 NEW_RDN


These obits will do no harm at all and can be safely ignored. What you
can try is ndsrepair -R -Ad -OT on each server, which will re-timestamp
the obits and they will then process if they can. Also people find that
promoting a RW with stuck obits to Master often helps.


--
Andrew C Taubman
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
------------------------------------------------------------------------
ataubman's Profile: http://forums.novell.com/member.php?userid=34
View this thread: http://forums.novell.com/showthread.php?t=449356


Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Ian-M Super Contributor.
Super Contributor.

Re: OBIT problem Backlink: Type = 00000005 NEW_RDN


Thanks, running ndsrepair with the -R -Ad -OT switch did the trick.

Cheers,
Ian


--
imoore
------------------------------------------------------------------------
imoore's Profile: http://forums.novell.com/member.php?userid=932
View this thread: http://forums.novell.com/showthread.php?t=449356

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OBIT problem Backlink: Type = 00000005 NEW_RDN


imoore;2159946 Wrote:
> Thanks, running ndsrepair with the -R -Ad -OT switch did the trick.
>
> Cheers,
> Ian


How different is this ndsrepair from running a epoch, I epoch is like
initializes timestamp for every object in the tree which can cause
outage.


--
gokulnathb
------------------------------------------------------------------------
gokulnathb's Profile: http://forums.novell.com/member.php?userid=33926
View this thread: http://forums.novell.com/showthread.php?t=449356

0 Likes
ataubman Absent Member.
Absent Member.

Re: OBIT problem Backlink: Type = 00000005 NEW_RDN


Very different indeed. NEVER declare a New Epoch unless you absolutely
have to (that is, you are getting Synthetic Time errors and the bogus
timestamps are a long way into the future). It's quite a risky
procedure.


--
Andrew C Taubman
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
------------------------------------------------------------------------
ataubman's Profile: http://forums.novell.com/member.php?userid=34
View this thread: http://forums.novell.com/showthread.php?t=449356


Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Knowledge Partner
Knowledge Partner

Re: OBIT problem Backlink: Type = 00000005 NEW_RDN

ataubman wrote:

>
> Very different indeed. NEVER declare a New Epoch unless you absolutely
> have to (that is, you are getting Synthetic Time errors and the bogus
> timestamps are a long way into the future). It's quite a risky
> procedure.


especially doing it in a large tree, better get a large pot of coffee
if you do that 🙂

--
Cheers,
Edward
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.