pfSense

Err, "only via IPv4". Whatever.

Also, OpenVPN is completely no-op, producing just segfaults.

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

Pull it :|

All the crashes here seem to be OpenVPN related.

Calling openvpn_resync_all() causes php-cgi to crash on boot, which unfortunately screws the rest of network setup.

Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring WAN interface...done.
Configuring LAN interface...done.
Configuring MGMT interface...done.
Configuring WLAN interface...done.
Configuring HEIPV6 interface...done.
Configuring CARP settings...done.
Syncing OpenVPN settings...Segmentation fault (core dumped)
Starting CRON... done.

Going to VPN - OpenVPN menu causes php-fpm to segfault.

Sep 24 21:12:15 gw gw.example.com nginx: 2016/09/24 21:12:15 [error] 24339#100138: *6627 upstream prematurely closed connection while reading response header from upstream, client: 192.0.2.3, server: , request: "GET /vpn_openvpn_server.php?act=edit&id=0 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "gw.example.com" 
Sep 24 21:12:15 gw kernel: pid 19542 (php-fpm), uid 0: exited on signal 11 (core dumped)

Fixed, thanks.

As a follow up - it appears that after openvpn_resync_all(), nothing else below that function call could run from the /etc/rc.bootup script -- since almost everything is plopped into that one script that crashed php-cgi.

Shouldn't this thing be a whole lot more robust/failsafe? As in, e.g. not sticking almost the entire boot process into one script which - when crashed somewhere at the top of the calls stack, renders the system very much useless? So, the core of the issue doesn't seem to be resolved at all, can happen anytime again, with amount of breakage depending on how early in the script it happens.

Do you want a separate bug for that?

Kill Bill wrote:

Going to VPN - OpenVPN menu causes php-fpm to segfault.

I'm not using OpenVPN, nor accessing the menu, but I still get a segfault that looks similar to what you showed. I've filed #7819

Greg Toombs wrote:

I'm not using OpenVPN, nor accessing the menu, but I still get a segfault that looks similar to what you showed. I've filed #7819

Yeah this old bug should be left well alone, completely different code base.