unbalance: plugin won't start on my unraid

First of all thanks for creating this plugin! Second I want to try it out for the first time on my very first UnRAID installation, but according the log it would start except I can’t get in the webUI…

I’m running UnRAID 6.2.4 (at the moment still in trial modus). The plugin version of unBalanced is v1.8.0 and in the settings of unBalanced even if I set the option to enable the server to “Yes” still it won’t work.

This is what I get in my log after enabling the plugin:

Nov 17 13:49:32 *** php: /usr/local/emhttp/plugins/unbalance/scripts/start
Nov 17 13:49:32 *** sudo:     root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/bin/bash -c /usr/local/emhttp/plugins/unbalance/unbalance -port 6237
Nov 17 13:49:35 *** emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

Then I checked the permissions on the folder and files for unbalance and this is the output:

root@***:/usr/local/emhttp/plugins/unbalance# ls -al
total 7980
drwxr-xr-x  7  501 wheel     280 Nov 11 18:14 ./
drwxrwxrwx 36 root root      720 Nov 17 13:57 ../
-rw-r--r--  1  501 wheel   33487 Nov 11 18:14 CHANGES
-rw-r--r--  1  501 wheel     142 Nov 11 18:14 README.md
-rw-r--r--  1  501 wheel       6 Nov 11 18:14 VERSION
drwxr-xr-x  2  501 wheel      80 Nov 17 13:57 app/
drwxr-xr-x  2  501 wheel      80 Nov 17 13:57 event/
drwxr-xr-x  2  501 wheel      60 Nov 17 13:57 images/
drwxr-xr-x  2  501 wheel     240 Nov 17 13:57 img/
-rw-r--r--  1  501 wheel     666 Nov 11 18:14 index.html
drwxr-xr-x  2  501 wheel      80 Nov 17 13:57 scripts/
-rwxr-xr-x  1  501 wheel 7937102 Nov 11 18:14 unbalance*
-rw-r--r--  1  501 wheel    4030 Nov 11 18:14 unbalance.page
-rw-r--r--  1  501 wheel  179257 Nov 11 18:14 unbalance.png

To me that doesn’t seem right, because user is set to “501” en group is set to “wheel”. Do I need and is it safe to chmod (755) and/or chown the unbalanced plugin folder and all the files inside to a “correct/known” user and/or group?

The following I’ve already tried, but all result into the same log:

Tried a different port to start the plugin
Tried a different user to start the plugin
Tried uninstalling and installing the plugin

I would like to take a look into the possibilities of this plugin, because now it seems to be doing nothing even if it is enabled.

What can I do to solve this issue and is this enough information to take a look into the problem or what information is needed to further look into this?

kind regards

kristof

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 47 (19 by maintainers)

Most upvoted comments

TL;DR: Make sure you have an “unbalance.conf” not just an “unbalance.cfg”, different files there. A simple touch can fix it. # touch /boot/config/plugins/unbalance/unbalance.conf

So, I’m an idiot… I had this problem too. Sat here looking at the code, trying to figure out whats happening (saw it, btw, just didn’t think it was a showstopper). Finally decided to run an strace… And, it can’t open the config file and exits with code 2. Looks familiar, that’s what should happen with flag.Parse() if it’s error handling is set to exitonerror, except the default is to continue on error (or it is supposed to be?) and I couldn’t see a place where you changed it. But ah well, exit(2) when the config file can’t be read none the less.

tobytl on Nov 24, 2016

@ziggyke I don’t have too many more ideas … last thing I can think of is create a /boot/config/plugins/unbalance folder, start the app, see if it works. If that fails create a /boot/config/plugins/unbalance/unbalance.conf file (it should be fine empty), start the app, see if it works.

I had replicated the behaviour (not starting), but only when running on my mac, which doesn’t have the same filesystem structure as unRAID, so it wasn’t a proper test.

It’s baffling, I will say that.

That did the trick!! But why does the plugin install doesn’t create the correct conf file? Because after installation there is a unbalance.cfg file created and nothing else.

root@***:/boot/config/plugins/unbalance# ls -al
total 3320
drwxrwxrwx  2 root root    4096 Nov 22 09:41 ./
drwxrwxrwx 32 root root    8192 Nov 22 09:41 ../
-rwxrwxrwx  1 root root 3379598 Nov 11 18:28 unbalance-1.8.0.tgz*
-rwxrwxrwx  1 root root      45 Nov 22 09:42 unbalance.cfg*

Maybe you can update the plugin that it also creates the unbalance.conf so that this should stop it from not starting. WebUI works but indeed not from the link on the settingspage of the plugin. It’s just creates a new tabbed window.

ziggyke on Nov 24, 2016

@ziggyke I don’t have too many more ideas … last thing I can think of is create a /boot/config/plugins/unbalance folder, start the app, see if it works. If that fails create a /boot/config/plugins/unbalance/unbalance.conf file (it should be fine empty), start the app, see if it works.

I had replicated the behaviour (not starting), but only when running on my mac, which doesn’t have the same filesystem structure as unRAID, so it wasn’t a proper test.

It’s baffling, I will say that.

jbrodriguez on Nov 23, 2016