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 - pilotboy72

#31
Went from 19.7.3 to 19.7.4_1.
#32
Hello,

Since updating to 19.7.4_1, I'm seeing this message about every minute in the logs:

vnstatd[48386]: Error: Database load failed even when using backup (Permission denied). Aborting.

I'm also not getting any Netflow data at all, and the flowd_aggregate service will not start, and I don't see any messages in the General logs for this.

Any ideas?

Brian
#33
Development and Code Review / Re: Widget Example
July 27, 2019, 06:44:47 PM
Appreciate the pointers @fabian.
#34
Development and Code Review / Widget Example
July 26, 2019, 08:24:39 PM
Hi,

I'm interested in developing some widgets to use on the Lobby page.  Are there any examples from which I can draw to get started?

Brian
#35
I'm getting an error on the Sensor configuration page.  The help text for the "Remote Port" value says to leave it blank when the sensor and server are on the same machine, but the UI is insisting on a value for it.
#36
Hello,

I have created two DHCP address pools specifically for some of my IoT devices for monitoring purposes.  I have added the correct partial MAC addresses for each of the pools.

For the first address pool, all of the devices with the partial MAC address are correctly being assigned to that pool (where there is a single partial MAC).  The second pool has 4 partial MAC addresses specified in MAC access control (allow) and only a handful of the devices are correct assigned to that pool -- the rest are maintaining their addresses in the main pool.

Looking at the DHCP logs, I see requests from these devices for an "unknown" lease.  However, I don't see any response in logs for this.  This example is all I see:

dhcpd: DHCPREQUEST for 192.168.1.188 (192.168.1.1) from 00:07:a6:xx:xx:xx via igb1: unknown lease 192.168.1.188

The correct pool range for partial MAC 00:07:a6 should be 192.168.1.200 to 192.168.1.232.

Not sure where to go next to try to debug my config.  Any ideas?
#37
19.1 Legacy Series / Re: UPS Status Empty
May 07, 2019, 05:01:16 PM
Ok, cracked the NUT (pun intended).

I looked at the listen configuration and saw that it was listening on my LAN address only.  I added 127.0.0.1 as a listen address and the diagnostics are showing up.
#38
19.1 Legacy Series / Re: UPS Status Empty
May 07, 2019, 04:59:00 PM
TrippLite UPS connected via USB.

It has to be working somehow since other devices on the network can see the status of the UPS.
#39
19.1 Legacy Series / Re: UPS Status Empty
May 07, 2019, 04:43:17 PM
There are a lot of pending API calls to /api/nut/diagnostics/upsstatus.  Looks like these calls never return anything.  Also tried using cURL with the same result -- no response from the server after 30 seconds.
#40
19.1 Legacy Series / [solved] UPS Status Empty
May 07, 2019, 03:56:09 PM
Hello,

I have a UPS attached to my OPNsense firewall and the NUT service seems to be working fine.  I have this networked to other devices as well and they are able to read the status of the UPS, time remaining, and the other metrics that NUT provides.  However, on the Diagnostics screen there is no information under UPS status.  Is this normal?

NOTE:  This is not unique to 19.1.7 -- have observed this behavior since installing OPNsense with version 19.1.1.

Brian