Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - jwestan

#1
Hi All,

Having an error with Telegraf writing to my Influx DB.  It was working several point versions ago, currently on 20.1.5.  I have tried uninstalling/reinstalling the plug in and deleting the telegraf.conf file.

This is the error that keeps repeating.
2020-04-26T14:23:55   E! [agent] Error writing to outputs.influxdb: could not write any address
2020-04-26T14:23:55   E! [outputs.influxdb] When writing to [http://192.168.1.115:8086]: Post "http://192.168.1.115:8086/write?consistency=any&db=opnsense": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Anyone have any ideas on what I can try?

thanks,
#2
My user had to have a cert and then it showed up for the user to download their client export.  I think previously you were able to just download the client export and was not based on user.
#3
Try changing the destination to "This Firewall", that is how I have mine setup and it is working.
#4
I guess for the i386 intel there is no Telegraf package available, not sure what I was using before 19.7.1.
#5
Hi All,

After doing a fresh install of 19.7.1 I don't have telegraf available as a plugin.

My previous version of opnsense had the plugin.

Any ideas?

thanks,
#6
Good Day All,

In the latest version 19.7.1 in VPN>OpenVPN>Client Export there is not a button to actually export the data when I select "File only".

Am I missing something?

Thanks,
#7
General Discussion / Re: Redis/Notpng reset
January 08, 2019, 07:34:01 PM
I was able to fix my issue by deleting the Redis folder referenced in another forum post.
#8
General Discussion / Re: Redis/Notpng reset
January 07, 2019, 05:19:40 PM
I am having this same issue.  I tried uninstalling and reinstalling Redis, do not have a password configured but am seeing this in the system logs.

Any suggestions on a fix?

Thanks.

Jan 7 07:43:47   redis[74835]: Internal error in RDB reading function at rdb.c:1666 -> Unexpected EOF reading RDB file
Jan 7 07:43:47   redis[74835]: Short read or OOM loading DB. Unrecoverable error, aborting now.
Jan 7 07:43:47   redis[74835]: Server initialized
Jan 7 07:43:47   redis-server: Configuration loaded
Jan 7 07:43:47   redis-server: Redis version=4.0.11, bits=64, commit=00000000, modified=0, pid=74803, just started
Jan 7 07:43:47   redis-server: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
#9
Hi All,

I am trying to setup the OPNsense ntopng plugin as a data source for Grafana but Grafana is unable to connect to my ntopng instance. 

I have followed the setup instructions online (https://grafana.com/plugins/ntop-ntopng-datasource) and it seems straight forward but maybe I am missing something?
I am using this as the datasource url http://192.168.1.1:3000/lua/modules/grafana and have a user setup that I am using.

My Grafana instance is on a local windows computer.

Has anyone been successful in setting this up?

Thanks
#10
@opnsrcfw thanks for the reply.  I am in the process of starting over with my OPNSense box.  I was starting to see some funny stuff going on, plus I had a bunch of plugins that I was trying that I didn't really need anymore.  Thought a clean slate was the way to go.
#11
I am still unable to get unbound to start and am still receiving the error about unable to set up local zones.

Can someone tell me how to reset the unbound config file or some other method to reset unbound?  I have removed the override I set up.  Not sure what is causing that error to be generated, if it is a configuration in another OPNsense applet?

Thanks
#12
Hi All,

I recently upgraded from 18.1.13 to 18.7.1_3 and the upgrade went well.  However overnight, unbound stopped working with the following errors.  The device at the ip listed is a wireless printer. To get the wan connection resolving again I disabled unbound and enabled dnsmasq dns.

Not sure if it is a really big deal using dnsmasq compared to unbound in a small home network but would like to resolve the issue and use unbound again.  I probably configured unbound based on a guide I was following setting up opnsense.

Aug 18 05:32:23   unbound: [36062:0] fatal error: Could not set up local zones
Aug 18 05:32:23   unbound: [36062:0] error: Bad local-data RR .(mydomainname) IN A 192.168.1.188
Aug 18 05:32:23   unbound: [36062:0] error: error parsing local-data at 2 '.(mydomainname) IN A 192.168.1.188'