Fatal error with php-fpm

  • I have an error with php-fpm which apparently appeared out of the blue. I am running pfSense virtualized to secure some VMs in a proxmox environment. I have noticed that i couldn't reach any of the VMs, so i restarted pfSense. After a reboot i got this error:

    Wed Nov 28 11:52:21 2018 (443): Fatal Error Zend OPcache cannot allocate buffer for interned strings.
    fcgicli: Could not connect to server(/var/run/php-fpm.socket)

    This error also appears on nearly every option i can select in the CLI menu. Fortunately i could still spawn a shell. However, the pfSense seems to have no network connectivity. ifconfig shows the interfaces as active, but the WAN interface which should receive it's IP address via DHCP shows no IP address at all.

    So, currently i am stuck. I am not very used to BSD, but to network configuration in general. The troubleshooting documentation is not really covering my problem, so i was hoping you have an idea.

  • Netgate Administrator

    What pfSense version is that?

    If it's not current I would backup the config, reinstall to 2.4.4 and restore the config.

    I would guess there is some corrupt file causing that which might be resolvable by booting into single user mode and running fsck a few times but since it's a VM reinstalling is trivial.


  • Sorry to re-open an old topic, but I'm facing the same problem, and was able to reproduce: Fatal Error Zend OPcache cannot allocate buffer for interned strings.

    For me it's happening after I changed the VM memory size (vmWare Workstation v15). I'm using latest pfSense 2.4.4 Patch 3 out-of-the-box, just downloaded and installed with default options - ZFS, no disk encryption, no RAID.

    If I set the VM to 256MB, the system boots normally, I can use web configuration, etc.

    But if I power off and change the memory size to 2GB, it gives the error above, and the menus are all unusable. The only option that works is 8 - Shell. Going back to 256MB allows me to boot again.

    Screenshots here

    Interestingly, using 2.5.0-DEV branch (built Jul 24 21:30:13 EDT 2019) doesn't present the same problems. I can change the memory size back without any problems.

Log in to reply