Upgrading via pkg breaks web UI upgradability

[datajunkie]

I was having some trouble upgrading via the web UI, so I did a pkg update/upgrade.  This seems to have broken the version checking in the web UI.  Which files should I check on to see why this has broken?

Also, it appears that the pkg update/upgrade now doesn't seem to find new snapshot versions.

[grandrivers]

try and reboot see if that fixes it ,
I haven't 100% nailed it but it acts like if there is no update needed it stays stuck in "no update" then reboot and it finds the update

[jimp]

I update both ways interchangeably on a set of systems I have, I haven't ever seen any problems like that.

I have on some rare occasions seen the pkg metadata get stuck and you have to run "pkg update -f" to nudge it back but it wasn't related to using the GUI.

[datajunkie]

I rebooted and it looks like it's still stuck not being able to either verify the current version installed and also the current snapshot version.  It does appear it's pulling other packages that need updating.

What does it look at to determine the current install/current repo?

It might be a file/permission that got whacked by something.  I didn't trace the UI code to figure out why it seems to be dying.

[datajunkie]

Here are the update packages as well.  Looks like it's properly messed up.

[jimp]

Looks like the pkg db is gone. Do you maybe have /var and/or /tmp in RAM disk? Or NanoBSD? Though NanoBSD should be fine, not sure the RAM disk bit has been as thoroughly tested.

[datajunkie]

Yep, I have /tmp and /var on RAMDisk

But now… how do I fix it?  I disabled the RAMDisk for now.

[datajunkie]

Just did a reinstall of the latest 2.3 and a restore of the config.  That looks like it worked.

[grandrivers]

mine says in gui  this is current 2.3.a.20151203.1050 ??


[grandrivers]

console 13 just dumps back to console

pkg update -f

does fix it but might be more than the avg user would have realized