Search • Nagios Support Forum

Where did you get this plugin from? Can you provide a URL or the raw script itself?

InfluxDB 2.0+ has a default username+password I believe: https://docs.influxdata.com/influxdb/v2.0/reference/release-notes/influxdb/#bug-fixes-4 Require user to set password during initial user onboarding. https://docs.influxdata.com/influxdb/v2.0/users/change-password/ If you're set on using Influx...

You're using the script provided by the vendor I assume?
https://www.hw-group.com/support/how-to ... wg-sms-gw3

Try passing -v for verbose instead of -q for quiet, that might provide some hints.

I haven't touched this code in ages, and it never really moved past the POC phase, but it's built on impacket which supports Kerberos: https://github.com/mcapra/nagios-check_wmi/blob/master/check_wmi.py Could try altering the authentication handler by just passing doKerberos=True https://github.com/...

So it seems like I may need to setup a chron job to run this script on a regular basis. You could also address this by reducing the cardinality -- add some filtering to the checkdrivesize module if you don't need size information for 100% of the drives that will ever exist on this system. My mind g...

I know nothing about this plugin or the hardware it's meant for, but I think --blacklist is the way to do this. See the "Blacklisting" section of the documentation:
https://labs.consol.de/nagios/check_hpasm/index.html

Perhaps something like this:

Code: Select all: --blacklist daacb

Nagios XI has a concept of scheduled reports, but I don't know of anything like this that would exist in the Nagios Core ecosystem.

I'm sure with some clever scripting you could hit avail.cgi with some parameters on a cron job and pipe the output into an email.

I'd suggest shooting an email to security@nagios.com.

https://www.nagios.com/products/security/

I think a simple disclaimer at the top of the docs to the effect of "don't do this in prod, it exposes your influxdb instance to anything with a network connection" would go a long way.

I'd have to see the full contents of at least the files mentioned to have a clue of what's going on:

Code: Select all: /etc/apache2/apache2.conf /etc/apache2/sites-enabled/pnp4nagios.conf

Was there particular documentation you were following to make this change?

I noticed that several of the servers are being queried over NRPE and referenced by their public IP address. Is this a security risk? It's not good practice to have any "monitoring stuff" be public facing, regardless of whether that's NRPE or NCPA or a Prometheus exporter or a Telegraf ag...

Search found 3722 matches

Re: CRITICAL 500 write failed (check_apache)

Re: Performance Graphs InfluxDB Nagflux issue

Re: calling phone via script

Re: check_wmi_plus and ntlm authentication

Re: check_wmi_plus.pl -checkdrivesize no historic perf data

Re: Skip checking the battery condition by check_hpasm

Re: Auto-Generation of Availability Reports

Re: Security Issue: Nagios Core - Performance Graphs Using I

Re: Error in Grant localhost Permission To PNP4Nagios Site

Re: NRPE safe over public IP