Comments on: January Plugin Updates

By: Philip Robar

Philip Robar — Tue, 05 Feb 2019 17:48:05 +0000

In reply to Dru Lavigne. I updated PMS_Updater and used it. I'll try the official methods when the next Plex update comes out.

By: Dru Lavigne

Dru Lavigne — Mon, 04 Feb 2019 15:57:31 +0000

In reply to Ixian.

Thank you for the clarification! It looks like this was the fix for that, which is coming with U2: https://redmine.ixsystems.com/issues/67510.

By: Ixian

Ixian — Mon, 04 Feb 2019 15:37:20 +0000

In reply to Dru Lavigne.

If you install the Plex plugin (regular or -plexpass) it creates a jail called “Plex”. The update json file in the jail is not called plex, it is called plexmediaserver or plexmediaserver-plexpass.
Running “iocage update plex” doesn’t work for this reason. If you rename the jail to either plexmediaserver or plexmediaserver-plexpass, depending on which you installed, it does.
It’s possible this was modified in 11.2U1 – hard to say from the bug notes – but there certainly seem to be a large subset of users with this problem if the forum posts are any indication.

By: Dru Lavigne

Dru Lavigne — Mon, 04 Feb 2019 14:45:07 +0000

In reply to Philip Robar. Were you able to resolve this? I cannot reproduce this error when I run "iocage update plex".

By: Dru Lavigne

Dru Lavigne — Sun, 03 Feb 2019 23:10:13 +0000

In reply to Darryl. We're open to suggestions on how to improve the Release Notes as they are meant to be a comprehensive but succint messaging for end-users so they know what to expect in a release and how changes impact them.

By: Darryl

Darryl — Sat, 02 Feb 2019 00:19:37 +0000

I am with Philip. My initial and continued purpose for FreeNAS is as a simpler, more dependable Plex server. The latter has never been a question. Rock solid performance. But wow, as someone with middle of the road command line skills, FreeNAS has been a major pain to manage … and the confusing release notes and forum updates (does it work or not) have only made this otherwise simple task up updating Plex more difficult. My expectations are small AND I so want to be a fan. Please fix this or at least communicate better, so that I can be one again.

By: Philip Robar

Philip Robar — Fri, 25 Jan 2019 21:14:42 +0000

And of course the work around for the broken GUI update process doesn’t itself work:
[root@server ~]# iocage list
+—–+——+——-+————–+——+
| JID | NAME | STATE | RELEASE | IP4 |
+=====+======+=======+==============+======+
| 3 | plex | up | 11.2-RELEASE | DHCP |
+—–+——+——-+————–+——+
[root@server ~]# iocage update plex
Snapshotting plex…
Updating plugin INDEX…
/mnt/space1/iocage/.plugin_index/plex.json was not found!
[root@server ~]# ls /mnt/space1/iocage/.plugin_index/
…
plexmediaserver-plexpass.json
plexmediaserver.json
…
Also since the link to the GUI bug given in the December Plugin Updates post can’t be seen by anyone outside of iXsystems because its owner apparently has been too lazy for weeks now to remove the personally identifiable data from bug so that the public can follow it, I guess that we should assume that fixing plugin related bugs (even those in the framework itself) is a very low priority for iXsystems and thus we shouldn’t count on it getting fixed any time in the foreseeable future.
So that leaves us with workarounds that may or may not break our jails since they’re not themselves supported:
1) Use FreeBSD’s updating process inside the jail, even though you’re not supposed to use them inside a jail.
2) Use the PMS_Updater script and hope that it doesn’t breaks things since it hasn’t been updated for iocages.
or
3) Delete and recreate your jail everytime a plugin is updated.
Sigh!

By: diskdiddler

diskdiddler — Thu, 24 Jan 2019 22:56:04 +0000

Thank you for the ongoing hard work. I really hope, in time, more people with coding skill contribute and help out with the plugins going forward.