After 2.4 upgrade, console tools not working

widmark

Hello, updated a SG-2440 to 2.4 the other day. Noticed some weird behavior on the console. Tools like top is not working anymore. Example:

# top
top: sysctl(vm.stats.vm.v_laundry_count...) failed: No such file or directory
# vmstat
procs  memory       page                    disks     faults         cpu
r b w  avm   fre   flt  re  pi  po    fr   sr md0 md1   in    sy    cs us sy id
vmstat: sysctl(vm.stats.vm.v_pdshortfalls): No such file or directory

This is worrying, did something go wrong with the update?
The web interface is also very slow, takes 30 seconds to log on to the fw. Recommendations?

ivor

Maybe a hard drive issue. Try doing a clean install.

widmark

Yes, will probably be doing a clean install. Something is wrong<tm>. Firewall seems to be working, but I guess it might break any time.

Edit: I did try a pkg update -f and pkg upgrade -f
Those commands executed without issue, but after a reboot the problem persists.</tm>

widmark

The problem seems to be that all packages updated fine to 2.4, but not the kernel package. So no wonder top, systat etc didn't work. A wonder that it even booted I'd say, lucky me indeed :)

fw/root: uname -a
FreeBSD fw 10.3-RELEASE-p19 FreeBSD 10.3-RELEASE-p19 #0 bbfdb9a1d(RELENG_2_3_4): Wed May  3 16:12:24 CDT 2017     root@factory23-amd64-builder:/builder/factory-234/tmp/obj/builder/factory-234/tmp/FreeBSD-src/sys/pfSense  amd64

And:

fw/root: pkg-static version -vL=
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
libpdel-0.5.3_6                    ?   orphaned: devel/libpdel
pfSense-kernel-pfSense-2.3.4       <   needs updating (remote has 2.4.0)

After a:

[/root: pfSense-upgrade -d[/code]

And a reboot everything seems to be working! So if anyone else manage to mess up their update, this might help. 
...
I'm not sure what went wrong during the update, I think I messed up a temporary netconfig. Always check twice before pushing into production...  ::)

jayjanssen

THANK YOU – just got into this exact situation and your commands did the trick. Much appreciated.

creiss

Hey folks,

I am in the exact same situation:

/root: uname -a
FreeBSD cerberus 10.3-RELEASE-p19 FreeBSD 10.3-RELEASE-p19 #0 bbfdb9a1d(RELENG_2_3_4): Wed May  3 16:09:14 CDT 2017

But:

]/root: pfSense-upgrade -d
>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
>>> Locking package pkg... 
Locking pkg-1.10.1_1
Your packages are up to date
>>> Unlocking package pkg... 
Unlocking pkg-1.10.1_1

And:

]/root: pkg info | grep -i kernel
bwi-firmware-kmod-3.130.20     Broadcom AirForce IEEE 802.11 Firmware Kernel Module
pfSense-kernel-pfSense-2.4.2_1 pfSense kernel (pfSense)

]/root: pkg-static version -vL=
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.

All went peachy– but the kernel. Any option on forcing the upgrade on that single component?

Cheers,
Christian.

creiss

D'oh.

I had a GEOM mirror that I deactivated prior to upgrade for emergency fallback. Turns out everything is fine; after syncing the right kernel was booted from the primary ssd. Oooookay.

Thanks :)

-Chris.