OpenVPN Not Accepting Connections

arrmo

OK, this is rather interesting. I have avoided the dashboard … and in doing os => no longer php-fpm crashing (for close to 24 hours now), and no issues with other services. It seems that something on the dashboard is causing php-fpm to crash, and in the process taking down all sorts of other services. This may be why others aren't seeing this - if you're not leaving the dashboard open, it doesn't seem to happen. I will go back to the dashboard in a bit, see if the failure occurs again.

BTW, unbound did restart overnight (it's running, no issue there) - is it supposed to restart regularly / on some schedule?

Thanks!

PiBa

The patch could be applied through systempatches package, after upgrade it will need to 'apply' again. (There is an checkbox to 'auto apply' them.)

What widgets do you have on the dashboard? For one i see the 'thermal_sensors.widget.php' in your error log. Could you remove that from the dashboard and try a day or two without it?

Steve_B

Yes - Determining which (if any) particular widget is causing the issue would be very helpful.

There is a "dashboard update period" setting on the "General" setup page. Does setting that to a larger value cause the failure to happen less often?

arrmo

Hi,

I think this is the culprit (NUT widget),
https://forum.pfsense.org/index.php?topic=111485.0

Not sure why a bad widget should cause php-fpm to crash, but I was running ~ 4.5 hours, no issue at all (with this widget removed). Add it back in, and within 3 minutes unbound restarted. Could be a coincidence, but seems unlikely. I'll keep running now without this one, let's see.

Thanks!

PiBa

The forum thread linked only talks about some webgui 'display issues' when the package got (re-)introduced.. Nothing about it crashing any processes or php in the background, that i read in it anyhow. (or you only provided it for reference as to what package your talking about.?)

Anyhow it could be that the NUT widget is the issue, once you know for sure the problem is gone without it..
Can you trigger the problem manually by visiting nut config page and possibly refreshing it a lot / fast?
What settings do you use in that package?

arrmo

Will keep poking - but first I want to make sure it's stable / staying up now (with this removed) … agreed? Just want to make sure I have a reasonable baseline first.

Thanks!

PiBa

Yes agreed, first make sure it stays stable with NUT widget removed

arrmo

Hi,

One thing that just occurred - that may be normal / expected, but given the issues before it was breaking when running … is unbound supposed to restart every 2 hours? I see in the log it seems to be (at least this last time, exactly 2 hours).

Thanks!

Hugovsky

How long do your dhcp leases last?

arrmo

24 hours.

arrmo

So far, so good - up 24 hours now, which is a recent record … ;). I do see some unbound restarts, but I'm guessing this is nothing new, I just wasn't looking for it before. Not sure why unbound is being restarted, but you can see it below. Leaving the system 24 hours more before messing with it.

clog /var/log/resolver.log | grep unbound | grep stopped
Jul 30 12:26:34 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 30 16:52:10 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 30 16:52:10 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 30 18:52:10 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 30 18:52:10 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 31 04:04:17 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 31 04:04:17 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 31 06:04:17 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).
Jul 31 06:04:17 pfSense unbound: [7522:0] info: service stopped (unbound 1.6.3).

Thanks!

arrmo

OK, found the smoking gun, finally … :). And I was wrong - got sidetracked by a couple items happening at the same time, but I put things back together very slowly. The widget is OK, the end culprit is the driver for my USB NIC. It's the axge driver, for the ASIX AX88179 chipset ... which is on the FreeBSD compatibility list, but seems to have issues with pfSense. There is actually an open ticket I found for it, https://redmine.pfsense.org/issues/4494

When I put this device back in place ... fire and ashes in < 15 min ... ;). I actually got a crash report (submitted that), and a spontaneous reboot. Removed the adapter, and things were smooth again. Not quite sure how to handle this one now, as it should be supported HW.

Thanks for all the debug help and pointers!

jimp

While USB NICs may be on the FreeBSD HCL and they may operate, none of them are known for their stability. They are best to be avoided at all costs. If you have a managed switch, setup and use VLANs instead of trying to rely on a USB NIC.

arrmo

Agreed, and already on that … ;). Just struggling a bit to put the pieces together there (setup wise). I have found a lot of partial solutions / info, nothing in one place all together.

Thanks!

arrmo

FYI, some very good info here,
https://blog.spirotot.com/2016/06/28/pfsense-vlans-with-one-nic-nuc-a-tp-link-tl-sg108e/

Perhaps capture this somewhere, so it's tucked away for folks? Just to make it easy for others.

Thanks!