The following tables list the critical log messages from dashboard.log file. The dashboard.log file is rotated every 24-hours.
Log messages Description
error - fatal protocol violation This message is logged in dashboard.log when there is a HTTP/(S) protocol error while connecting to ABS or Elasticsearch.
error - fatal transport error This message is logged in dashboard.log when there is an unknown host for ABS or Elasticsearch.
error - error while sending message to syslog This message is logged in dashboard.log when the syslog server is not reachable, or there is an error in configuration of SSL or non-SSL connections.
error - capacity full in syslog consumer worker, retries exhausted, ignoring this message This message is logged in dashboard.log when the Syslog server is not reachable, or there is an error in the configuration of SSL or non-SSL connections.
error - error while closing response stream This message is logged in dashboard.log when ABS, or Elasticsearch socket is not closed properly.
error - error while flushing file stream This message is logged in dashboard.log when there is a failure in the storage disk, or the storage disk is full..
error - error while closing file stream This message is logged in dashboard.log when there is a failure in the storage disk, or the storage disk is full..
error - error while parsing access_time from file This message is logged in dashboard.log when ABS returns an invalid access_time or the time format is not consistent.
error - error while parsing api_key name from file This message is logged in dashboard.log when ABS returns an empty API Key in the API Key metrics or attack report.
error - error while parsing cookie name from file This message is logged in dashboard.log when ABS returns an empty cookie name in the metrics or attack report.
warn - http request " + <URL> + ", response status: " + <Response status> This message is logged in dashboard.log when ABS or Elasticsearch returns HTTP status code that is greater than or equal to 300.
Dashboard stopped This message is logged in dashboard.log when Dashboard is shutdown.