All the messages have a severity level attached to it that helps you determine how critical the message is. The levels in decreasing order of severity are:
A fatal message indicates a significant problem, such as loss of data or functionality.
Examples:
If the eDirectory server fails to load system modules like NCPEngine and DSLoader while loading modules, a fatal error is reported and logged.
If the eDirectory server fails to bind on secure port 636, then a fatal error is reported and logged.
A message that is not necessarily severe, but might be a possible cause for future problem.
Examples:
Connection failures between any two servers in tree, resulting in server getting added to bad address cache. Server can recover from this particular state by resetting the bad address cache.
If the LDAP client application does a bind and closes the connection without doing an unbind then LDAP server should log warning with appropriate warning message.
If the eDirectory server has consumed all the file descriptors and it has reached the Threshold limit as result server is not able to process any incoming requests and respond it and leading to failure of the application.
A message that could be due to invalid operation, but which will not cause any problem.
Examples:
When an client application tries to add a object for which attributes definition are not defined In schema, then eDirectory server will report the ERR_NO_SUCH_ATTRIBUTE error.
When an User tries to login with an invalid password, eDirectory server will report error ERR_FAILED_AUTHENTICATION.
A message that describes successful completion of an operation or event in the eDirectory server.
Examples:
When a module gets loaded/unloaded successfully, it may be appropriate to log an informative message of the operation.
When database cache configuration is changed, informative message should be logged on successfully saving the configuration.
A message that contains information which will help developers in debugging a program.
Examples:
While doing a dynamic group search, display all the dynamic group members with information of entry ID, partition ID, and DN of the members. This information will help in knowing that all members are returned at the eDirectory level.