This support forum board is for support questions relating to
Nagios Log Server , our solution for managing and monitoring critical log data.
floki
Posts: 65 Joined: Tue Dec 18, 2018 5:23 am
Post
by floki » Mon Jan 14, 2019 12:01 am
Good Day
Just want to ask what's wrong on my nagios log server instance. It seems that I can't apply the configurations made. It always show " The instance is likely offline, please check and try again". My current method is to configure the logstash pipeline [input, filter & output] then restart logstash. Is there another way I can load the the pipeline without restarting logstash like for example:
Code: Select all
bin/logstash -f first-pipeline.conf --config.reload.automatic
which is from the official documentation of logstash
scottwilkerson
DevOps Engineer
Posts: 19396 Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:
Post
by scottwilkerson » Mon Jan 14, 2019 4:24 pm
Is elasticsearch running on all instances?
Also, you should only be starting logstash through the service command instead of what you posted in your previous command
floki
Posts: 65 Joined: Tue Dec 18, 2018 5:23 am
Post
by floki » Mon Jan 14, 2019 11:13 pm
Good day,
Yes, my current method is to restart logstash with: systemctl restart logstash eventhough I only changed the input.conf. What im asking is if there's a way I can edit the conf files (input, filter, output) without restarting logstash?
scottwilkerson
DevOps Engineer
Posts: 19396 Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:
Post
by scottwilkerson » Tue Jan 15, 2019 10:15 am
the configurations should only be edited through the UI.
floki
Posts: 65 Joined: Tue Dec 18, 2018 5:23 am
Post
by floki » Tue Jan 15, 2019 10:33 pm
yeah but when i'm applying my configurations in the UI, I always get this message "The apply command hasn't started yet. The instance may not be online or is unreachable."
I don't know the reason, is there a log file generated when applying a config?
Thanks a lot
scottwilkerson
DevOps Engineer
Posts: 19396 Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:
Post
by scottwilkerson » Wed Jan 16, 2019 3:55 pm
floki wrote: "The apply command hasn't started yet. The instance may not be online or is unreachable."
Is this a multi-instance cluster?
floki wrote: I don't know the reason, is there a log file generated when applying a config?
There should be logs here when you click apply config
Code: Select all
tail -f /usr/local/nagioslogserver/var/jobs.log
floki
Posts: 65 Joined: Tue Dec 18, 2018 5:23 am
Post
by floki » Wed Jan 16, 2019 8:35 pm
Its a single instance Nagios log server
the only log in job.log is this:
Code: Select all
Running command run_alerts with args ' ' for job id: run_all_alerts
SUCCESS
But still can't apply config through UI
scottwilkerson
DevOps Engineer
Posts: 19396 Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:
Post
by scottwilkerson » Thu Jan 17, 2019 8:36 am
Hmm, this sounds like something is stuck.
Can you go to Admin -> Command Subsystem
click "Reset All Jobs"
click OK on the dialog box
Then attempt to Apply Configuration again.
floki
Posts: 65 Joined: Tue Dec 18, 2018 5:23 am
Post
by floki » Fri Jan 18, 2019 1:04 am
Was able to reset all the jobs but still can't apply configuration through UI
still got this error in UI:
Code: Select all
The instance is likely offline, please check and try again.
scottwilkerson
DevOps Engineer
Posts: 19396 Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:
Post
by scottwilkerson » Fri Jan 18, 2019 1:27 pm
If you go to Admin -> Command Subsystem are the times updating on all of the items?