Result code hierarchy
From GEANT2-JRA1 Wiki
Contents |
[edit]
Result codes
Read more about Result codes.
[edit]
Hierarchy
[edit]
perfSONAR base
- error.common.no_configuration - Service internal error -- service cannot find configuration component and doesn't work properly
- error.common.no_logger - Service internal error -- service cannot find logger component and doesn't work properly
- error.common.parse_error - Parsing error -- something wrong with request message (not well-formed XML or not NMWG accordant)
- error.common.manager.no_configuration - Service internal error:wrong server configuration, service cannot finds internal components configuration
- error.common.manager.cant_create_component - Service internal error -- wrong server configuration, service cannot create internal components (probably wrong class names)
- error.common.service_engine.creation_failure - ServiceEngineFactory could not create an ServiceEngine. If it isn't because the class wasn't found, it's likely that it's a bug.
- error.common.action_not_supported - Selected service Engine doesn't support such request type. Often occurs when trying to send for instance MA-request to non-MA service (e.g. LS)
- error.common.action_not_implemented - Action not implemented (some message types may be reserved for future use)
- error.common.storage.xmldb.open - XML DB Storage Manager - cannot open database (perhaps wrong collection/username/password)
- error.common.storage.xmldb.close XML DB Storage Manager - cannot close database (problems with database connection)
- error.common.storage.xmldb.wrong_query - XML DB Storage Manager - wrong query (not XQuery/XPath or wrong-formed expression)
- error.common.storage.xmldb.empty_query - XML DB Storage Manager - empty query (without content)
- error.common.storage.xmldb.query - XML DB Storage Manager - problems with query expression
- error.common.storage.xml_file.fetch - XML File Storage Manager - fetch error (wrong query, file not found, IO error)
- error.common.storage.xml_file.init - XML File Storage Manager - initialization error
- error.common.scheduler.init - Scheduler initialization error
- warning.common.no_metadata - Warning - no metadata in request/response
- success.echo - Success from Echo Request
[edit]
Measurement Archive
[edit]
common
- error.ma.writing - unable to write data in MA
- error.ma.fetching - unable to fetch data from MA
- error.ma.fetching.timeout - unable to fetch data due to timeout.
- error.ma.fetching.interrupted - unable to fetch data because processing was interrupted externally.
- error.ma.service_engine.creation - can't create the service engine
- error.ma.action - action type is not supported by MA (there are 3 types of action: get key, get data, store data)
- error.ma.query - srtucture of query to MA is wrong
- error.ma.configuration - the MA is not correctly configured. causing it to be unable to return a result
- error.ma.metadata_configuration - component responsible for managing metadata encountered serious problem
- warning.ma.metadata_configuration - component responsible for managing metadata encounterd minor problem
- error.ma.metadata_query_mapping_configuration - unable to map correctly eventType and metadata query class (see conf/metadata-queries-map.xml)
[edit]
RRD MA
- error.ma.rrd.rrd_file - unable to get data from rrd file
- error.ma.rrd.rrdjtool - problem with rrdjtool library
[edit]
SQL MA
- error.ma.sql.db_connection - unable to connect with a database
- error.ma.sql.db_connection_ibatis - no iBatis configuration file name in the parameter list of request
[edit]
Measurement Point
[edit]
common
- ...
[edit]
TCMP
- error.mp.tcmp.data_missing_metadataIdRef - Data element is missing metadataIdRef attribute
- error.mp.tcmp.unknown_capture_interface - Unknown capture interface
- error.mp.tcmp.validator.missing_request - Request to the measurement executor cannot be null
- error.mp.tcmp.validator.no_data_elements - No data elements found in request. At least one is required in the message.
- error.mp.tcmp.validator.no_metadata_elements - No metadata elements found in request. At least one is required in the message.
- error.mp.tcmp.validator.no_metadata_subject - No subject in metadata element of request.
- error.mp.tcmp.validator.no_interface_hostName_or_ipAddress - Either hostName or ipAddress element required in interface element.
- error.mp.tcmp.validator.no_interface_ifName - ifName element required in interface element.
- error.mp.tcmp.validator.unsupported_endPoint_type - The only supported endPoint type is currently 'hostname'.
- error.mp.tcmp.validator.no_endPoint_value - endPoint value is required.
- error.mp.tcmp.validator.no_endPoint_port - endPoint port is required.
- error.mp.tcmp.validator.no_endPointPair_src_and_dst - endPointPair element requires both src and dst elements.
- error.mp.tcmp.validator.no_src_endPoint_value - src endPoint value is required.
- error.mp.tcmp.validator.no_src_endPoint_port - src endPoint port is required.
- error.mp.tcmp.validator.no_dst_endPoint_value - dst endPoint value is required.
- error.mp.tcmp.validator.no_dst_endPoint_port - dst endPoint port is required.
- error.mp.tcmp.validator.no_interface_or_endPoint_or_endPointPair - Missing one of (nmwg:interface, nmwg:endPoint, nmwg:endPointPair) elements in subject element request.
- error.mp.tcmp.validator.no_metadata_parameters - No parameters in metadata element found in request.
- error.mp.tcmp.validator.unsupported_flow_s_type_parameter - Unknown flow_s_type parameter found in request.
- error.mp.tcmp.validator.invalid_flow_s_thre_parameter - Parameter flow_s_thre is not positive Integer.
- error.mp.tcmp.validator.invalid_characteristics_parameter - Parameter characteristics is not positive Integer.
- error.mp.tcmp.validator.invalid_granularity_parameter - Parameter granularity is not positive Integer.
- error.mp.tcmp.validator.invalid_start_time_parameter - Missing or invalid start_time parameter.
- error.mp.tcmp.validator.unsupported_start_time_type - Only 'unix' start_time type is currently supported.
- error.mp.tcmp.validator.invalid_end_time_parameter - Missing or invalid end_time parameter.
- error.mp.tcmp.validator.unsupported_end_time_type - Only 'unix' end_time type is currently supported.
- error.mp.tcmp.validator.no_commonTime - Missing commonTime element inside datum element.
- error.mp.tcmp.validator.no_datum_in_commonTime - commonTime must contain at least one datum child.
- error.mp.tcmp.validator.no_first_datum_filename_attribute - First datum of commonTime must contain filename attribute.
- error.mp.tcmp.validator.invalid_first_datum_filename_attribute - Filename attribute of first datum contains file separator char.
- error.mp.tcmp.validator.no_second_datum_in_commonTime - commonTime must contain two datum childs.
- error.mp.tcmp.validator.no_second_datum_filename_attribute - Second datum of commonTime must contain filename attribute.
- error.mp.tcmp.validator.invalid_second_datum_filename_attribute - Filename attribute of second datum contains file separator char or first and second datums point to the same filename.
- error.mp.tcmp.validator.no_pcap_storage_dir - service.mp.tcmp.pcap.file.storage.dir property missing in service.properties.
- error.mp.tcmp.validator.invalid_pcap_storage_dir - service.mp.tcmp.pcap.file.storage.dir property should point to a directory!
- error.mp.tcmp.validator.first_datum_filename_exists - First datum filename already exists. Use different datum filename.
- error.mp.tcmp.validator.second_datum_filename_exists - Second datum filename already exists. Use different datum filename.
- error.mp.tcmp.validator.invalid_remote_interfaces_configuration - service.mp.tcmp.remote.interfaces entry contains host:interface token without ':' char.
- error.mp.tcmp.validator.denied_trace_on_interface - Local Tracefile capture requested, but interface is not present in service.mp.tcmp.local.interfaces property.
- error.mp.tcmp.validator.remote_host_interface_not_configured - Remote Tracefile capture requested, but host:interface is not present in service.mp.tcmp.remote.interfaces property.
- error.mp.tcmp.validator.denied_trace_on_second_interface - Local Tracefile capture requested, but second interface is not present in service.mp.tcmp.local.interfaces property.
- error.mp.tcmp.validator.second_remote_interface_not_configured - Remote Tracefile capture requested, but second host:interface is not present in service.mp.tcmp.remote.interfaces property.
[edit]
SNMP MP
- ...
[edit]
SSH/Telnet MP
- success.mp.sshtelnet - Representing a successfully executed request
- error.mp.sshtelnet.configuration - Indicates the failure to read something in the configuration file
- error.mp.sshtelnet.nosuchcommand - Indicates the command the client wants to execute is not supported or allowed
- error.mp.sshtelnet.device - Indicates that the device the client wants to contact through this Measurement Point is not supported.
- error.mp.sshtelnet.connect - Represents the fact that the SSH/Telnet Measurement Point was unable to connect to the underlying device
- error.mp.sshtelnet.parameter - Indicates something is wrong with the supplied parameters, either not satisfying the tests on the validity, or a wrong number of parameters has been supplied.
- error.mp.sshtelnet.token - Indicates that too many consequent requests are posed on this Measurement Point.
- error.mp.sshtelnet.request - General failure to execute the request.
[edit]
CLMP
- error.mp.clmp.validator.no_metadata_elements - No metadata elements found in request. At least ne is required in the message.
- error.mp.clmp.validator.unsuported_message_type - Message type in request not supported. Currently CLMP only handles MeasurementRequest messages.
- error.mp.clmp.validator.no_metadata_eventType - No eventType definition found in any of the metadata in the request.
- error.mp.clmp.cant_find_tool - Unable to find the tool abstraction for the given eventType.
- error.mp.clmp.toolFactory.hashtable - ToolBundleFactory was unable to create the tools hashtable.
- error.mp.clmp.toolFactory.cant_instantiate - ToolBundleFactory was unable to instantiate the corresponding tool object.
- error.mp.clmp.exec.exit_request - Received an exit code request for still running process while executing command.
[edit]
LS Registration component
- error.lsregistrator.no_service_description - Cannot find service.r.* properties (in service.properties file) which are responsible for creation registration metadata
- error.lsregistrator.no_service_content - Cannot find data elements (perhaps wrong XML information file)
- error.lsregistrator.no_ls_url - LS address is not provided
- error.lsregistrator.other - Any other exception, whould be described in additional data description
[edit]
Lookup Service
- error.ls.no_access_point - no accessPoint parameter in the request
- error.ls.no_storage - XML DB Storage Manager is not loaded (check components.properties)
- error.ls.action_not_suported - LS action not supported
- error.ls.no_scheduler - No scheduler component (required for LSCleanup)
- error.ls.no_metadata - Metadata cannot be found in request message
- error.ls.no_eventtype - eventType cannot be found in request message
- error.ls.eventtype_not_supported - eventType not supported
- error.ls.no_key - No Key in request message (in deregistration, update, keepalive)
- error.ls.key_not_found - Key not found in the database. For instance when trying deregister not-registered data
- error.ls.no_querytype - No query type in query/lookup message
- error.ls.querytype_not_suported - Given query type is not supported
- error.ls.update.key_not_found - Key not found when trying to update data
- error.ls.no_data_trigger - No empty data element. For most of LS requests all parameters are passed by metadata, but empty data trigger with the reference to the metadata (
<data metadataIdRef="xxx"/>) should be also added. - error.ls.cant_replace_data - Old data can't be replaced by new one. No write rights to database for such user?
- error.echo.no_storage_content - no storage schema for LS (LSStore & LSStore-control)
- success.ls.register - registration successful
- success.ls.deregister- deregistration successful
- success.ls.keepalive- keepalive successful
[edit]
Topology Service
- success.tops.downloaddb - Download database successful
- error.tops.parameters - Wrong parameters in metadata received in the request
- error.tops.fetching - Error executing an SQL query
- error.tops.dependency - Cannot obtain the requested object
[edit]
Authentication Service (AS)
There is a page explaining all result codes.
