Now Available: pfSense® CE 2.8.1-RELEASE

randombits

I've a couple of random crash restarts since the update and this is the report of the last one.

Crash report begins.  Anonymous machine information:

amd64
15.0-CURRENT
FreeBSD 15.0-CURRENT #21 RELENG_2_8_1-n256095-47c932dcc0e9: Thu Aug 28 16:27:48 UTC 2025     root@pfsense-build-release-amd64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSense-CE-snapshots-2_8_1-main/obj/amd64/AupY3aTL/var/jenkins/workspace/pfSense-CE-

Crash report details:

PHP Errors:
[06-Sep-2025 01:06:00 Europe/London] PHP Fatal error:  Uncaught TypeError: posix_kill(): Argument #1 ($process_id) must be of type int, string given in /etc/inc/openvpn.inc:1552
Stack trace:
#0 /etc/inc/openvpn.inc(1552): posix_kill()
#1 /etc/inc/openvpn.inc(1575): openvpn_stop_process()
#2 /etc/inc/openvpn.inc(2494): openvpn_restart()
#3 /etc/inc/service-utils.inc(774): openvpn_restart_by_vpnid()
#4 /usr/local/pkg/servicewatchdog.inc(96): service_control_start()
#5 /usr/local/pkg/servicewatchdog_cron.php(30): servicewatchdog_check_services()
#6 {main}
  thrown in /etc/inc/openvpn.inc on line 1552



No FreeBSD crash data found.

fireodo

@randombits said in Now Available: pfSense CE 2.8.1-RELEASE:

Hi, as many posters have told this

servicewatchdog

is not a good Idea - watchdog is a "dumb" tool that creates more trouble than it resolves.

Another thing is - take a look at openvpn.inc on line 1552 to see whats there.
To the rest may a Specialist take a look.

My 2 cents,
fireodo

nimrod

Performed dirty upgrade from 2.8.1 RC to 2.8.1-RELEASE with zero issues.

randombits

@fireodo
Line 1552

		posix_kill($pid, SIGTERM);

And in some context

function openvpn_stop_process($mode, $settings) {
	global $g;

	$mode_id = openvpn_name($mode, $settings, 'generic');
	$pfile = g_get('varrun_path')."/openvpn_{$mode_id}.pid";
	if (file_exists($pfile)) {

		/* read the pid file */
		$pid = rtrim(file_get_contents($pfile));
		unlink($pfile);
		syslog(LOG_INFO, "OpenVPN terminate old pid: {$pid}");

		/* send a term signal to the process */
		posix_kill($pid, SIGTERM);

		/* wait until the process exits, or timeout and kill it */
		$i = 0;
		while (posix_kill($pid, 0)) {
			usleep(250000);
			if ($i > 10) {
				log_error(sprintf(gettext('OpenVPN ID %1$s PID %2$s still running, killing.'), $mode_id, $pid));
				posix_kill($pid, SIGKILL);
				usleep(500000);
			}
			$i++;
		}
	}
}

I'll stop the watchdog for the time being, it's never been a problem before.

fireodo

@randombits said in Now Available: pfSense CE 2.8.1-RELEASE:

I'll stop the watchdog for the time being, it's never been a problem before.

As I read the code (with my humble knowledge) the killing of the openvpn process was konflicting with watchdogtrying to restart the process (that was dead in his eyes). IMHO

randombits

@fireodo
It appears something like that, I've removed the Watchdog anyway and I'll see how it goes.

sandrinho1976

Any news for the Zabbix Proxy 7 package?

sokeada

@sandrinho1976 said in Now Available: pfSense CE 2.8.1-RELEASE:

Any news for the Zabbix Proxy 7 package?

Is this what you're looking for?

Machine22

Hey Mates, Just completed an upgrade to 2.8.1 from 2.8.0 all is working fine, no crushes despite ignoring the instructions to first remove all packages before doing the upgrade.
I went with my way, and all is perfect. If you haven't please do the necessary.
Africa is up-to-date.............

nimrod

This post is deleted!

Wylbur

Has anyone updated from CE 2.7.2 to 2.8.1?

I'm asking because the upgrade to 2.8.0 for me failed and recovery required re-installing 2.7.1 (ISO), and then upgrade to 2.7.2 (which I've been running for a while now).

Since I have two systems, I can upgrade the one and keep the other as a backup.... I just dislike going back through manually putting in the various IP pools and static addresses for my network.

Regards,
Wylbur

Patch

@Wylbur worked fine form me
I suspect the easiest is to

backup your pfsense configuration
Connect your backup pfsense routers want to your main units lan (so you can crash the backup unit and your internet continues to function
Download pfsense iso v2.70 v2.71 v2.72 from https://atxfiles.netgate.com/mirror/downloads/
download the free pfsense installer (internet connection during install required) from https://shop.netgate.com/products/netgate-installer
Try installing various versions of pfsense to confirm which are compatable with your hardware
restore your configuration to your preferred working pfsense version

Patch

@Wylbur worked fine form me
I suspect the easiest for you is to

backup your pfsense configuration
Connect your backup pfsense router WAN to your main units LAN (so you can crash the backup unit and your internet continues to function)
Download pfsense iso v2.70 v2.71 v2.72 from https://atxfiles.netgate.com/mirror/downloads/
download the free pfsense installer (internet connection during install required) from https://shop.netgate.com/products/netgate-installer
Try installing various versions of pfsense to confirm which are compatible with your hardware
restore your configuration to your preferred working pfsense version

(re-entered as editing prior posts is not working atm)

Wylbur

@Patch Thanx. I'll find time to set up to do this. I just wanted to not be a guinea pig for this update. Last time it took me a few hours to re-install and configure both fire wal/gateway servers.