9.3 - update 20160414 - SAMBA Fix - Failed to write core file error

[depasseg]

I updated yesterday to FreeNAS-9.3-STABLE-201604120241 which was fine,
And then this morning I saw the SAMBA update was available. So I applied it to 2 systems and got this string of errors, rending the boxes useless. Has anyone else applied this on 9.3 and experienced the same problem?

"Failed to write core file for process python2.7 (error 14)"

I rolled back the boot environment and I'm good for now.

 

[dlavigne]

It's definitely worth reporting at bugs.freenas.org. Does it let you get to the GUI (or the console menu) at all? If it lets you get to the console menu, you could drop to shell and run freenas-debug to get a debug to include with the report.

 

[depasseg]

No, CLI, SSH, and webgui were all inaccessible. I'll open a bug

 

[depasseg]

https://bugs.freenas.org/issues/14706

 

[JoelN]

I assume you mean 0556 in description not 0566. Thanks for the report.

 

[depasseg]

Good point yes, 0556, but I can't change it from my phone.

 

[jhigham]

Same issue after applying update today. Same solution - revert to older version.

 

[sef]

Okay, this issue was discovered yesterday, and has been rectified. By requiring a reboot, I am sad to say.

If you've already installed, then you should:

1. Boot to a previous boot environment.
2. Make that boot environment the "active" one, using either the UI, or by "beadm activate <name>". (Use "beadm list" to find the name; it'll be the last column.)
3. Delete the bad update ("beadm destroy -F FreeNAS-9.3-STABLE-201604140556")
4. Out of paranoia, clear out the update cache ("rm -rf /var/db/system/update")
5. Update the system. Either via CLI ("freenas-update check ; freenas-update update; shutdown -r now"), or using the UI.

We may have a post mortem at some point.

 

[sef]

Or, of course, now there's a new SU, so you can just boot to a previous BE, and then update.

 

[depasseg]

Thanks sef. I did boot to a previous BE and then saw jkh's post this morning saying that we could apply the new update which I performed, so I didn't do steps 3 or 4. I'm guessing at this point step 4 is irrelevant, but step 3 has me a little confused.

I'm confused, because there are more boot environments than I expected, and the names and dates/times seem out of whack. I'm assuming I can delete201604120241, and201604140556.