freenas web page 9.10 sluggish compared to 9.2.1 ??

[Bernard Mentink]

Hi,

I have just upgraded my hardware and my Freenas OS from 9.2.1 to 9.10. The pool imported just fine and everything is stable .... (although I am prompted to upgrade my pool of course )

What I am finding though, is that the web interface is very sluggish on various items. For example, when it first comes up the left hand menu takes a long time to show, and also my installed plugins take over a minute to show when I am looking at that tab ..

It is way slower than 9.2.1, yet the hardware is much faster in all respects ...
... is this something to do with not upgrading my pool yet?

I am reluctant to upgrade my pool just yet, just in case the new hardware is not stable and I have to go back to the 9.2.1 system ..

Cheers,
Bernie

 

[dlavigne]

How much RAM on the system? Which web browser name and version?

 

[Bernard Mentink]

Hi,
I presume you mean RAM on the server, it is 16G ....
Browser on client machine is Chromium version 50.0 ...

I had a lot less RAM on the old system(4G) and the web interface was much faster ...

 

[dlavigne]

Make sure the system is updated to the latest SU as there were recent dojo fixes to make Chromium happy.

Also, make sure Chromium is updated to the latest.

Or, try a different browser...

 

[Bernard Mentink]

What is SU? If you mean the system update, the last time I did one was a week ago ..

 

[dlavigne]

Yes. There was another one yesterday.

 

[Bernard Mentink]

Ok, I update to: FreeNAS-9.10-STABLE-201606270534 (dd17351)

But the problem remains. I get the "Bar" animation when loading the left had pane for some 10 seconds and it still takes over one minute to show my plugins ... I get the "bar" animation plus ".. loading"
I also tried firefox ... still the same issue ..

 

[dlavigne]

Anything in /var/log/messages while this is happening?

 

[Bernard Mentink]

Good thought, I did see this:

Code:

Jun 29 07:57:58 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://127.0.0.1/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
Jun 29 07:58:08 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/treemenu: timed out
Jun 29 07:59:13 freenas kernel: arp: 192.168.178.37 moved from 02:ff:20:00:06:0a to 30:5a:3a:c8:3b:29 on epair1b
Jun 29 08:00:28 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/status: No JSON object could be decoded

.. and a bit more complete one:

Code:

un 29 07:39:25 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
Jun 29 07:40:03 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://127.0.0.1/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
Jun 29 07:40:11 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/treemenu: timed out
Jun 29 07:42:01 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://127.0.0.1/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
Jun 29 07:42:11 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/treemenu: timed out
Jun 29 07:43:54 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/status: No JSON object could be decoded
Jun 29 07:52:28 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/status: No JSON object could be decoded
Jun 29 07:54:22 freenas notifier: Generating grub configuration file ...
Jun 29 07:54:25 freenas notifier: done
Jun 29 07:54:26 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://127.0.0.1/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
Jun 29 07:54:36 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/treemenu: timed out
Jun 29 07:57:26 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/myvolume/pluginjails/.warden-template-pluginjail'
Jun 29 07:57:26 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/plexmediaserver_1'
Jun 29 07:57:26 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/couchpotato_1'
Jun 29 07:57:26 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/webpage'
Jun 29 07:57:26 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/tvheadend'
Jun 29 07:57:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs list -H -o name '/mnt/myvolume/pluginjails/.warden-template-pluginjail'
Jun 29 07:57:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/plexmediaserver_1'
Jun 29 07:57:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/couchpotato_1'
Jun 29 07:57:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/webpage'
Jun 29 07:57:27 freenas manage.py: [common.pipesubr:61] Popen()ing: /sbin/zfs get -H origin '/mnt/myvolume/pluginjails/tvheadend'
Jun 29 07:57:58 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://127.0.0.1/plugins/plexmediaserver/1/_s/treemenu: No JSON object could be decoded
Jun 29 07:58:08 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/treemenu: timed out
Jun 29 07:59:13 freenas kernel: arp: 192.168.178.37 moved from 02:ff:20:00:06:0a to 30:5a:3a:c8:3b:29 on epair1b
Jun 29 08:00:28 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://127.0.0.1/plugins/couchpotato/2/_s/status: No JSON object could be decoded
[bmentink@freenas ~]$

 

[dlavigne]

This comment from today might interest you: https://bugs.freenas.org/issues/15013#note-54.

However, you should plan on reinstalling your plugins/jails at some point as the ABI changed between 9.2 and 9.10, which is most likely the real issue...

 

[Bernard Mentink]

Ok, thanks. The plex plugin was "Upgraded" does that not use the new ABI? Or should I re-install it ..

I have a number of other jails, especially one running a web server/wiki .... are you saying I have to redo those from scratch? That would be a pain ..

 

[dlavigne]

Yes (eventually), and definitely if you have any plans to update them.

 

[Bernard Mentink]

Ok, thanks for your help ..

By the way, should I be doing the pool upgrade before/after these plugin/jail changes ... and what is the risk on my pool of upgrading it? ...

 

[dlavigne]

When to upgrade the pool won't matter as it is separate from the OS, installed software, and config.

The rule of thumb for pool upgrades is to consider whether or not you ever plan to use those disks in a non-FreeNAS system that supports ZFS (or an older version of FreeNAS). If never, there is no harm in being updated to all available ZFS feature flags (which is what a pool upgrade does). If there's a possibility, be aware that the upgraded pool may not work on older versions or other ZFS systems that don't have those feature flags.