Search found 125 matches
- Wed Feb 03, 2016 12:56 pm
- Forum: Nagios Log Server
- Topic: Lookback period issue regression in 1.4
- Replies: 38
- Views: 2733
- Wed Feb 03, 2016 11:49 am
- Forum: Nagios Log Server
- Topic: Lookback period issue regression in 1.4
- Replies: 38
- Views: 2733
Re: Lookback period issue regression in 1.4
Hey what's the status of Bug ID: 7652?
- Wed Feb 03, 2016 10:27 am
- Forum: Nagios Log Server
- Topic: Lookback period issue regression in 1.4
- Replies: 38
- Views: 2733
Re: Lookback period issue regression in 1.4
Ok here's my results from creating the new check as requested yesterday.
6:45AM Today 7:00AM Today It doesn't appear to be an issue with the check as I recreated it completely.
6:45AM Today 7:00AM Today It doesn't appear to be an issue with the check as I recreated it completely.
- Tue Feb 02, 2016 6:18 pm
- Forum: Nagios Log Server
- Topic: Lookback period issue regression in 1.4
- Replies: 38
- Views: 2733
Re: Lookback period issue regression in 1.4
Sounds good. Thanks.
- Tue Feb 02, 2016 2:27 pm
- Forum: Nagios Log Server
- Topic: Logstash Lumberjack Input crash: Security Issue
- Replies: 11
- Views: 2200
Re: Logstash Lumberjack Input crash: Security Issue
I think you're good with most things. I believe I've redacted out most of the private information. But If I've posted it visible for all, it's fair game.
- Tue Feb 02, 2016 11:41 am
- Forum: Nagios Log Server
- Topic: Lookback period issue regression in 1.4
- Replies: 38
- Views: 2733
Re: Lookback period issue regression in 1.4
Even with the backups disabled. I get an alarm around 6:45 every morning that clears at 7:00AM
Manual checks during this time still bring failed results.
Manual checks during this time still bring failed results.
- Mon Feb 01, 2016 2:16 pm
- Forum: Nagios Log Server
- Topic: Logstash Lumberjack Input crash: Security Issue
- Replies: 11
- Views: 2200
Re: Logstash Lumberjack Input crash: Security Issue
As for Received an event that has a different character encoding than you configured , this happens due to the non-UTF8 characters being sent from the remote side. Notably: REDACTED.COM, request: "P?c?60" Do you think there's some issue logstash has processing these url formatted control ...
- Mon Feb 01, 2016 12:59 pm
- Forum: Nagios Log Server
- Topic: Logstash Lumberjack Input crash: Security Issue
- Replies: 11
- Views: 2200
Re: Logstash Lumberjack Input crash: Security Issue
Upgrade completed. Sorry it took so long, internal protocol dictates I snapshot the VM before upgrading anything. So I had to take it offline for a bit. After it came back up I see the following. {:timestamp=>"2016-02-01T12:43:26.996000-0500", :message=>"Lumberjack input: the pipeline...
- Mon Feb 01, 2016 12:02 pm
- Forum: Nagios Log Server
- Topic: Logstash Lumberjack Input crash: Security Issue
- Replies: 11
- Views: 2200
Re: Logstash Lumberjack Input crash: Security Issue
Also as another thought. So you still think this isn't related to the specific messages? Just to congestion? It could make sense as we did maintenance that disconnected some remote devices from the log server for several hours. However I didn't see a ramp-up after the maintenance which I would expec...
- Mon Feb 01, 2016 11:30 am
- Forum: Nagios Log Server
- Topic: Logstash Lumberjack Input crash: Security Issue
- Replies: 11
- Views: 2200
Re: Logstash Lumberjack Input crash: Security Issue
I will try that today, probably right after I get out of my meeting.
Thanks!
Thanks!