[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::x500

Title:X.500 Directory Services
Notice:Sprt: FORTY2::X500_SUPPORT, Kits: 216.*, try dir/titl=OFFICIAL
Moderator:FORTY2::PULLEN
Created:Tue Jan 30 1990
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1016
Total number of notes:4299

972.0. "decAltRFC822Mailbox Data Corruption in InfoBroker on a T3.1 system bound to the local DSA" by wookpc.ogo.dec.com::LEE () Thu Feb 13 1997 00:56

I have InfoBroker V2.1-2 installed on the T3.1/UNIX V4.0B system. When it tries
to read data from the T3.1 server, the values read for decAltRFC822Mailbox are
corrupted. None of the other attributes seem to be affected, but I haven't tried
many of them yet. This only seems to occur when ibxd running on the T3.1 system
is bound to the T3.1 DSA. Any other combination of components seems to work.
Here's what I've tried:

ibxd	DSA	Corruption

T3.1	T3.1	Yes
T3.1	V3.0-3	No
V3.0-3	T3.1	No
V3.0-3	V3.0-3	No

I suspect the problem lies with the patches that I applied to the V4.0B system.
The patches were meant for a V4.0A system, so I'm playing with fire here. Are
the patches even necessary on the V4.0B system?

Wook
T.RTitleUserPersonal
Name
DateLines
972.116.11.160.101::FORTY2::PALKAAndrew Palka Altavista DirectoryThu Feb 13 1997 12:3313
Patches are required for V4.0B as well as V4.0A. I dont know if the
same patches work properly.

The reason for the patch is to prevent a mutex deadlock, which hangs
the DSA. I dont know if there are other changes which can affect the
data, but it seems unlikely that anything would corrupt just one
attribute.

What kind of corruption happens ?
Can you see the corruption on a DSA or OSAK trace (I.e. do you think
it happens in the DSA or infobroker).

Andrew
972.2Turns out to be my problem for nowwookpc.ogo.dec.com::LEEThu Feb 13 1997 19:0411
In poking around a bit more, it looks like there's something wrong with the
custom ibxlookupd that I'm using. I'd forgotten that it was running rather than
the vanilla V2.1A-2 ibxlookupd.

The attribute value is missing or corrupted on the entry display page, but okay
on the brief (list) display page, so I guess that exonerates the DSA and ibxd.

I'll do some more testing with the vanilla ibxlookupd just to be sure it's not
something I introduced while extending the gateway.

Wook