Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[SOLVED] Dynamix Plugin Control doesn't survive reboot

Featured Replies

I have an interesting problem.

 

I have the Dynamix Webgui loaded on unraid. As indicated in an earlier post, the Dynamix plugin control and the other sub-apps (S3 sleep, SSMTP etc) .PLG files are located in /boot/config/plugins folder.

 

However, when I reboot the server, Dynamix is reloaded as are my other plugins such as Couchpotato, Sabnzbd and Sickbeard, but the sub-plugins of Dynamix such as S3, SSMTP and Plugin Control panel don't load. I can manually start them and they pop up nicely on the Webui.

 

I looked over a my syslog after a fresh reboot, and it looks like unRaid is starting these sub-applications (S3, SSMTP, plugin control panel) BEFORE it has even loaded the Dynamix webgui... So an error occurs, and then later in the syslog, Dynamix gets loaded. How can I change the order so that The main webgui plugin gets loaded first and then the sub-plugins get loaded?

 

Here is a pastebin log of my syslog: http://pastebin.com/ubdGLsRM

 

The relevant portion from the syslog is posted below:

Mar 25 23:52:03 Tower logger: installing plugin: dynamix.cache.dirs-2.1.0-noarch-bergware

Mar 25 23:52:03 Tower logger:  file /tmp/plugin-startup: successfully wrote INLINE file contents

Mar 25 23:52:03 Tower logger:  /bin/bash /tmp/plugin-startup ... missing Dynamix webGui plugin !!!

Mar 25 23:52:03 Tower logger: failed

Mar 25 23:52:03 Tower logger: installing plugin: dynamix.email.notify-2.1.0-noarch-bergware

Mar 25 23:52:03 Tower logger:  file /tmp/plugin-startup: successfully wrote INLINE file contents

Mar 25 23:52:03 Tower logger:  /bin/bash /tmp/plugin-startup ... missing Dynamix webGui plugin !!!

Mar 25 23:52:03 Tower logger: failed

Mar 25 23:52:03 Tower logger: installing plugin: dynamix.plugin.control-2.1.1-noarch-bergware

Mar 25 23:52:03 Tower logger:  file /tmp/plugin-startup: successfully wrote INLINE file contents

Mar 25 23:52:03 Tower logger:  /bin/bash /tmp/plugin-startup ... missing Dynamix webGui plugin !!!

Mar 25 23:52:03 Tower logger: failed

Mar 25 23:52:03 Tower logger: installing plugin: dynamix.webGui-2.2.2-noarch-bergware

Mar 25 23:52:03 Tower logger:  file /tmp/plugin-startup: successfully wrote INLINE file contents

Mar 25 23:52:03 Tower logger:  /bin/bash /tmp/plugin-startup ... success

Mar 25 23:52:03 Tower logger:  file /boot/config/plugins/dynamix/dynamix.webGui.cfg: already exists

Mar 25 23:52:03 Tower logger:  file /boot/plugins/dynamix.webGui-2.2.2-i486-1.txz: already exists

Mar 25 23:52:03 Tower logger:  upgradepkg --install-new /boot/plugins/dynamix.webGui-2.2.2-i486-1.txz ...

Mar 25 23:52:03 Tower logger: +==============================================================================

Mar 25 23:52:03 Tower logger: | Installing new package /boot/plugins/dynamix.webGui-2.2.2-i486-1.txz

Mar 25 23:52:03 Tower logger: +==============================================================================

Mar 25 23:52:03 Tower logger:

Mar 25 23:52:03 Tower logger: Verifying package dynamix.webGui-2.2.2-i486-1.txz.

Mar 25 23:52:03 Tower logger: Installing package dynamix.webGui-2.2.2-i486-1.txz:

Mar 25 23:52:03 Tower logger: PACKAGE DESCRIPTION:

Mar 25 23:52:03 Tower logger: Package dynamix.webGui-2.2.2-i486-1.txz installed.

Mar 25 23:52:03 Tower logger:

Mar 25 23:52:03 Tower logger:

Mar 25 23:52:03 Tower logger: success

Mar 25 23:52:03 Tower logger:  file /boot/config/plugins/images/dynamix.webGui.png: already exists

Mar 25 23:52:03 Tower logger:  file /usr/local/emhttp/plugins/webGui/images/dynamix.webGui.png: successfully copied LOCAL file

 

Can someone please help me and educate me on how best to fix this problem? I've posted the portion where the dynamix plugins are attempted to be started in RED and the part where dynamix webui gets loaded in BLUE.

 

Thank you so much!

Did you put the dynamix plugins in /boot/config/plugins and the webgui in /boot/plugins? Or did you put everything in /boot/plugins? If so, that is your reason. :)

  • Author

Yes, as you see in the log, the dynamix webgui .txz file is in the /boot/plugins.

 

But the dynamix plugins are in the /boot/config/plugins.

 

There is a copy of the dynamix webgui in /boot/config/plugins as well. Should that no be there?

There is a copy of the dynamix webgui in /boot/config/plugins as well. Should that no be there?

It is not there on my system that is behaving itself so it could well be the cause of your problem.

  • Author

 

Yes, that did the trick! Thanks!  :D

 

Perhaps that ought to be stated in the Dynamix plugin page:

 

The webgui has to be on /boot/plugins

All other plugins should be in /boot/config/plugins

Technically that info is there, if you follow the installation procedure detailed on the github entry page, it installs the gui to /boot/plugins first and then tells you to install the other optional plugins to /boot/config/plugins. :)

  • 2 weeks later...

I would like to know if the dynamix plugin control plg should be in the boot/plugins or boot/config/plugins?

  • 6 months later...

Great thread! It helped me solve my issue. Once I copied the webui plg into the /boot/plugins dir and restarted, my dynamix tab/plugin control became resident.

 

I'm very impressed with Dynamix's development....everyone should donate!

 

Thanks!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.