31 EVM-00001 to EVM-00901
- EVM-00001: Cannot write raw events to a terminal
-
Cause: Attempted to redirect binary events to a terminal.
- EVM-00002: Use evmshow to format events for display
-
Cause: Attempted to redirect binary events to a terminal.
- EVM-00003: Failed to open file "string": string
-
Cause: Filename, path or the permisions were not valid.
- EVM-00004: Failed to open channel config file "string"
-
Cause: Configuration file name,the path or the permissions were not valid.
- EVM-00006: Failed to create temporary file
-
Cause: The file being used as a temporary file for evmsort had one of the following issues; filename, path or the permisions were not valid.
- EVM-00007: Failed to write to temporary file
-
Cause: The file being used as a temporary file for evmsort had one of the following issues; filename, path or the permisions were not valid.
- EVM-00008: Failed to read from temporary file
-
Cause: The file being used as a temporary file for evmsort had one of the following issues; filename, path or the permisions were not valid.
- EVM-00009: Failed to create EVM posting connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00010: Failed to read from EVM posting connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00011: Failed to write to EVM posting connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00012: Failed to create EVM listening connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00013: Failed to read from EVM listening connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00014: Failed to write to EVM listening connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00015: Failed to create EVM service connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00016: Failed to read from EVM service connection
-
Cause: Error occured while communicating with the EVM daemon.
- EVM-00017: Failed to start EVM service "string"
-
Cause: EVM daemon failed to start.
- EVM-00018: Failed to write to output stream
-
Cause: Failed to write to standard output.
- EVM-00019: Failed to read event from input stream
-
Cause: Bad input file for evmshow/evmsort EOF missing.
- EVM-00020: Failed to create event subscription
-
Cause: Bad network connection between subscriber and EVM daemon.
- EVM-00021: Failed to create filter
-
Cause: Used a null filter string or memory allocation failed.
- EVM-00022: Invalid filter string
-
Cause: Used a null or invalid filter string.
- EVM-00023: Filter test operation failed
-
Cause: Used a null or invalid filter string.
- EVM-00024: Lost connection to EVM daemon
-
Cause: Evmlogger lost connection to evmdaemon.
- EVM-00025: Authorization database error
-
Cause: Not authorized to post/listen for certain events.
- EVM-00026: Failed to post event "string"
-
Cause: Evmpost failed to post an event.
- EVM-00027: Memory allocation failure
-
Cause: The system is running low on memory.
- EVM-00029: Event contains invalid values
-
Cause: Invalid syntax for an event was used.
- EVM-00030: Event name is missing
-
Cause: Name of the event was missing.
- EVM-00031: Event name has too few components
-
Cause: Invalid syntax for an event was used.
- EVM-00032: Failed to write event
-
Cause: Failed to write event to output file.
- EVM-00033: Error in input file "string", line number
-
Cause: Failed to parse input file.
- EVM-00034: Error: string
-
Cause: Error Occured.
- EVM-00035: EVM service "string" terminated with exit code number
-
Cause: EVM daemon died.
- EVM-00036: Host "string" is unknown
-
Cause: Invalid hostname discovered while trying to create a connection to the EVM daemon.
- EVM-00037: Failed to connect to EVM daemon on "string"
-
Cause: EVM daemon is dead or is not responding.
- EVM-00038: Failed to create an EVM event
-
Cause: Failed to create an EVM event.
- EVM-00039: Invalid port number in host name "string"
-
Cause: Used an invalid port number.
- EVM-00040: Error occurred while reading from "string"
-
Cause: Error occured when evmshow was reading from an input file.
- EVM-00042: Use "string -A" to format events, or pipe output to evmshow
-
Cause: Invalid use of evmshow command.
- EVM-00043: Attempting to reconnect to the EVM daemon...
-
Cause: Evmwatch trying to reconnect to the evm daemon.
- EVM-00044: Attempting to reconnect to the EVM daemon on "string"...
-
Cause: Evmwatch trying to reconnect to the evm daemon on this host.
- EVM-00045: EVM connection re-established
-
Cause: Evmwatch was able to reconnect to the evm daemon.
- EVM-00104: End of file reached unexpectedly
-
Cause: End of event template file reached unexpectedly.
- EVM-00105: Missing end-of-group character
-
Cause: end-of-group character missing in event template file.
- EVM-00106: Missing end-of-string character
-
Cause: end-of-string character missing in event template file.
- EVM-00107: Value "string" is not valid
-
Cause: Invalid value found in the event template file.
- EVM-00108: Keyword "string" is not valid
-
Cause: Invalid keyword found in the event template file.
- EVM-00201: Failed to allocate space for application object
-
Cause: The system is running low on memory.
- EVM-00202: Failed to allocate space for local lock pathname
-
Cause: The system is running low on memory.
- EVM-00301: Failed to open logger config file "string"
-
Cause: Configuration file had one of the following problems; filename, path or permissions were not valid.
- EVM-00302: Configuration error - using default configuration
-
Cause: Configuration file had invalid configuration details
- EVM-00303: Keyword "string" is invalid in this position
-
Cause: Valid Keyword was used in an invalid position in configuration file.
- EVM-00304: Configuration error in file string, line number
-
Cause: Configuration error in configuration file.
- EVM-00305: Memory allocation failure for "string"
-
Cause: The system is running low on memory.
- EVM-00306: Failed to create filter for "string"
-
Cause: Failed to create a filter for events for evmlogger.
- EVM-00307: Filter string invalid for "string"
-
Cause: Used a null filter string or memory allocation failed.
- EVM-00308: Failed to open eventlog "string": string
-
Cause: Eventlog file had one of the following problems; filename, path or permissions were not valid.
- EVM-00309: Failed to write to eventlog "string"
-
Cause: Eventlog had one of the following problems; size or permissions were not valid.
- EVM-00310: Invalid suppression filter for eventlog "string"
-
Cause: Invalid filter was used.
- EVM-00311: Invalid entry in eventlog "string" (number events OK)
-
Cause: Evmlogger found an invalid entry in eventlog.
- EVM-00312: Eventlog "string" disabled
-
Cause: Events could not be written to the eventlog file.
- EVM-00313: Eventlog "string" re-enabled
-
Cause: Events logging is reenabled.
- EVM-00314: Forwarder "string" disabled
-
Cause: Forwarding is disabled by the evmlogger.
- EVM-00315: Forwarder "string" re-enabled
-
Cause: Forwarding is disabled by the evmlogger.
- EVM-00316: Suppression disabled for "string"
-
Cause: Error message filtering supression disabled for this string.
- EVM-00317: Suppression re-enabled for "string"
-
Cause: Error message filtering supression reenabled for this string.
- EVM-00318: Failed to open config info file "string"
-
Cause: Configuration file had one of the following problems; filename, path or permissions were not valid.
- EVM-00319: Keyword "string" is not allowed in a secondary config file
-
Cause: Invalid Keyword was used.
- EVM-00323: Config file "string" has insecure write permission
-
Cause: The configuration file had write permissions for the group 'other'.
- EVM-00324: Config file "string" has incorrect ownership
-
Cause: Configuration file should be owned by root or bin.
- EVM-00325: Config file "string" is not a regular file
-
Cause: Configuration file is not a regular file.
- EVM-00401: Failed to open binary event library file
-
Cause: Binary event file had one of the following problems; filename, path or permissions were not valid.
- EVM-00601: Data read from the input stream is not a valid EVM event
-
Cause: evmshow tried to read an invalid EVM event.
- EVM-00701: Check that the event is registered and you are authorized to post it
-
Cause: Not authorized to post for certain events.
- EVM-00702: Priority must be an integer in the range 0-number
-
Cause: Used an integer out of the range for priority.
- EVM-00801: Missed number subscribed-to event(s)
-
Cause: Missed some events during the connection setup phase.
- EVM-00802: Failed to reconnect within number seconds - terminating
-
Cause: Failed to establish a connection with EVM daemon.
- EVM-00901: Invalid sort specification "string"
-
Cause: Invalid sort specification used for evmsort.