Upgrading from 20160418 - database is locked

[Tony Nelson]

This morning I tried to upgrade my server. After clicking the upgrade button, I stepped away from my desk and when I got back the upgrade status window was gone, but the server had not rebooted.

Not knowing what else to do, I rebooted it, and thankfully it booted just fine. I did notice some odd errors as it booted though.

May 25 07:54:22 va-nas alert.py: [system.alert:246] Alert module '<replication_status.ReplicationStatusAlert object at 0x80b88c950>' failed: database is locked
May 25 07:54:28 va-nas alert.py: [system.alert:246] Alert module '<samba4.Samba4Alert object at 0x80b88c9d0>' failed: database is locked
May 25 07:54:33 va-nas alert.py: [system.alert:246] Alert module '<smartdstatus.SMARTDAlert object at 0x80b895190>' failed: database is locked
May 25 07:54:38 va-nas alert.py: [system.alert:246] Alert module '<update_check.UpdateCheckAlert object at 0x80d0c8e90>' failed: database is locked

I tried the update again, and watched. The when the popup disappeared, an error displayed in red at the top of the screen that said it was unable to write something because the database is locked.

I considered rebooting again, but I decided to check my boot volume status first, and I see this: http://take.ms/t297T

When I last rebooted, the only entry I saw in grub was for 20160418, so I'm concerned if I reboot, it's going to fail.

I did just save a config, so if all goes south I suppose I can just do a fresh install and import my config, but I'd rather avoid that if possible.

Thanks in advance.
Tony

 

[dlavigne]

The fix for that error is scheduled for the next update: https://bugs.freenas.org/issues/15461.

 

[Tony Nelson]

In my googling I did find that but I wasn't sure if i was seeing the same error.

Am I safe to reboot?

Thanks again for your help.

 

[dlavigne]

Should be, please let us know if it was more painful than that...

 

[Tony Nelson]

Rebooted just fine. Did notice one odd thing, the console indicated I could access the UI using the IP assigned to the server, and the IP assigned to a bacula-fd jail. I only have one IP configured in interfaces:

http://take.ms/lDAyu

The other is definitely on the jail:

http://take.ms/yt0TE

And I can indeed access the UI on either IP.

It's not a problem for me b/c bacula doesn't use any of those ports, just thought I should mention it.

I'll wait for the next patch and let everyone know how that goes when it is released.