Page 2 of 2
Re: Nagios Log server logstash behaving crazy
Posted: Tue Jun 27, 2017 11:51 am
by anish
Hi ,
I have deleted the 2014 indices from indices and restarted the elastic search service . But the index logstash-2014.06.27 reappeared . Deleted the file from both the nodes but i can see the 2014 for the date 27 reappeared after restarting the service
Re: Nagios Log server logstash behaving crazy
Posted: Tue Jun 27, 2017 1:18 pm
by cdienger
I'd like to take a closer look. Please open a ticket and we can setup a time for a remote.
Re: Nagios Log server logstash behaving crazy
Posted: Wed Jun 28, 2017 5:14 am
by anish
can you please let me know the procedure to raise the ticket with Nagios Support.
Re: Nagios Log server logstash behaving crazy
Posted: Wed Jun 28, 2017 9:39 am
by cdienger
You can email
[email protected]. If your email address is not in our system then you will receive a bounce back and will have to email
[email protected] to be added. Feel free to PM me if you have any issues creating a case.
Re: Nagios Log server logstash behaving crazy
Posted: Thu Jul 06, 2017 9:24 am
by anish
The issue got resolved after updating the NTPD on both the nodes and then restarting the services . Thanks for help
Re: Nagios Log server logstash behaving crazy
Posted: Thu Jul 06, 2017 10:03 am
by scottwilkerson
Excellent.
Yes, Log Server will create indexes in the past/future if it is receiving logs from a different time that contain their own timestamp. This can actually be quite useful because you can load historical logs into Log Server and have them on the correct dates.