Cannot list snapshots in GUI - Sorry, an error occurred

[sunshine931]

Code:

root@omega:/var/log # 
root@omega:/var/log # cat /etc/version 
FreeNAS-11.1-U4 (89e3d93bc)
root@omega:/var/log # 

Trying to manage my snapshots, and cannot do so via the GUI.

I have the following snapshots:

Code:

root@omega:/var/log # zfs list -t snapshot   
NAME													  USED  AVAIL  REFER  MOUNTPOINT
freenas-boot/ROOT/default@2018-04-24-22:39:26			7.30M	  -   836M  -
nebula/iocage/releases/11.1-RELEASE/root@owl			  112K	  -   836M  -
nebula/iocage/releases/11.1-RELEASE/root@build			112K	  -   836M  -
nebula/iocage/releases/11.1-RELEASE/root@burst			112K	  -   836M  -
nebula/iocage/releases/11.1-RELEASE/root@antpatrol		112K	  -   836M  -
nebula/jails/.warden-template-pluginjail-10.3-x64@clean  2.15M	  -   434M  -

In multiple browsers, I get "Sorry, and error occurred" when listing in the GUI.

Any ideas? Nothing obviously helpful in the logs, though I do see way more of these than I'd expect:

Code:

May 29 00:01:18 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:03:19 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:04:19 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:06:20 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:07:21 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:09:21 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:10:22 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:12:23 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:13:23 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:15:24 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:16:25 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:18:26 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:19:26 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:21:27 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:22:28 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:24:29 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:25:29 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:27:30 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:28:30 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout
May 29 00:30:31 omega /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ac18>' failed: Call timeout
May 29 00:31:32 omega /alert.py: [system.alert:393] Alert module '<update_check.UpdateCheckAlert object at 0x814d49c50>' failed: Call timeout

 

[dlavigne]

Were you able to resolve this? If not, does updating to U5 fix it? Is this in the new or the old UI?

 

[sunshine931]

After a great deal of poking around, I noticed many other screens (in the web ui) not populating and generating errors. I tried stopping/starting various services, and finally determined that it was the middlewared service that was wedged up.

I decided to export my config and do a fresh install of U4, and updated in the web ui to U5. This may have been overkill, but so far so good.