Update 2.1.5 -> 2.2.2 leads to errors
I was updating a virtual pfS and unfortunately I was to lazy to start a snapshot..
After the update there's garbled letters on dashboard|services status|openvpn and the OpenVPN choice under VPN cannot be used, a blank page with this is the only thing that comes up:
"Fatal error: Can't use function return value in write context in /usr/local/www/vpn_openvpn_server.php on line 805 "
It is not possible to enter the OpenVPN section at all that is.
The error report that pfS wants to send contains:
[25-Apr-2015 21:45:29 Europe/Stockholm] PHP Fatal error: Can't use function return value in write context in /usr/local/www/vpn_openvpn_server.php on line 805
Did the VM successfully reboot after the update?
What FreeBSD kernel version is shown on the dashboard?
Did you accidentally switch to a 64bit version?
Those are things that can cause that error. Running the old kernel in a new filesystem due to reboot failure.
When did you run the update?
I have done some more tests also on another VM and have now been able to update both and the error is gone.
It seems that the VMs are not being rebooted correctly, when looking at the console the menu just sits there and if you hit enter a logon prompt comes up that I wasn't able to logon to for some reason.
I tried to reset the VM but that didn't work at first but did so when doing it from the Inventory menu (ESXi).
Then after another boot the VM finally seems updated.
There seems to be something broken in the update/boot procedure.
Both VMs behaved the same way, did update through option 13 in console, auto URL.
built on Mon Apr 13 20:10:33 CDT 2015
The most common cause of not rebooting is accidentally switching from 32 to 64bit or vice versa. You were running 32bit before I assume?
What hypervisor are you using?
Well as I said I used the built-in auto update via console/URL so I didn't fetch the wrong file manually.
These two VMs have been 32bit all along, have another that's newly installed that's 64 though.
Using ESXi 5.5.x but the VMs may have been running on another ESXi (5.1.x) earlier.
This seems related:
But I did not enter the command given here but simply rebooted/reset the VM.
Yeah, that was my first thought but that's been fixed since 21st Apr so if you only updated yesterday you should not be running into that.