Expand description
Standard device failed reasons, documented after their usage in cppTango and Databaseds;
the ones noted as not used by cppTango only exist there as a constant.
Constantsยง
- API_
Alias NotDefined - The device or attribute alias is not defined in the database.
- API_
Already Polled - The command or attribute is already in the polling list of the device.
- API_
Asyn Reply NotArrived - The reply of an asynchronous call has not arrived yet.
- API_
Attr Config - Attribute configuration could not be read or applied.
- API_
Attr Event Prop - Attribute event properties are wrong or cannot be set. Not used by cppTango.
- API_
Attr Incorrect Data Number - Incorrect number of elements given when writing an attribute value.
- API_
Attr NoAlarm - Alarm information was asked on an attribute which has no alarm defined.
- API_
Attr NotAllowed - The attribute operation is forbidden, e.g. a property not changeable at run time.
- API_
Attr NotFound - The attribute does not exist on the device or in its class.
- API_
Attr NotPolled - Attribute history or cached value was asked while the attribute is not polled.
- API_
Attr NotWritable - A write was attempted on an attribute which is not
READ_WRITE/READ_WITH_WRITE. - API_
Attr OptProp - Problem with the attribute value or its optional properties: null pointer, bad type.
- API_
Attr Prop Value NotSet - The numeric representation of an attribute property value has not been set.
- API_
Attr Value NotSet - The attribute value was never updated, it cannot be read nor pushed as an event.
- API_
Attr Wrong Defined - The attribute is badly defined in its class: bad data type, association, memorized.
- API_
Attr Wrong MemValue - The memorized value stored in the database for this attribute has an incorrect format.
- API_
Attribute Failed - Wrapper reason stacked on the real error when reading or writing an attribute failed.
- API_
Attribute NotData Ready Enabled - A
data_readyevent was asked on an attribute not data ready enabled. - API_
Attribute Polling NotStarted - An event was asked but the polling needed to push it is not started.
- API_
BadAsyn - The asynchronous callback request being looked up does not exist.
- API_
BadAsyn Poll Id - Invalid asynchronous request identifier given for the polling model.
- API_
BadAsyn ReqType - The asynchronous request type is incompatible with the call made on it.
- API_
BadConfiguration Property - A device configuration property has a wrong syntax, e.g.
polled_attr. - API_
Black BoxArgument - The argument given to read the black box is out of range.
- API_
Black BoxEmpty - Nothing is stored in the device black box yet.
- API_
Cannot Check Access Control - The access control device could not be imported, rights cannot be checked.
- API_
Cannot Open File - A file could not be opened, in cppTango the device server logging file.
- API_
Cant ActivatePOA Manager - Activation of the CORBA POA manager failed. Not used by cppTango.
- API_
Cant Connect ToDatabase - The database device could not be reached on the given host and port.
- API_
Cant Connect ToDevice - The connection to the device could not be built, e.g. nil reference or dead server.
- API_
Cant Create Class Poa - Creation of the CORBA POA of a device class failed. Not used by cppTango.
- API_
Cant Create Locking Thread - The thread keeping a device lock alive could not be created.
- API_
Cant Destroy Device - The device to remove is not in the device list of its Tango class.
- API_
Cant Find Locking Thread - No locking thread was found for that device, e.g. unlocking a non locked device.
- API_
Cant GetClient Ident - The client identification, required by the lock commands, could not be retrieved.
- API_
Cant GetDev Object Id - The CORBA reference id of a device could not be obtained.
- API_
Cant Install Signal - Installing a signal handler failed, bad signal number or OS error.
- API_
Cant Resolve Host - The addresses of a host could not be resolved. Specific to rstango: cppTango has no such reason.
- API_
Cant Retrieve Class - The Tango class of a device could not be retrieved.
- API_
Cant Retrieve Class List - The class list of a device server could not be retrieved. Not used by cppTango.
- API_
Cant Store Device Class - The device class could not be inserted in the client side class cache.
- API_
Class NotFound - The Tango class is not known by the device server process.
- API_
Client TooOld - The client Tango release is too old for events or device locking.
- API_
CmdArgument Type NotSupported - The command argument data type is not handled by this code path.
- API_
CmdNot Polled - Command history or cached result was asked while the command is not polled.
- API_
Command Failed - Wrapper reason stacked on the real error when a
command_inoutfailed. - API_
Command NotAllowed - The command is not allowed in the current device state.
- API_
Command NotFound - The command does not exist in the command list of the device class.
- API_
Command Timed Out - A server side timeout expired on a serialization monitor or a blocked polling thread.
- API_
Communication Failed - The network exchange with the device failed, wraps the transport error.
- API_
Connection Failed - A connection to a peer failed, in cppTango the log consumer device.
- API_
Corba Exception - A CORBA user exception was received and translated into a Tango error.
- API_
Corba SysException - A CORBA system exception was caught, an unexpected ORB or transport failure.
- API_
Corrupted Database - The database returned inconsistent attribute or pipe properties.
- API_
DSFailed Registering Event - The device server refused or failed the event registration.
- API_
DServer Class NotInitialised - The
DServerclass singleton is not initialized yet. - API_
Database Access - An error occurred while reading from or writing to the database.
- API_
Database Cache Access - The entry is not available from the database cache built at server startup.
- API_
Database File Error - Error with the file database used in
-file=mode: syntax, access or missing class. - API_
Decode Err - Decoding of a
DevEncodedpayload failed. - API_
Deprecated Command - A deprecated admin command was called, e.g.
SetTraceLevel. - API_
Device Already Defined - The device is already defined in the database. Not used by cppTango.
- API_
Device Locked - The device is locked by another client, the request is refused.
- API_
Device NotDefined - The device is not defined in the database, it cannot be imported.
- API_
Device NotExported - The device is defined but not exported, its device server is not running.
- API_
Device NotFound - The device was not found in the device list of the server.
- API_
Device NotLocked - The operation requires the device to be locked first.
- API_
Device NotPolled - The device, or one of its objects, is not polled.
- API_
Device Timed Out - The client side timeout expired while waiting for the device answer.
- API_
Device Unlockable - The device cannot be locked at all, e.g. the admin or database device.
- API_
Device Unlocked - The lock owned on the device has been released, reported to its holder.
- API_
Dummy Exception - Placeholder reason with no meaning, used internally and never propagated.
- API_
Empty Data Element - The pipe data element is empty, it holds no value to extract.
- API_
Empty DbDatum - The
DbDatumholds no data, the requested extraction is impossible. - API_
Empty DbDb Datum - Same as
API_EmptyDbDatum, kept because of a historical typo in cppTango. - API_
Empty Device Attribute - The
DeviceAttributeholds no data, the read failed or it is uninitialized. - API_
Empty Device Data - The
DeviceDataholds no data, the requested extraction is impossible. - API_
Encode Err - Encoding of a
DevEncodedpayload failed. - API_
Event Channel NotExported - The notifd event channel could not be found, no notifd runs on that host.
- API_
Event Consumer - No event consumer object is available, no subscription was done before.
- API_
Event NotFound - The given event id is unknown, on unsubscribe or event queue access.
- API_
Event Properties NotSet - The event properties needed by the requested event are not configured.
- API_
Event Queues - Misuse of the event queue: none configured, or no event available to return.
- API_
Event Supplier NotConstructed - The event supplier of the server is not created yet.
- API_
Event Timeout - No event was received within the keep alive period, pushed to the callback.
- API_
FwdAttr Inconsistency - Internal inconsistency in the forwarded attribute registry maps.
- API_
FwdAttr NotConfigured - The forwarded attribute has no valid root. Not used by cppTango, see
API_AttrConfig. - API_
History Invalid - The history data received is invalid, its format could not be interpreted.
- API_
Incoherent DbData - The data received from the database device is not what the client expected.
- API_
Incoherent DevData - The data received from the device is not coherent with the type extracted.
- API_
Incoherent Values - Two related property values are incoherent, e.g.
mingreater thanmax. - API_
Incompatible Argument Type - The argument type is incompatible with the target type, e.g. for an enum.
- API_
Incompatible Attr Argument Type - The extracted type does not match the
DeviceAttributecontent. - API_
Incompatible Attr Data Type - The provided value data type does not match the attribute data type.
- API_
Incompatible CmdArgument Type - The command argument type does not match the type the command expects.
- API_
Init Method NotFound - No
init_devicemethod found for the class. Not used by cppTango. - API_
Init NotPublic - The
init_devicemethod is not public and cannot be called. Not used by cppTango. - API_
Init Throws Exception init_device()threw, so the device is no longer available.- API_
Internal Error - Unexpected internal state of the library, and generic fallback reason.
- API_
Invalid Args - An invalid argument was given to a library call or on the server command line.
- API_
Invalid Corba Any - The received CORBA
Anyhas an unexpected kind and cannot be interpreted. - API_
Java Runtime Security Exception - A Java runtime security error occurred. JTango only.
- API_
MemAtt Failed During Init - Writing a memorized attribute failed during the device startup sequence.
- API_
Memory Allocation - A memory allocation failed in the server or in the client.
- API_
Method Argument - A method argument is missing, of the wrong type, or in the wrong number.
- API_
Method NotFound - The requested method was not found. JTango and PyTango only.
- API_
Missed Events - Some events were lost, e.g. ZMQ high water mark reached, pushed to the callback.
- API_
NoData Yet - Polling is configured but its cache holds no data yet for that object.
- API_
NoSet Value Available - No write (set) value is available in the
DeviceAttribute. - API_
NonDatabase Device - The method requires a database, but the device was built without one.
- API_
NotSupported - The operation is not supported in this context, e.g. polling not externally triggered.
- API_
NotSupported Feature - The peer does not support the feature, its IDL release is too old.
- API_
NotUpdated AnyMore - The polling cache data is not refreshed any more, polling stopped or in error.
- API_
Notification Service Failed - The notifd notification service failed, e.g. its factory import.
- API_
NtDebug Window Error - Creation of the Windows debug or main output window failed.
- API_
Overloading NotSupported - Command or method overloading is not supported. PyTango and JTango only.
- API_
Pipe Data EltNot Found - Data element not found in the pipe blob. Not used by cppTango, see
API_PipeWrongArg. - API_
Pipe DuplicateDE Name - Two data elements of the same pipe blob have the same name.
- API_
Pipe Failed - Wrapper reason stacked on the real error when reading or writing a pipe failed.
- API_
Pipe NoData Element - No data element is available in the pipe blob for insertion or extraction.
- API_
Pipe NotAllowed - Reading or writing the pipe is currently not allowed, e.g. by the serial model.
- API_
Pipe NotFound - The pipe does not exist on the device or in its class.
- API_
Pipe NotWritable - A write was attempted on a pipe which is not writable.
- API_
Pipe OptProp - Problem with a pipe data element property, e.g. a null data pointer.
- API_
Pipe Value NotSet - The pipe value was never updated by the device, it cannot be read.
- API_
Pipe Wrong Arg - Wrong argument used on a pipe blob: bad index, bad data type, or blob never received.
- API_
Pipe Wrong ArgNumber - Wrong number of data elements given for a pipe. Not used by cppTango.
- API_
Poll ObjNot Found - The command or attribute is not in the polled object list of the device.
- API_
Poll Ring Buffer Empty - Not enough data is stored yet in the polling ring buffer.
- API_
Poll Thread OutOf Sync - The polling thread lost its schedule and is out of sync.
- API_
Polled Device NotIn Pool Conf - The polling pool is full and the device is not in the pool configuration.
- API_
Polled Device NotIn Pool Map - The polling pool is full and the device is missing from the polled map.
- API_
Polling Thread NotFound - No polling thread was found for that device or thread id.
- API_
Read Only Mode - Access control refused the request, the client only has read access.
- API_
Root Attr Failed - Root attribute access failed. Not used by cppTango, see
API_AttributeFailed. - API_
Server NotRunning - The device server process is not running, reported without database.
- API_
Shutdown InProgress - The device server is shutting down and refuses the request.
- API_
Signal OutOf Range - The signal number is out of range or cannot be handled by a user handler.
- API_
Startup Sequence - An error occurred in the device server startup sequence.
- API_
StdException - A
std::exceptionwas caught and translated into a Tango error. - API_
System Call Failed - A system call failed, e.g. socket creation or
getifaddrs(). - API_
Tango Host NotSet - The
TANGO_HOSTvariable is not set, or its syntax is incorrect. - API_
Throw Exception - Generic reason for an exception thrown on purpose. Not used by cppTango.
- API_
Unsupported Attribute - The attribute is not supported by the device.
- API_
UnsupportedD Base Modifier - Unsupported database modifier in a name, only
#dbase=no|yesare valid. - API_
Unsupported Feature - The feature is absent from this build, e.g. a Tango built without jpeg.
- API_
Unsupported Protocol - Unsupported protocol prefix in a name, only
tango://is supported. - API_
Util Singleton NotCreated - The
Utilsingleton is not created, Tango is not initialized. - API_
Util Singleton Poisoned - The
Utilsingleton was inherited through afork()withoutexec(). - API_
WAttr Outside Limit - The written value is outside the attribute limits, or is NaN/Inf, or too large.
- API_
Wizard Conf Error - A property is already defined in the wizard configuration of the class.
- API_
Wrong Attribute Name Syntax - Invalid attribute name syntax, four fields or a plain alias are expected.
- API_
Wrong CmdLine Args - Wrong command line arguments given to the device server.
- API_
Wrong Device Name Syntax - Invalid device name syntax,
domain/family/memberis expected. - API_
Wrong Event Data - The event data received is malformed and cannot be turned into a value.
- API_
Wrong Format - The
DevEncodeddata is not in the expected image format. - API_
Wrong History Data Buffer - The history data buffer received from the server is not valid.
- API_
Wrong Locking Status - The locking status returned by the server is invalid.
- API_
Wrong Number OfArgs - Wrong number of arguments given to a command, mostly the admin ones.
- API_
Wrong Wildcard Usage - Wrong use of wildcards in a pattern, only one
*is allowed. - API_
ZmqFailed - A ZMQ call failed at run time, when binding or pushing an event or heartbeat.
- API_
ZmqInit Failed - ZMQ initialisation failed, on context creation or socket bind at startup.
- DB_
Alias NotDefined Databaseds: no alias for that device/attribute, or nothing matches that alias.- DB_
Class NotFound InCache - The Tango class was not found in the startup database cache.
- DB_
Device NotDefined Databaseds: device, server, event or class not defined in the database.- DB_
Device NotFound InCache - The device or object was not found in the startup database cache.
- DB_
SQLError Databaseds: a MySQL query, a stored procedure or the given SQL command failed.- DB_
TooOld Stored Proc - The database stored procedure is too old, e.g. pipes need release 1.9.