Nagios Support Forum

Hi Troy,

Please let me know if you need any additional information regarding this ongoing issue for resolution. I look forward to hearing from you and thanks in advance.

Best Regards,

Kaushal

Hi Troy,

When I disable the livestatus block in /opt/nagflux/config.gcfg, I get https://paste.centos.org/view/16b80f5a and when I enable livestatus block in /opt/nagflux/config.gcfg I am facing this issue https://paste.centos.org/view/c965160c

Any help will be highly appreciated.

Best Regards,

Kaushal

kaushalshriyan wrote:Hi Troy,

#systemctl status nagflux.service

● nagflux.service - A connector which transforms performancedata from Nagios/Icinga(2)/Naemon to InfluxDB/Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/nagflux.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Fri 2020-01-31 17:10:48 UTC; 3s ago
Docs: https://github.com/Griesbacher/nagflux
Process: 10845 ExecStart=/opt/nagflux/nagflux -configPath /opt/nagflux/config.gcfg (code=exited, status=2)
Main PID: 10845 (code=exited, status=2)

Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal nagflux[10845]: main.main()
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal nagflux[10845]: /root/gorepo/src/github.com/griesbacher/nagflux/main.go:68 +0x22e
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: Unit nagflux.service entered failed state.
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: nagflux.service failed.
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: nagflux.service holdoff time over, scheduling restart.
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: Stopped A connector which transforms performancedata from Nagios/Icinga(2)/Naemon to InfluxDB/Elasticsearch.
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: start request repeated too quickly for nagflux.service
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: Failed to start A connector which transforms performancedata from Nagios/Icinga(2)/Naemon to InfluxDB/Elasticsearch.
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: Unit nagflux.service entered failed state.
Jan 31 17:10:48 ip-172-31-0-145.ap-south-1.compute.internal systemd[1]: nagflux.service failed.

Please suggest further and correct me if I am missing anything. I look forward to hearing from you. Thanks in Advance.

Best Regards,

Kaushal

It appears your nagflux service is stopping for some reason. I suggest you contact the Influx creators for help on this. While we have provided a guide to get it working we are not always able to provide support due to the environment complexities that arrive.

We do not provide any support for Livestatus, this is not created by us and you need to contact their support for help with this issue.

Hi Troy,

I could figure out the issue and it seems we need to replace "fill(previous)" instead of "fill(null)" in the SQL query to read data from the InfluxDB time-series database.

I am attaching chart one with "fill(null)" in the SQL query
I am attaching chart one with "fill(previous)" in the SQL query
The issue is that Histou which is a Grafana add-on that creates graphs specifically for the Nagios performance data generates dashboards without that behavior. Can it be done using histou? More Info regarding histou:- https://github.com/Griesbacher/histou. I look forward to hearing from you. Much appreciated for your help and thanks in advance.

Best Regards,

Kaushal

Any help with Histou would have to be asked via the github page for that project. I've not spent much time with it except for just installing it and it worked but that was about 18 months ago and things can change and break.

Hi Troy,

I have already raised an issue in Github https://github.com/Griesbacher/histou/issues/36. I tried reaching out to Philip Griesbacher on philip.griesbacher@consol.de and I am getting Address not found.
Is there a way to reach out to Philip Griesbacher? I look forward to hearing from you. Much appreciated for your help and thanks in advance.

Best Regards,

Kaushal

Hi Troy,

Checking in again if you had a chance to look at my earlier post? I look forward to hearing from you. Much appreciated for your help and thanks in advance.

Best Regards,

Kaushal

A issue within GitHub is the best communication method. Keep in mind that open source projects are done by people in their spare time, the time it takes for someone to respond depends on the amount of free time they have in their lives.

Thanks Troy for your reply and appreciate your help.

kaushalshriyan wrote:Thanks Troy for your reply and appreciate your help.

Best of luck!

Locking thread