pfblockerng crash report

Bob.Dig

Me, too...

Crash report begins.  Anonymous machine information:

amd64
12.2-STABLE
FreeBSD 12.2-STABLE d48fb226319(devel-12) pfSense

Crash report details:

PHP Errors:
[02-Mar-2021 11:01:17 Europe/Berlin] PHP Fatal error:  Uncaught Error: Class 'Net_IPv6' not found in /etc/inc/util.inc:680
Stack trace:
#0 /etc/inc/util.inc(657): is_ipaddrv6('i.mxplayer.j2in...')
#1 /usr/local/www/pfblockerng/www/index.php(59): is_ipaddr('i.mxplayer.j2in...')
#2 {main}
  thrown in /etc/inc/util.inc on line 680
[02-Mar-2021 11:11:18 Europe/Berlin] PHP Fatal error:  Uncaught Error: Class 'Net_IPv6' not found in /etc/inc/util.inc:680
Stack trace:
#0 /etc/inc/util.inc(657): is_ipaddrv6('i.mxplayer.j2in...')
#1 /usr/local/www/pfblockerng/www/index.php(59): is_ipaddr('i.mxplayer.j2in...')
#2 {main}
  thrown in /etc/inc/util.inc on line 680



No FreeBSD crash data found.

Thankfully, that reminded me to block some apps on my phone.

3.0.0_13, IPv6 DNSBL enabled, unbound mode

BBcan177

Fixed in v3.0.0_14

chudak

@bbcan177 said in pfblockerng crash report:

Fixed in v3.0.0_14

13 is not a good number anyway :)

fireodo

@bbcan177 said in pfblockerng crash report:

Fixed in v3.0.0_14

Is the increasing number of "tail_pfb" processes also fixed?

Thanks again!

RonpfS

@fireodo Yes in 3.0.0_14

Re-add rc_stop as good measure to ensure services are stopped

fireodo

@ronpfs said in pfblockerng crash report:

rc_stop

Thanks!

Regards,
fireodo

fireodo

@ronpfs said in pfblockerng crash report:

@fireodo Yes in 3.0.0_14

Re-add rc_stop as good measure to ensure services are stopped

It seems that is not working because this morning:

12645 - S 0:01.36 /usr/bin/tail_pfb -n0 -F /var/log/filter.log
15089 - S 0:01.38 /usr/bin/tail_pfb -n0 -F /var/log/filter.log
41182 - S 0:03.72 /usr/bin/tail_pfb -n0 -F /var/log/filter.log
42986 - S 0:00.00 sh -c ps ax | grep tail_pfb 2>&1
43101 - S 0:00.00 grep tail_pfb

This is pfBlockerNG-devel 3.0.0_14 and I have yesterday allready done:

rm /usr/local/etc/rc.d/pfb_filter.sh
pkill tail_pfb

and a force update after that.

Regards,
fireodo

fireodo

As a "quick and dirty" solution of the "tail_pfb" issue I added in the pfblockerng.inc this:

	# Terminate pfBlockerNG Firewall filter Daemon (clog) and filter Daemon, if found
	/usr/bin/logger -p daemon.info -t "\${filter_type}" "[pfBlockerNG] Firewall Filter Service stopped"
	/usr/bin/logger -p daemon.info -t php_pfb "[pfBlockerNG] filterlog daemon stopped"
	pidnum="\$(/bin/ps -wax | /usr/bin/grep '[c]log_pfb -f /var/log/filter.log\|[t]ail_pfb -n0 - F /var/log/filter.log\|[p]fblockerng.inc filterlog' | /usr/bin/awk '{print \$1}')"
	if [ ! -z "\${pidnum}" ]; then
		for i in \${pidnum}; do
			/bin/kill -9 "\${i}"
		done
pkill tail_pfb
	fi

After "done" I added the "pkill tail_pfb" and now everything is as it should and there is only one process "/usr/bin/tail_pfb -n0 -F /var/log/filter.log" active.

UPDATE: After a chat with bbcan he point me to a mistake I made - its a "space" before the "F" in the script above:
"[t]ail_pfb -n0 - F" should be "[t]ail_pfb -n0 -F"! Now everything runs like expected.

Regards,
fireodo

RonpfS

@fireodo The problem occurred when Unbound restart after WAN was toggling.

I stop Firewall service, that stopped all tail_pfb processes. Start Firewall service.

fireodo

@ronpfs said in pfblockerng crash report:

@fireodo The problem occurred when Unbound restart after WAN was toggling.

I stop Firewall service, that stopped all tail_pfb processes. Start Firewall service.

I have also toggled the WAN and there was no problem.