Nagios Support Forum

Looks like this is solved - I reapplied Nagios configuration via UI and loggregator is accepting logs again.

Hello, our logging server (2.0.2) recently stopped accepting logs altogether. Logstash is not working and elasticsearch is also reporting errors. No new logs are available. Tried rebooting (multiple times), closing all indices, restarting logstash/elasticsearch and following this: https://support.na...

To anyone facing the same issue: installing HAProxy on same server that runs Nagios Log Server and configuring it to terminate TLS connection and forward data to Nagios solved issue for us. Setting up HAProxy is simple. haproxy.cfg example configuration: global maxconn 10000 stats socket /var/run/ha...

Thank you for your insights. Unfortunately that means that there is no easy solution for us. Local rsyslog instance is not an option at the source at Bluemix. I am looking at ways to terminate TLS connection at destination server and pass it on to NLS as @tacolover101 suggested. Any practical ideas?...

We are running Nagios Log Server 1.4.4 and not receiving any logs from Bluemix for the past weeks. Reponse from Bluemix support about issue is that supported TLS ciphers in loggregator have changed to the following: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RS...

Thread can be closed, thanks.

Thank you for your feedback. Issue is solved - indeed configuration #2 worked, but it looks like it needed some time and restarts on both client and server to take effect.

Hello, I need to set up Nagios Logging server as a syslog-tls sink (for Bluemix / CloudFoundry). I failed to find documentation on how to do that. I generated TLS certificates and attempted to configure Inputs but failed: Attempt #1: syslog { type => 'syslog' port => 5545 ssl_cacert => "/etc/pk...