When an event occurs, the DSA sends a description of the event to the event sink. The events are described below.
1 – Accounting Disabled
This event is generated when the DSA disables the accounting facility. When the DSA disables the accounting facility, it closes the accounting file. The event contains the filename of the closed accounting file.
2 – Accounting Enabled
This event is generated when the DSA successfully enables the accounting facility. The event contains the filename of the accounting file.
3 – Accounting File Rollover
This event is generated when the DSA rolls over the accounting file, that is, closes the current accounting file and creates a new accounting file. The event contains the following information: - The filename of the closed accounting file. - The filename of the new accounting file.
4 – Accounting File Access Failure
The event contains the following information:
- What type of access the DSA was trying to make to the accounting
file. This can be one of WRITE, OPEN, or CLOSE access.
- A system message that indicates why the DSA failed to access the
accounting file. The system messages are described in the
documentation for your operating system.
- The filename of the accounting file that the DSA failed to open.
5 – Accounting Records Discarded
This event is generated when the DSA is forced to discard records without writing them in the accounting file. The reasons why the DSA may be forced to discard accounting files are described in HP Enterprise Directory - Problem Solving. The event indicates the number of records discarded since the last record was successfully written in the accounting file.
6 – Authentication Failure
This event is generated when the DSA fails to authenticate the
originator of a Bind request. The event returns the following
information:
- The reason why authentication failed. This may be one
of the following:
- Unknown User.
The distinguished name supplied in the Bind request does not
identify an entry within the directory.
- Incorrect Password.
The password supplied in the Bind request does not match the
password stored in the directory entry identified by the
supplied distinguished name.
- Inaccessible Password.
The DSA could not verify the supplied password because the
DSA containing the directory entry is not accessible. This
might be a temporary problem, for example, the connection to
that DSA cannot be made, or it might be a more permanent
problem, where the DSA holding the directory entry is not
a trusted DSA.
- Password Verification Loop.
When a DSA attempts to verify a password, it might need to
communicate with another DSA to access the directory entry
that contains the password. This communication might also
require the specification of a password, which must be
verified by the second DSA. It is therefore possible that
two DSAs will find themselves in a situation where each is
waiting for the other to verify a password. If this happens,
one of the DSAs detects the problem, and the authentication
fails.
- Information on the application or user that requested the
operation. This comprises:
- The application entity title of the DSA from which the Bind
request was received.
- The presentation address of the DSA from which the Bind
request was received.
- The distinguished name that was supplied in the Bind request,
if any.
- The directory protocol in use, that is DAP, DSP, DISP, or DOP.
The DAP protocol is used by directory applications to bind to the DSA.
The DSP protocol is used by other DSAs to chain requests to the DSA.
The DOP protocol is used by other DSAs to manage shadowing agreements.
The DISP protocol is used by other DSAs to replicate information to
or from this DSA.
7 – Create Failure
This event is generated when the DSA fails to create the DSA entity
in response to the CREATE DSA directive. The event provides the
following information:
- The reason why the DSA entity could not be created. This is
one of the following:
- Database already in use by another DSA.
The DSA is trying to connect to a database that is being
used by another DSA.
- DIT Incompatible.
The DSA database is incompatible with this version
of the DSA. This can only occur after an upgrade of the
DSA software.
- DIT Corrupt.
The DSA database is corrupt.
- DIT and Schema Incompatible
The DIT contains information that is not defined in the
schema. Fix your schema files, recompile them, and restart
the DSA.
- Schema Incompatible.
The directory schema is incompatible with this version of
the DSA. Both the schema compiler and the DSA contain
internal revision numbers that define the revision level
of the software. The most likely cause of this event
message is that an old version of the schema compiler has
been used to compile the schema files. This can only happen
after an upgrade of the DSA software.
- Schema Corrupt.
The directory schema is corrupt. Recompile the schema.
- License Check Failure.
The license check for the product has failed.
- System Error.
An unexpected system error has occurred.
- Additional information that assists in diagnosing the reason
for the failure. For example, if the reason is set to System
Error, the diagnostic string might provide the actual reason,
such as insufficient memory.
8 – Distributed Operation Failure
A Distributed Operation Failure event is issued when the DSA
cannot connect to another DSA.
The event returns the following information:
- Reason.
This is one of the following:
- Communications Failure.
The DSA could not establish an association for one of the
following reasons stated in the event:
- Fatal Interface Error
- Insufficient Resources
- Network Unavailable
- Address Already In Use
- Invalid AEI
- Transport Error
- System Error
- Invalid Transport Template
- Unknown Error
- DSA Not Trusted
The target DSA does not trust this DSA, and considers that
the connection requires trust.
- Authentication Failure.
The target DSA could not verify this DSA's password.
Refer to HP Enterprise Directory - Problem Solving.
- Invalid Reference.
The target DSA does not hold the part of the DIT that this
DSA expects it to. The knowledge information of this DSA is wrong.
See HP Enterprise Directory - Problem Solving.
- Remote Operation Rejected.
The target DSA has rejected the remote operation. This is
normally due to a protocol error.
- Diagnostic.
This may be, for example, an internal system error code.
- Target DSA.
The access point of the target DSA with which this DSA was
attempting to communicate when the failure occurred.
- Requestor.
Information on the application or user that requested the
operation. This comprises:
- The application entity title of the DSA from which the Bind
request was received.
- The presentation address of the DSA from which the Bind
request was received.
- The distinguished name that was supplied in the Bind request,
if any.
- The directory protocol in use, that is, DAP, DSP or the DEC
Shadow Protocol.
9 – Failure To Start Accounting Facility
The event indicates the reason why the DSA failed to start
the accounting facility. The reason can be either of the following:
- There was insufficient disk space for the accounting facility.
In this case, you need to release extra disk space on the
disk that the accounting facility uses, and then start the
accounting facility. Moving or deleting accounting files
might be the simplest solution.
HP recommends that you store accounting files on a
different disk to the DSA files, as follows:
- On Tru64 UNIX systems, create a softlink in the /var/dxd
directory so that the /var/dxd/accounting directory is on
a different disk.
- On OpenVMS systems, define the logical DXD$ACCOUNTING to
point to a directory on a different disk to the one that
contains DXD$DIRECTORY.
- The DSA failed to create an accounting thread.
Restart the accounting facility. If this problem happens
frequently, report it to HP.
10 – Internal Error
An Internal Error event is generated when the DSA detects an internal error. Report this error to HP. Each occurrence of this event results in the Internal Errors counter being incremented by 1.
11 – Listen Failure
This event is generated when the DSA fails to set up its own
presentation address for receiving communications. The event
provides a diagnostic message, and one of the following reasons:
- Fatal Interface Error
- Insufficient Resources
- Network Unavailable
- Address Already In Use
- Invalid AEI
- Transport Error
- System Error
- Invalid Transport Template
- Unknown Error
12 – Resource Exhausted
A Resource Exhausted event is generated when the DSA detects that
a critical resource is exhausted, preventing it from performing an
operation.
Each occurrence of this event results in the Exhausted Resource
counter being incremented by 1.
The event identifies the resource which is exhausted. This is one
of the following:
- Insufficient Memory.
Insufficient memory remains to process the operation.
- Fatal Memory Exhaustion
The DSA has run out of memory during an essential operation.
The DSA exits to avoid corrupting the database. The event
indicates how many bytes of memory were not available.
You should take steps to increase the amount of memory
available to the DSA.
- Insufficient License Capacity.
The DSA contains more entries than its licenses permit.
Reduce the DSA's entry count, or load more licenses.
- Insufficient Associations.
Insufficient resources are available to process a BIND operation.
- Insufficient Disk Space.
Insufficient disk space remains to perform a backup of the
DSA's DIB fragment.
- Insufficient Threads.
Insufficient processor threads remain to perform the requested
operation.
- Miscellaneous Resource Exhausted.
A miscellaneous resource is exhausted.
13 – Shadow Agreement Update Complete
This event is generated when a DSA successfully creates, modifies, or deletes a shadowing agreement. A shadowing agreement describes how and when a DSA must replicate a given naming context to or from another DSA. The event provides the following information: - The name of the naming context to which the agreement applies - Whether this DSA is the supplier or consumer DSA - The access point of the other DSA that the agreement applies to - The identifier of the agreement that was successfully updated Note that updating an agreement does not mean that replication has taken place. The success or failure of replication is indicated by the Shadow Update Complete and Shadow Update Failure events. This event indicates only that the DSA has successfully managed an agreement, for example, to reschedule replication.
14 – Shadow Agreement Update Failure
This event is generated when a DSA fails to create, modify,
or delete a shadowing agreement. The event provides the
following information:
- One of the following Shadowing Agreement Problems:
- Communications Problem
- DOP error received
- DOP error sent
- The name of the naming context to which the agreement applies
- Whether this DSA is consumer of supplier DSA
- The access point of the other DSA that the agreement applies to
- If the Shadowing Agreement Problem was a Communications Problem,
a diagnostic message is provided, and one of the following reasons;
- Fatal Interface Error
- Insufficient Resources
- Network Unavailable
- Address Already In Use
- Invalid AEI
- Transport Error
- System Error
- Invalid Transport Template
- Unknown Error
- ACSE User Reject
- If the Shadowing Agreement Problem was either DOP error received
or DOP error sent, one of the following reasons;
- Invalid ID
- Duplicate ID
- Unsupported Binding Type
- Not Allowed For Role
- Parameter Missing
- Role Assignment
- Invalid Start Time
- Invalid End Time
- Invalid Agreement
- Currently Not Decidable
- Modification Not Allowed
- The identifier of the agreement that was not updated.
Most of the DOP problems are self correcting. For example, the
Duplicate ID problem leads to the proposal of a different
agreement identifier. The Invalid Agreement and the Currently
Not Decidable problems may require manual intervention. See
HP Enterprise Directory - Problem Solving for
details of how to handle those problems.
15 – Shadow Update Complete
This event is generated when the DSA has successfully updated a
shadow naming context. Either the consumer DSA or the supplier DSA,
or both, may generate this event. The event provides the following
information:
- The name of the naming context that was updated.
- Whether this DSA is the supplier DSA or the consumer DSA.
- The access point of the other DSA.
- The identifier of the shadowing agreement relating to the
replication that completed successfully.
- The type of update that took place, which is one of:
- No changes
- Incremental
- Total
16 – Shadow Update Failure
This event is generated when the DSA fails to update a shadow naming
context. This event can be generated by both the supplier and the
consumer of the naming context. The event provides the following
information:
- The reason for the failure, which is one of the following:
- Supplier DSA Unavailable
- Cannot Save Updates
- Update Incompatible
- Failed to Apply Updates
- Invalid Arguments
- Cannot Read Supplier Address
- Invalid Protocol
- Unexpected Failure
- Consumer Not Authenticated
- Communications Failure
- DISP error received
- DISP error sent
- Schema incompatible
- DIT incompatible
- The name of each naming context that failed to be updated.
- Whether the DSA generating the event was the supplier
DSA or the consumer DSA.
- The access point of the DSA with which the update was processed.
- If the reason was DISP error received or DISP error sent, then
the agreement identifier is displayed, and one of the following
problems:
- Invalid Agreement ID
- Inactive Agreement
- Invalid Information Received
- Unsupported Strategy
- Missed Previous
- Full Update Required
- Unwilling To Perform
- Unsuitable Timing
- Update Already Received
- Invalid Sequencing
Most of the DISP problems are self correcting. In some cases, a
DISP problem causes a total (or full) update to occur. This makes
sure that the consumer DSA has a complete, up-to-date copy of the
relevant naming context.
Some of the DISP problems can only be generated if an HP DSA
is interworking with another vendor's DSA.
If any of these problems happen frequently, refer to HP Enterprise
Directory - Problem Solving.
17 – State Change
This event is generated when the state of the DSA changes, either as a result of a management directive, or as a result of an operational problem. The event provides the following information: - The old state of the DSA - The new state of the DSA