Chapter 10 Directory Proxy Server Error Log Message Reference

This chapter lists messages logged by Directory Proxy Server . While this list is not exhaustive, the information presented in this chapter serves as a good starting point for resolving common problems.

The error is severe so immediate action should be taken to avoid any service loss.

When using the error log for debugging, increase the log level progressively until the debugging data you need becomes evident in the log. Do not enable error logging for all Directory Proxy Server components at once, especially on a production system, to avoid severely impacting performance.

Common Administrative Alert Codes

This section describes the administrative alert codes displayed in the instance-path/logs/errors log and the appropriate action to take should these alerts occur.

1000: Server startup

Description:

Proxy instance has started.

Solution:

dpadm start

1001: Clean Server Shutdown

Description:

Clean Server Shutdown alert is displayed when the Directory Proxy Server instance is stopped via. LDAP by the ShutDown task plug-in. The command-line interface implementation does not currently use this stop method.

1002: Abrupt Server Shutdown

Description:

Directory Proxy Server instance has shut down abruptly.

Cause:

Proxy was stopped through the command-line utility or Proxy JVM exited (Unexpected Fatal Exception, Out Of Memory...)

Solution:

Restart the Directory Proxy Server instance.

dpadm restart

1003: Configuration Reloaded: OK

Description:

This alert is raised when the proxy dynamically reload the configuration file as a whole. This may happen in the following scenarios:

• The Reload Configuration task plug-in is invoked via LDAP. This is currently not used by the monitoring framework.

• It is possible to configure the proxy to automatically reload its configuration file when it is manually modified, that is, using a text editor. This feature is disabled by default for security and reliability reasons.

This alert is never raised using standard configuration.

Cause:

The configuration file is changed on the disk.

Solution:

Do not manually edit the configuration file, use dpconf to configure the proxy instance.

1004: Configuration Reloaded: Warning

Description:

See the error code 1003. The server failed to reload the configuration but the running instance is not impacted by the configuration problem. As for the error code 1003, this can never occur with a default configuration as automatic configuration reloading is disabled.

1005: Configuration Reloaded: Error

Description:

See the error code 1003. The server failed to reload the configuration and the running instance could possibly be impacted by the configuration problem. As for the error code 1003, this can never occur with a default configuration as automatic configuration reloading is disabled.

2000: Data Source Not Available

Description:

A data Source is not available anymore. Last proactive monitoring query showed data source is unavailable.

Cause:

The error occurred because of any of the following reasons:

• Data source has been put offline

• Data source crashed

• Network issue

Solution:

Do any of the following:

• Bring data source back up

• Fix network issue

Bring data source down.

2001: Data Source Available

Description:

A Data Source has become available. Last proactive monitoring query showed data source is available.

Cause:

A Data source has been added or put online.

Solution:

Bring data source up.

3000: Listener Not Available

Description:

The error is raised when a listener gets fatal IO exception during the accept()() system call. This error might prevent the proxy from restarting. It needs to be addressed as soon as it occurs.

Cause:

The listener port is already in use.

Solution:

Do the following to solve the problem:

• Change port to an unused value.

• Free the port by stopping the application bound to it.

4000: Data Inconsistency in Data Sources

Description:

The error occurs when an operation has to be applied on multiple back ends partially failed. This only may happen for write LDAP operations. For instance it would be raised when an add must be applied to two data views, if the add to the first data view goes through, the add to the second data view fails and automatic rollback, which consists in deleting the previously added entry in first data view, fails as well.

This may happen in Virtualization and Distribution use cases only.

Cause:

An update, add, or delete operation has failed on one data source and the roll back operation is not performed.

Solution:

When an operation must be applied to two data views, the proxy first make sure both are able to serve the request by allocating a connection to each data view. So to reproduce easily the problem, use a modify request targeting two data views and tweak the data so that the modify succeeds on the first data view and fails on the second one. For example, value already exists.

Common Error Messages

This section describes the error messages displayed in the instance-path/logs/errors and instance-path/logs/access logs and the appropriate action to take should these errors occur.

No value provided for required attribute listenPort in client listener listener-entry-dn. Disabling the listener.

Solution:

Set the listen-port in ldap-listener or ldaps-listener with a port number in which the listener should listen for new connections from the client

Attribute listenPort must have a value between 1 and 65535. Disabling the listener.

Solution:

Set the listen-port in ldap-listener or ldaps-listener with a port number that should be in the range from 1 to 65535.

Attempt to reload Proxy Server configuration failed. (exception-detail). Current configuration not altered.

Solution:

Check the server configuration is valid, that is, it contains all the necessary entries and the configuration file is a valid ldif file.

Directory Proxy Server configuration reload failed. Directory Proxy server configuration may be inconsistent.

Solution:

Check the server configuration is valid, that is, it contains all the necessary entries and the configuration file is a valid ldif file.

Unable to create entry from information starting at line line-number in the configuration file -- "dn: " expected but found "problematic-line-from-config-file".

Solution:

Check if the server configuration file is a valid ldif file.

Unable to create entry from information starting at line line-number in the configuration file -- "attr: value" expected but found "problematic-line-from-config-file".

Solution:

Check if the server configuration file is a valid ldif file.

Unable to initialize SSL (exception-detail) -- SSL may fail.

Solution:

Check the SSL configuration - certificate database location, keystore password, nick names of client and server certificates.

Attempt to reload file ldif-file-name failed. (exception-detail). Current DIT not altered.

Solution:

Check if the server configuration file is a valid ldif file.

Search of "search-base-dn" would have returned multiple data views. This indicates a bad distribution configuration.

Solution:

Check if there are more than one data views with the same base dn.

Invalid value for attribute listenPort. Port already in use.

Solution:

Set the listen-port in ldap-listener or ldaps-listener with a port number that is not in use.

Can't invoke alert plugin config-entry-dn-of-alert-plugin -- exception-detail

Solution:

Check the alert plugin configuration.

Unable to register plugin config-entry-dn-of-postop-plugin as a postoperation add plugin -- exception-detail

Solution:

Check the postop plugin configuration.

The attribute attribute-name does not support case sensitive queries. Use only cis ldap-syntax for this attribute.

Solution:

The ldap-syntax of jdbc-attr is specified as ces and the matching sql column is found to be case-insensitive. Directory Proxy Server supports only the following possibilities - ldap-syntax:cis and sql-column:case-insensitive, ldap-syntax:cis and sql-column:case-sensitive, ldap-syntax:ces and sql-column:case-sensitive. Change the configuration to the one supported by Directory Proxy Server.

Server address provided in attribute serverAddress in configuration entry config-entry-dn-of-ldap-data-source can't be resolved. -- LDAP Server ldap-data-source-name disabled.

Solution:

Check if the host-address value provided in ldap-address attribute of ldap-data-source is valid and resolvable.

Could not decrypt password exception-detail

Solution:

If the password values in the server configuration are changed manually or through some other means, restore the password value with the valid value that was present previously.

Unable to create client listener name-of-listener: I/O Exception detail. Disabling the client listener.

Solution:

Check the listener address and port.

SSL Initialization Failed: exception-detail

Solution:

Check the SSL configuration.

Unable to access database metadata for table jdbc-table-name in data view jdbc-data-view-name -- some SQL statements may fail.

Solution:

Check the configuration or the connection to the back-end database.

Unable to get the Metadata information for the backend jdbc-data-source-info -- exception-detail

Solution:

Check if the connection to the back-end database specified in jdbc-data-source is alive.

Failed to create a connection to ldap-data-source-info.

Solution:

Check if the connection to the back-end LDAP server specified in ldap-data-source is alive. Also check the ldap-data-source configuration.

SQL Exception when committing the transaction to the database: db-name on server db-url -- exception-detail Cause: cause-of-exception SQL State: sql-state Vendor specific exception code: error-code.

Solution:

Check if the connection to the back-end database specified in jdbc-data-source is alive. Also refer to the documentation of RDBMS server vendor for the possible causes of the problem

SQL Exception when executing query to get column metadata: exception-detail Cause: cause-of-exception SQL State: sql-state Vendor specific exception code: error-code.

Solution:

Check if the column specified in JDBC attributes exists in the table at the back-end. Check if the connection to the back-end database specified in jdbc-data-source is alive. Refer the documentation of RDBMS server vendor for the possible causes of the problem.

Unable to connect to JDBC server jdbc-data-source-info -- exception-detail

Solution:

Check the jdbc-data-source configuration.

Fatal uncaughtException in thread-name. No more monitoring running on data-source-info

Solution:

Check the available Java Virtual Machine (JVM) memory for Directory Proxy Server.

Fatal uncaughtException in thread-name. Abandon current operation.

Solution:

Check the available JVM memory for Directory Proxy Server.

Fatal uncaughtException in thread-name.Abandon and send error response to the client.

Solution:

Check the available JVM memory for Directory Proxy Server.

Fatal uncaughtException in thread-name. Disconnecting all client connections.

Solution:

Check the available JVM memory for Directory Proxy Server.

ACI syntax error

Solution:

Check the ACI Syntax.