Apply config never complete | Ports not shown on configure

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
irfansst
Posts: 8
Joined: Fri Jun 12, 2020 11:10 am

Apply config never complete | Ports not shown on configure

Post by irfansst »

Hello All,


I have running nagios log server which is streaming logs and which are processed and shown on dashboard properly.
Recently I added some more input and output filters for new source server.
There are two issues which I observed which are as follow:


1. While performing apply configuration, it keeps on applying for longer duration 15 mins or more than that never seen it as completed.
Although after 2 3 mins I was able to see new port in configure page, so I proceeded further in adding more filters and same were reflected in configure page.


2. After a day on adding 20 filters, Now i am not able to see any tcp ports on this page which we configure in input filters.


Configuration Editor
The configuration editor is used to write configurations for Logstash running on each of the Log Server instances. The local configurations can be written to Logstash on each of the instances in your cluster. You can also add global config options which will be applied to the top of all configuration files on every Log Server instance in the cluster. Global configurations are an easy way to set up the same Logstash configuration on all your instances.


Logstash is currently collecting locally on: IP tcp: ports -- This line is not shown as of now


Although my dashboards and alerts are working fine for which were configured previously from old source server.
Attachments
CONFIG_PORT_NOT_SHOWN
CONFIG_PORT_NOT_SHOWN
APPLY CONFIG
APPLY CONFIG
gormank
Posts: 1114
Joined: Tue Dec 02, 2014 12:00 pm

Re: Apply config never complete | Ports not shown on configu

Post by gormank »

You might want to look at the logstash.log to see if it says anything interesting. I'd experiment with disabling say, half of the filters, apply and see if it's different, then the other half, apply again, etc. until you find the filter (if any) causing the trouble.
If this is a newer Linux version, try systemctl status logstash -l to see if that says something interesting.
Locked