THIS KNOWLEDGE BASE HAS BEEN ARCHIVED AND IS NO LONGER BEING UPDATED
Please visit library.nagios.com/docs for the latest and most up-to-date documentation.
Home » Categories » Products » Nagios Log Server » Troubleshooting » Common Problems

Logs Not Appearing with Failed to Parse Date Error

Problem Description

Logs are not coming in and you see an error like this in the Logstash log:

:response=>{"create"=>{"_index"=>"logstash-2019.12.13", "_type"=>"syslog", "_id"=>"AW8Ab04im8e-JsUH61
c5", "status"=>400, "error"=>"MapperParsingException[failed to parse [timestamp8601]]; nested: MapperParsingException[
failed to parse date field [2019-12-13 18:04:52.81], tried both date format [dateOptionalTime], and timestamp number w
ith locale []]; nested: IllegalArgumentException[Invalid format: \"2019-12-13 18:04:52.81\" is malformed at \" 18:04:5
2.81\"]; "}}

You also have multiple identical input types (ex. syslog) in your input configuration, something like the following:

syslog {
  port => xxx
  type => 'syslog'
}

syslog {
    port => xxxx
    type => 'syslog'
    tags => 'Linux-Max'
}

Solution 

Logs coming in on the same input need to use the same formatting so that parsing works properly. The format that the input expects is somewhat flexible initially but once the first message comes in, the format is set(until the next day's index is created). For example, the syslog input expects all input to follow rfc3164 which can send a message like:

<0>1990 Oct 22 10:52:01 TZ-6 scapegoat.dmz.example.org 10.1.2.3 sched[0]: That's All Folks!

If a message with a different date format then comes in([2019-12-13 18:04:52.81]) you'll see a message logged like the one you see.

The fix is to make sure that all devices use the same date format or configure another input for these devices. For example:

syslog {
    port => xxxx
    type => 'alternative-syslog'
    tags => 'alternative Linux-Max'
}

See the Advanced Configuration section of the Sending ESXi Logs to Nagios Log Server document for more information on how to set the type field for specific hosts(in cases where different logs formats need to come in on the same input.



Special Offer For Knowledgebase Visitors! Get a huge discount on Nagios Log Server by clicking below.

Get 60% Off Nagios Log Server!

Did you know? Nagios provides complete monitoring of: Windows, Linux, UNIX, Servers, Websites, SNMP, DHCP, DNS, Email, Storage, Files, Apache, IIS, EC2, and more!

0 (0)
Article Rating (No Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Web Browser Reports 330 Error Content Encoding
Viewed 9507 times since Tue, Mar 7, 2017
Nagios Log Server - License Activation Issues
Viewed 5985 times since Wed, Dec 13, 2017
Nagios Log Server - Understanding and Troubleshooting Red Cluster Health
Viewed 11058 times since Mon, Apr 6, 2015
Forwarding Logs from Nagios Log Server to Another Destination
Viewed 8420 times since Wed, Sep 16, 2020
Nagios Log Server - Waiting For Database Startup
Viewed 8599 times since Wed, Oct 12, 2016
Nagios Log Server - Logstash process dying
Viewed 7177 times since Mon, Apr 10, 2017
Nagios Log Server - Resetting nagiosadmin Password
Viewed 15551 times since Tue, Aug 9, 2016
Active Directory / LDAP - Troubleshooting Authentication Integration
Viewed 22252 times since Mon, Jun 26, 2017
Nagios Log Server - Logstash not running after upgrade to 2.0
Viewed 5126 times since Tue, Nov 14, 2017
Installation errors on customized corporate builds of CentOS or RHEL
Viewed 15558 times since Tue, Jan 26, 2016