PfBlockerNG

john_galt

I updated to yesterdays build.

The issue persists. 3+ hours after booting the GUI and serial console become unresponsive. Interesting to note that from a network point of view everything still works. WAN and LAN connectivity is normal.

VPN in does not work.

I monitored "/tmp/PHP_error.txt" until it became unresponsive but there were no entries.

Doug

BreeOge

To me it seems like some counter / process in the kernel with Pfblockerng is not releasing like it should. I have multiple boxes, with different loads, all same config. All of them will eventually lock up, but the time it takes is related to how much load is on the system.

If you try to SSH in when it locks you will notice you can not restart, start or do anything with any service, it will freeze. Also if you change directory the directory your in is never shown. FYI if you do SSH in, you will need to CTRL-Z to drop out of the menu execution as it will lock up as well.

john_galt

Well I got home from work and all appears to be working. GUI responsive, Serial console okay. VPN answered several times during the day. Still I think I'll follow others and reinstall and restore a recent config. Good time to switch to ZFS.

Thanks for listening.

Doug

BreeOge

@john_galt:

Well I got home from work and all appears to be working. GUI responsive, Serial console okay. VPN answered several times during the day. Still I think I'll follow others and reinstall and restore a recent config. Good time to switch to ZFS.

Thanks for listening.

Doug

Please keep us updated, I was wondering that myself if a fresh install to the newest release would fix issues. I know they had a major issue the other day and had to revert due to upgrade problems.

john_galt

Jinxed myself. 502 Bad Gateway nginx

Going to nurse it along until the weekend when I can get an 18 pack
and re-install.

Doug

BreeOge

https://redmine.pfsense.org/issues/7923

Thank you doktornotor

BreeOge

BBcan177

Just letting you know of another thread on this, trying to narrow the issue down. Wanted to make you aware of the other thread.

https://forum.pfsense.org/index.php?topic=137103.msg754247#new

Thank you sir.
BreeOge

john_galt

I made the edits in this post:

https://forum.pfsense.org/index.php?topic=137103.msg754338#msg754338

Now my pfSense isn't locking up as I had reported before.

Doug

john_galt

I have reinstalled 2.4.0-R with ZFS and restored my previous config file. I reset pfBlockerNG.
I will report any of the previous symptoms if the occur.

Doug

BBcan177

@BreeOge:

BBcan177

Just letting you know of another thread on this, trying to narrow the issue down. Wanted to make you aware of the other thread.

https://forum.pfsense.org/index.php?topic=137103.msg754247#new

Thank you sir.
BreeOge

Thanks for helping work thru the issue… I will work on converting that to use an SQLite3 database as recommended by jimp... I have just shied away in the past on using any SQL dbs...

For those that remove that section of code in the index.php, that will stop the widget DNSBL counters from populating, however all else will still function as-is...

StyleNZ

Hey, don't know what thread to post this on, but I am using a nanobsd install of pfsense and want to upgrade. I just want to know if pfblockerng is running okay with the new release before switching and if I do a backup of my config, and import, will that be ok without issues?

BreeOge

If you use the ZFS file system (If you do a full reload) It will work just fine. If you just upgrade or re-install with the UFS file system, then pfBlockerNG will lock up the system with a 502 bad gateway error.

https://forum.pfsense.org/index.php?topic=137103.0

In that thread there is a current work around, but like BBcan stated, if you do the work around your widget will not update properly.

BreeOge

belt9

I wanted to chime in here as I just updated from a month old RC to 2.4.0-RELEASE last night and ran into this problem today.

I haven't read through all of the many pages of the many threads that seem related to this issue (show how popular pfBNG is!), so maybe this has already been covered.

But I've seen several people state that this doesn't happen on ZFS - I have a raidz2 ZFS install, and this happened to me, just throwing that out there.

BreeOge

@belt9:

I wanted to chime in here as I just updated from a month old RC to 2.4.0-RELEASE last night and ran into this problem today.

I haven't read through all of the many pages of the many threads that seem related to this issue (show how popular pfBNG is!), so maybe this has already been covered.

But I've seen several people state that this doesn't happen on ZFS - I have a raidz2 ZFS install, and this happened to me, just throwing that out there.

That is good to know. Thank you for the report. BBcan177 is currently updating it to use SQLlite and this should fix any issues in the future. In the other thread there is a temp fix posted..

https://forum.pfsense.org/index.php?topic=137103.75

Thank you
BreeOge

Jailer

Looks like there is an update available in the package manager. Where can one find release notes for the new version? I'm wondering if this has the fix in it.

Cino

@Jailer:

Looks like there is an update available in the package manager. Where can one find release notes for the new version? I'm wondering if this has the fix in it.

https://github.com/pfsense/FreeBSD-ports/commit/fe101279ac400e2794fa27780f020c0bbe1c8caa
https://github.com/pfsense/FreeBSD-ports/pull/424

pfcode

@Cino:

@Jailer:

Looks like there is an update available in the package manager. Where can one find release notes for the new version? I'm wondering if this has the fix in it.

https://github.com/pfsense/FreeBSD-ports/commit/fe101279ac400e2794fa27780f020c0bbe1c8caa
https://github.com/pfsense/FreeBSD-ports/pull/424

Has it fix the issue??

strigona

@pfcode:

@Cino:

@Jailer:

Looks like there is an update available in the package manager. Where can one find release notes for the new version? I'm wondering if this has the fix in it.

https://github.com/pfsense/FreeBSD-ports/commit/fe101279ac400e2794fa27780f020c0bbe1c8caa
https://github.com/pfsense/FreeBSD-ports/pull/424

Has it fix the issue??

No. That update was initiated 18 days ago and is unrelated to the current issue.

BreeOge

We are currently testing a fix, if all goes well you should see an update soon.

BBcan177

I am going to make a PR shortly to hopefully fix this issue….

You could download these two files from my Github gist to get the updated code:

fetch -o /usr/local/www/pfblockerng/www/index.php "https://gist.githubusercontent.com/BBcan177/9f9c8e62b166cee07ad16cd4ff59103c/raw"

fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/7ff15715be0f02afdbe0a00c676aedce/raw"

You will need to restart the DNSBL Service for this to take effect.

A reboot is not required, but would be recommended.