Errors associated with the BAGdam database.
| Name | Severity | ID | Description | Action |
|---|---|---|---|---|
| ALREADY_OPEN | error | 3 | A GDAM database cannot be opened as it is already open. | |
| BAD_PAGED_RESULTS_COOKIE | error | 46 | A client operation failed because the passed paged results cookie/query reference was invalid. | |
| BAD_VOLUME_LABEL | fatal | 10 | An invalid entry volume label was encountered in a GDAM configuration. | |
| CANNOT_INIT_NAME_LOCK | error | 52 | Report error to support@isode.com. | |
| CONFIG_ENTRY_WRITE_FAIL | error | 32 | Failed to write an entry to the configuration database. | This suggest either an inconsistency or corruption in the database. Check for error events of type DB_ERROR in the log. If found then database corruption is a possibility. The directory server should be shutdown, a backup taken and a database recovery initiated before restarting. |
| CONFIG_FAIL | fatal | 7 | Failed to read GDAM configuration. | |
| CREATE_FAIL | error | 26 | Failed to create a GDAM. GDAM creation failure is normally due to a given invalid database directory or insufficient permissions in that directory (the user needs to be able to create the GDAM directory and then write to it). | Verify that the given GDAM database directory is a full absolute path and can be created by the calling userid. Preceding error events may contain more precise detail and context. |
| CREATED | information | 28 | A BAGDAM has been created. | None - this is an informational event. |
| CREATING_BAGDAM | information | 27 | A BAGDAM is about to be created. | None - this is an informational event. |
| DB_DEADLOCK | information | 45 | A database operation was rejected in order to resolve a deadlock. | |
| DB_ERROR | error | 17 | A low-level error occurred in a GDAM database. | |
| DB_ERROR_REPORT | error | 53 | A low-level error occurred in a GDAM database. A subsequent log message should report the GDAM or database in which the error occurred. | |
| DB_OPEN_FAIL | fatal | 12 | Failed to open a low-level database file. | |
| DIR_ACCESS | error | 5 | An invalid file was encountered during GDAM initialization. | |
| DIR_CREATE_FAIL | error | 25 | Failed to create a directory during GDAM creation. | Make sure that the named directory does not exist, or that the invoking user has sufficient permissions to create the directory. |
| DNID_NOT_FOUND | information | 51 | An entry with the given DNID was not found in the database. The most likely cause is that the entry associated with the DNID has been recently deleted. | |
| DNID_VOLUME_GET_FAIL | error | 19 | Failed to get the entry volume associated with the given DNID identifier. | |
| ENTRY_DECODE_FAIL | error | 23 | Failed to decode an entry retrieved from the database. | |
| ENTRY_ENCODE_FAIL | error | 24 | Failed to encode an entry prior to writing to the database. | |
| ENTRY_GET_FAIL | error | 20 | Failed to get the entry identified by the given DNID. | |
| ENTRY_ID_NOT_FOUND | information | 33 | An attempt to access the entry attributes failed as the id2parent database does not contain the given identifier. | |
| ENTRY_NOT_FOUND | information | 22 | An attempt to access the entry attributes failed as the id2entry database does not contain the given identifier. | |
| ENTRY_PUT_FAIL | error | 21 | Failed to put the entry identified by the given DNID. | |
| ENTRY_REMOVE_FAIL | error | 29 | Failed to remove the entry identified by the given DNID. | This suggest either an inconsistency or corruption in the database. Check for error events of type DB_ERROR in the log. If found then database corruption is a possibility. The directory server should be shutdown, a backup taken and a database recovery initiated before restarting. |
| ENV_OPEN_FAIL | critical | 18 | Failed to open a database environment for a BAGdam. | |
| EXTRACT_KNOWLEDGE_FAIL | error | 30 | At startup the directory server extracts knowledge from the | This suggest either an inconsistency or corruption in the database. Check for error events of type DB_ERROR in the log. If found then database corruption is a possibility. The directory server should be shutdown. A backup should then be taken of the GDAM for which errors are reported and a database recovery initiated before restarting. |
| FILE_OPEN_FAIL | error | 6 | Failed to open a file while initializing GDAM. | |
| GDAM_OPEN_FAIL | fatal | 8 | Failed to open a GDAM. | |
| HISTORICAL_LOG_GET_FAIL | error | 39 | GDAM failed to determine the list of historical database transaction log files for removal. | |
| INDEX_ALREADY_OPEN | error | 50 | An attempt to open or create an index has failed because an identical index is already present and open. | This event message serves only to notify of failure. Log messages preceding this one should provide context. |
| INDEX_BUILD_COMPLETE | information | 48 | An index build operation has completed. | |
| INDEX_BUILD_FAIL | error | 49 | An index build operation has failed. | This event message serves only to notify of failure. Log messages preceding this one should provide context. |
| INDEX_BUILD_START | information | 47 | An index build operation has started. | |
| INDEX_ENTRY_REMOVE_FAIL | error | 31 | Failed to remove index entries associated with the given DNID. | This suggest either an inconsistency or corruption in the database. Check for error events of type DB_ERROR in the log. If found then database corruption is a possibility. The directory server should be shutdown, a backup taken and a database recovery initiated before restarting. |
| INDEX_REMOVE_FAIL | error | 42 | An index database could not be removed. The exact reason is given in the log message detail. | |
| INVALID_CONFIG_LINE | fatal | 14 | An invalid line was encountered in a BAGdam configuration file. | |
| INVALID_DIR | error | 4 | An invalid directory was encountered during GDAM initialization. | |
| LOG_FILE_REMOVE_FAIL | error | 41 | A GDAM failed to remove to a historical database transaction log file. | |
| MULTI_NAME_LOCK_FAIL | error | 38 | An operation failed to get a multiple name lock. | |
| MULTI_NAME_LOCK_WAIT | information | 37 | An operation is waiting on a multiple name lock. | |
| NAME_ALREADY_IN_CACHE | information | 34 | The given name was already in the name cache. Most likely cause is that two directory caused a database read for that name close to simultaneously. | |
| NAME_LOCK_FAIL | error | 36 | An operation failed to get a lock on the entry with the given DNID. | |
| NAME_LOCK_WAIT | information | 35 | An operation is waiting on a lock on the entry with the given DNID. | |
| OPENED_DATABASE | information | 2 | A GDAM database has been opened. | |
| OPENING_DATABASE | information | 1 | A GDAM database is about to be opened. | |
| REMOVING_INDEX_NOT_PRESENT | error | 43 | An index database could not be removed. The exact reason is given in the log message detail. | |
| REMOVING_LOG_FILE | information | 40 | A GDAM is ready to remove to a historical database transaction log file. | |
| SEGMENT_ALREADY_MAPPED | fatal | 9 | A database segment has already been mapped to a GDAM entry volume. | |
| TOO_MANY_VOLUMES | critical | 15 | More than the maximum number of entry volumes were configured. | |
| UNMAPPED_SEGMENT | fatal | 11 | A database segment is unmapped in a GDAM configuration. | |
| UNRESOLVED_DB_DEADLOCK | error | 44 | An operation failed due to repeated database deadlock. | |
| VOLUME_CONFIGURED_TWICE | critical | 16 | A volume was specified more than once for the same GDAM. | |
| VOLUME_OPEN_FAIL | fatal | 13 | Failed to open a GDAM entry volume. |