| 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 |
Hello,
A customer experienced a DSA core dump.
The EVENT file shows:
Event: Shadow Update Complete
from: Node LOCAL:.isa1 DSA
at : 1997-04-22-10:41:32.964+02:00I-----
Naming Context = "/C=BE/L=Isa"
Role = Supplier
Peer = "/C=be/O=isaserver/CN=dsa-isa2"
Agreement ID = "6"
Update Strategy = Incremental
EventUID 394564EE-BAEC-11D0-8E85-08002BE4ADCB
EntityUID D9749216-B17B-11D0-8E85-08002BE4ADCB
StreamUID D7CD81B6-B17B-11D0-8E85-08002BE4ADCB
Event: Shadow Update Complete
from: Node LOCAL:.isa1 DSA
at : 1997-04-22-10:47:04.867+02:00I-----
Naming Context = "/C=BE/L=Isa"
Role = Supplier
Peer = "/C=be/O=isaserver/CN=dsa-isa2"
Agreement ID = "6"
Update Strategy = Incremental
EventUID FF19B828-BAEC-11D0-8E85-08002BE4ADCB
EntityUID D9749216-B17B-11D0-8E85-08002BE4ADCB
StreamUID D7CD81B6-B17B-11D0-8E85-08002BE4ADCB
Event: Shadow Update Failure
from: Node LOCAL:.isa1 DSA
at : 1997-04-22-10:48:04.602+02:00I-----
Role = Supplier
Reason = DISP error received
Naming Context = "/C=BE/L=Isa"
Peer = "/C=be/O=isaserver/CN=dsa-isa2"
DispProblem = Unwilling To Perform
Agreement ID = "6"
EventUID 22B48F60-BAED-11D0-8E85-08002BE4ADCB
EntityUID D9749216-B17B-11D0-8E85-08002BE4ADCB
StreamUID D7CD81B6-B17B-11D0-8E85-08002BE4ADCB
Any idea on what happend??
Pierre
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 999.1 | a-107.tunnel.crl.dec.com::FORTY2::PALKA | Andrew Palka Altavista Directory | Thu Apr 24 1997 15:27 | 17 | |
You dont give us much information.
1) What X.500 version ?
2) What operating system (and version ?)
3) Is there anything in the dsa output log file
(/var/dxd/dsa_output.log or dxd$directory:dxd$dsa_startup.log)
On Unix the file is overwritten when the dsa is restarted.
4) Is the core file readable (by dbx or analyse/process) ?
'Unwilling to Perform' is not a common DISP error, and probably
indicates some kind of error in the DSA that sent it (possibly
resource problems). However this DSA received the error. Possibly
it encountered some bug while trying to recover from the error and
transmit a new update.
Andrew
| |||||
| 999.2 | The info's | BACHUS::CAPPELLEMANS | The Dark side of the \FORCE | Fri Apr 25 1997 15:18 | 13 |
Andrew, sorry about that, in my hurry I forgot to tell wich version and so on. They are running X.500 V3.0.23 on UNIX V3.2c And as they restarted the DSA, the /var/dxd/dsa_output.log is empty... If you want to take a look at the core dump, I've put it on BACHUS::ISA_DSA_CORE.DMP Best regards Pierre | |||||
| 999.3 | a-107.tunnel.crl.dec.com::FORTY2::PALKA | Andrew Palka Altavista Directory | Fri Apr 25 1997 15:56 | 9 | |
Core dumps on Unix V3 are generally not very useful, as the dumper program does not correctly save the registers of threads. You are running an old version of V3, so if there it is quite possible that the problem will be fixed by a newer version. If I get anything out of the dump I will let you know. Andrew | |||||
| 999.4 | BACHUS::CAPPELLEMANS | The Dark side of the \FORCE | Fri Apr 25 1997 17:10 | 7 | |
Andrew, I will keep tuned, and ask the customer to upgrade to the latest version. Many thanks Pierre | |||||