Lost access to web UI after badlock update

[FlippantGeece]

Today I was trying to update my system via the web UI, and it hung at around 50%

I tried refreshing but got the nginx "An error occured" page

I then rebooted the system, but the web UI wasn't coming back

I checked the KVM and this message is now being printed over and over "Freenas kernel: Failed to write core file for process python2.7 (error 14)"

I still have a working shell via which I can access the system

My freenas version is FreeBSD 9.3-RELEASE-p31 (FREENAS.amd64) #0 r288272+ecf8c25

The mobo is a supermicro Super X10DRH-iT

dmesg output is the same as what I see via KVM, these lines over and over

Code:

pid 9154 (python2.7), uid 0: exited on signal 11
Failed to write core file for process python2.7 (error 14)
pid 9155 (python2.7), uid 0: exited on signal 11
Failed to write core file for process python2.7 (error 14)
pid 9156 (python2.7), uid 0: exited on signal 11
Failed to write core file for process python2.7 (error 14)
pid 9157 (python2.7), uid 0: exited on signal 11
Failed to write core file for process python2.7 (error 14)
pid 9158 (python2.7), uid 0: exited on signal 11
Failed to write core file for process python2.7 (error 14)
pid 9159 (python2.7), uid 0: exited on signal 11

e: My main pool also doesn't show anymore if i do a 'zpool list', I just get this output

Code:

NAME           SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
freenas-boot  29.8G  2.12G  27.6G         -      -     7%  1.00x  ONLINE  -

 

[dlavigne]

Looks like a trend: https://forums.freenas.org/index.ph...d-to-write-core-file-error.42755/#post-278598

Which version did you upgrade from?

 

[depasseg]

I upgraded from 20160412.
My bug report: https://bugs.freenas.org/issues/14706

 

[depasseg]

I should mention that I just rebooted and selected the previous boot environment.

 

[FlippantGeece]

My last update was tuesday evening, so I believe i was on 20160412 as well

 

[depasseg]

Yep, same as me.

 

[FlippantGeece]

I should mention that I just rebooted and selected the previous boot environment.

Thanks, this worked for me too, 201604120241 boots fine

 

[jkh]

Today I was trying to update my system via the web UI, and it hung at around 50%

I tried refreshing but got the nginx "An error occured" page

I then rebooted the system, but the web UI wasn't coming back

Sorry folks, this was due to a temporary glitch with the rebootless SMB update. We've fixed this one in-place and also rolled another "full reboot" update to avoid the problem for now (this glitch only happens when we roll non-rebooting updates right now, and we're working on that). If you've already applied the previous SSU and gotten stuck this way, simply reboot into the previous boot environment and try to install the subsequent update which has a slightly different changelog - it will identify itself as the Badlock fix that does reboot - this one is totally safe.

For 9.10, the update was always rebooting so we didn't it this problem.