If i enable Ram disks i have a "Unable to check for updates" message in dashboard
-
I also had this problem when my RAM disk was enabled.
When I turned off the RAM disk, it was then immediately able to check and perform the upgrade to latest RC (built on Thu Mar 31 23:48:37 CDT 2016 ).
After rebooting it's back to complaining it is unable to check for updates with or without the RAM disk enabled.
Before I enabled the RAM disk it was updating fine, I have been running the v2.3 beta for over a month updating regularly.
-
I was running 2.2.6 with RAM disks when RC was released. Disabled RAM disks, rebooted, upgraded to 2.3 RC, enabled RAM disks again.
Update works fine for me with RAM disks but I lost my old RRD data.
-
Little offtopic, but with Ram-disk enabled system, pfSense did not come back after update to new snapshot. Error messages about read-only filesystem. Solved by reinstall of fresh pfSense installation.
-
@pLu:
I was running 2.2.6 with RAM disks when RC was released. Disabled RAM disks, rebooted, upgraded to 2.3 RC, enabled RAM disks again.
I did not reboot immediately after disabling the RAM disk, and upgraded right afterwards because the option then became available. :(
-
https://redmine.pfsense.org/issues/6068
-
@cmb:
https://redmine.pfsense.org/issues/6068
Thanks. I see this is already fixed, very nice.
How do we patch if already affected by this? Is there some way to force check/apply updates via the CLI?
-
If you just reboot, it should work post-reboot.
-
@cmb:
If you just reboot, it should work post-reboot.
I have rebooted many times, and the problem persists even without having the RAM disk set.
-
I have rebooted many times, and the problem persists even without having the RAM disk set.
Had the same problem, the workaround from https://forum.pfsense.org/index.php?topic=107665.msg600840#msg600840 did fix it for me.
But I only executed:/usr/sbin/pkg update -f /usr/sbin/pkg install -yf pkg pfSense pfSense-kernel-pfSense pfSense-base pfSense-default-config -
Had the same problem, the workaround from https://forum.pfsense.org/index.php?topic=107665.msg600840#msg600840 did fix it for me
Thanks a lot for the link, your abbreviated version of the fix is what I used and it worked perfectly.