Could not resolve host
The given remote host could not be resolved.
6
6
compareTrue
The Compare operation completed successfully and the asserted value matched the attribute value in the entry. This is a normal result, not an error.
SERVER_DEVICE_BUSY
The server is busy processing a long-duration command and cannot accept a new request at this time. The client should retry the request when the server is free.
Numeric value: 6
Daemon unable to append to log file
The rsync daemon could not write to its log file.
References
Symbolic codes with this numeric value
- PIN_OR_KEY_MISSING PIN or Key Missing bluetooth
- CANNOT_PARSE_NUMBER Cannot parse number clickhouse
- YXDOMAIN Name exists when it should not dns
- ALREADY_EXISTS Already exists gcp
- ALREADY_EXISTS Already exists grpc
- FRAME_SIZE_ERROR Frame size error http2
- QUIC_FINAL_SIZE_ERROR Final size error http3
- NOT_LEADER_OR_FOLLOWER Not Leader or Follower kafka
- KDC_ERR_C_PRINCIPAL_UNKNOWN Client not found in Kerberos database kerberos
- 6 SERVER_DEVICE_BUSY modbus
- NFS3ERR_NXIO No such device or address nfs
- NFS4ERR_NXIO No such device or address nfs
- ENXIO No such device or address posix
- enterpriseSpecific Enterprise Specific snmp
- noAccess No Access snmp
- SQLITE_LOCKED Table locked sqlite
- SSH_DISCONNECT_COMPRESSION_ERROR Compression Error ssh
- ERROR_INVALID_HANDLE Invalid handle windows
- ENXIO No such device or address windows-errno