DAOS error numbering starts at 1000. The most common errors are documented in the table below.
|DER_EXIST||1004||Entity already exists|
|DER_NONEXIST||1005||The specified entity does not exist|
|DER_NOSPACE||1007||No space left on storage target|
|DER_ALREADY||1008||Operation already performed|
|DER_NOMEM||1009||Out of memory|
|DER_NOSYS||1010||Function not implemented|
|DER_BUSY||1012||Device or resource busy|
|DER_UNINIT||1015||Device or resource not initialized|
|DER_TRUNC||1016||Buffer too short|
|DER_OVERFLOW||1017||Data too long for defined data type or buffer size|
|DER_OOG||1019||Out of group or member list|
|DER_HG||1020||Transport layer mercury error|
|DER_BADPATH||1026||Bad path name|
|DER_NOTDIR||1027||Not a directory|
|DER_EVICTED||1032||Rank has been evicted|
|DER_DOS||1034||Denial of service|
|DER_BAD_TARGET||1035||Incorrect target for the RPC|
|DER_HLC_SYNC||1037||HLC synchronization error|
|DER_IO||2001||Generic I/O error|
|DER_ENOENT||2003||Entry not found|
|DER_NOTYPE||2004||Unknown object type|
|DER_NOSCHEMA||2005||Unknown object schema|
|DER_KEY2BIG||2012||Key is too large|
|DER_REC2BIG||2013||Record is too large|
|DER_IO_INVAL||2014||IO buffers can't match object extents|
|DER_EQ_BUSY||2015||Event queue is busy|
|DER_SHUTDOWN||2017||Service should shut down|
|DER_INPROGRESS||2018||Operation now in progress|
|DER_NOTREPLICA||2020||Not a service replica|
|DER_REC_SIZE||2024||Record size error|
|DER_TX_RESTART||2025||Transaction should restart|
|DER_DATA_LOSS||2026||Data lost or not recoverable|
|DER_TX_BUSY||2028||TX is not committed|
|DER_AGENT_INCOMPAT||2029||Agent is incompatible with libdaos|
When an operation fails, DAOS returns a negative DER error.
For a full list of errors, please check
DER_ERR_GURT_BASE is equal to 1000, and
DER_ERR_DAOS_BASE is equal
The function d_errstr() is provided in the API to convert an error number to an error message.
On the server side, there are three log files created as part of normal server operations:
|Component||Config Parameter||Example Config Value|
Control Plane Log¶
The default log level for the control plane is INFO. The following
levels may be set using the
control_log_mask config parameter:
Data Plane Log¶
Data Plane (
daos_engine) logging is configured on a per-instance
basis. In other words, each section under the
servers: section must
have its own logging configuration. The
log_file config parameter
is converted to a D_LOG_FILE environment variable value. For more
detail, please see the Debugging System
section of this document.
Privileged Helper Log¶
By default, the privileged helper only emits ERROR-level logging which
is captured by the control plane and included in that log. If the
helper_log_file parameter is set in the server config, then
DEBUG-level logging will be sent to the specified file.
Daos Agent Log¶
log_file config parameter is set in the agent config, then
DEBUG-level logging will be sent to the specified file.
DAOS uses the debug system defined in
specifically the GURT library.
Both server and client default log is
otherwise set by
D_LOG_FILE environment variable (client) or
log_file config parameter (server).
The debug logging system includes a series of subsystems or facilities which define groups for related log messages (defined per source file). There are common facilities which are defined in GURT, as well as other facilities that can be defined on a per-project basis (such as those for CaRT and DAOS). DD_SUBSYS can be used to set which subsystems to enable logging. By default all subsystems are enabled ("DD_SUBSYS=all").
DAOS Facilities: common, tree, vos, client, server, rdb, pool, container, object, placement, rebuild, tier, mgmt, bio, tests
Common Facilities (GURT): MISC, MEM
CaRT Facilities: RPC, BULK, CORPC, GRP, LM, HG, ST, IV
All macros that output logs have a priority level, shown in descending order below.
D_FATAL(fmt, ...) FATAL
D_CRIT(fmt, ...) CRIT
D_ERROR(fmt, ...) ERR
D_WARN(fmt, ...) WARN
D_NOTE(fmt, ...) NOTE
D_INFO(fmt, ...) INFO
D_DEBUG(mask, fmt, ...) DEBUG
The priority level that outputs to stderr is set with DD_STDERR. By default in DAOS (specific to the project), this is set to CRIT ("DD_STDERR=CRIT") meaning that all CRIT and more severe log messages will dump to stderr. However, this is separate from the priority of logging to "/tmp/daos.log". The priority level of logging can be set with D_LOG_MASK, which by default is set to INFO ("D_LOG_MASK=INFO"), which will result in all messages excluding DEBUG messages being logged. D_LOG_MASK can also be used to specify the level of logging on a per-subsystem basis as well ("D_LOG_MASK=DEBUG,MEM=ERR").
DEBUG messages account for a majority of the log messages, and finer-granularity might be desired. Mask bits are set as the first argument passed in D_DEBUG(mask, ...). To accomplish this, DD_MASK can be set to enable different debug streams. Similar to facilities, there are common debug streams defined in GURT, as well as other streams that can be defined on a per-project basis (CaRT and DAOS). All debug streams are enabled by default ("DD_MASK=all").
DAOS Debug Masks:
md = metadata operations
pl = placement operations
mgmt = pool management
epc = epoch system
df = durable format
rebuild = rebuild process
daos_default = (group mask) io, md, pl, and rebuild operations
Common Debug Masks (GURT):
any = generic messages, no classification
trace = function trace, tree/hash/lru operations
mem = memory operations
net = network operations
io = object I/Otest = test programs
Common Use Cases¶
Generic setup for all messages (default settings)
$ D_LOG_MASK=DEBUG $ DD_SUBSYS=all $ DD_MASK=all
Disable all logs for performance tuning
$ D_LOG_MASK=ERR -> will only log error messages from all facilities $ D_LOG_MASK=FATAL -> will only log system fatal messages
Disable a noisy debug logging subsystem
$ D_LOG_MASK=DEBUG,MEM=ERR -> disables MEM facility by restricting all logs from that facility to ERROR or higher priority only
Enable a subset of facilities of interest
$ DD_SUBSYS=rpc,tests $ D_LOG_MASK=DEBUG -> required to see logs for RPC and TESTS less severe than INFO (the majority of log messages)
Fine-tune the debug messages by setting a debug mask
$ D_LOG_MASK=DEBUG $ DD_MASK=mgmt -> only logs DEBUG messages related to pool management
Refer to the DAOS Environment Variables document for more information about the debug system environment.
Common DAOS Problems¶
When DER_AGENT_INCOMPAT is received, it means that the client library libdaos.so is likely mismatched with the DAOS Agent. The libdaos.so, DAOS Agent and DAOS Server must be built from compatible sources so that the GetAttachInfo protocol is the same between each component. Depending on your situation, you will need to either update the DAOS Agent or the libdaos.so to the newer version in order to maintain compatibility with each other.
When DER_HLC_SYNC is received, it means that sender and receiver HLC timestamps are off by more than maximum allowed system clock offset (1 second by default).
In order to correct this situation synchronize all server clocks to the same reference time, using services like NTP.
Bugs should be reported through our issue tracker1 with a test case to reproduce the issue (when applicable) and debug logs.
After creating a ticket, logs should be gathered from the locations described in the Log Files section of this document and attached to the ticket.
To avoid problems with attaching large files, please attach the logs in a compressed container format, such as .zip or .tar.bz2.