New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin won't start on my unraid #1
Comments
Hi @ziggyke even though the permissions seem a bit off, user, group and others have rights to read all the files and execute the unbalance binary. It doesn't seem like that should be an issue. What's the log showing ( Ah I saw you mention the log shows the plugin as started. If you go to There's been some reports in the past about ad-blockers not allowing access to some server pages (such as unbalance's). Is it possible you have any router firewall rules blocking access ? |
I don't have a dir called "logs" in the "boot" dir so can't see nor give you the output of this log.
Yeah the log shows that it seems to be started, but the unRAID UI shows status: "Stopped". So when I try to go to the unBalanced plugin webUI it gives me the output: I don't use a router nor firewall (software or hardware) with rules that block access to certain ports/addresses. Thank you for taking a look into this. |
Ok, try this ... from the server terminal
It should start and it should create a file You should also be able to browse to Let me know how it goes. |
thank you for the quick reply. |
mmm that's really strange ... can you post a screenshot ? then try this ...
|
@ziggyke I think I was able to reproduce the issue, I'm looking into it |
Ah great to hear! |
Turns out I wasn't able to reproduce. Not really sure what's the problem with the plugin in your server. Try and change permissions and user/groups like you mentioned in your first post. Below is how it's behaving in my server This is /boot without a logs folder
So I run the app
It created the logs folder
I checked the size of the executable from the terminal output you sent and it matches what I have
|
I've changed the permissions to 755 for the dir "unbalance" and the files within:
I've also manually created the "logs" dir in the "boot" dir. Still when I try to start by command line or trough the webGUI of unRAID the status stays stopped and nothing is started... Can it be that a plugin/docker is conflicting with your plugin? Further nothing can be found in the logs of unRAID what the plugin is doing or why it won't start... |
@ziggyke I don't have too many more ideas ... last thing I can think of is create a 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 folder is created correctly and also a config is present in that folder when installing the plugin, so I'm not sure if that would solve the problem. When I get home I'll try to perform this test. Aha that maybe a direction to a solution... Also on the forum there are 2 other people who are mentioning to having this problem. |
I am one of the others with the problem. I am running XFS as filesystem.
|
One thing there could be an issue regarding starting it from settings, is that it seems like it is clearing the .cfg after a few seconds
|
TL;DR: Make sure you have an "unbalance.conf" not just an "unbalance.cfg", different files there. A simple touch can fix it. 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. |
Nice :) That did the trick
And now the web ui works |
The webui link on the settings page, does not work though. Its just getting me a blank about page |
That did the trick!!
Maybe you can update the plugin that it also creates the unbalance.conf so that this should stop it from not starting. |
hi @ziggyke @ZataH @tobytl I'm really glad the root cause was finally found. Thanks @tobytl for the analysis, I'll have to learn a bit more about strace. I actually see an error now in the plugin template .. it tries to create unbalance.cfg instead of unbalance.conf. I'll fix that and it should start working normally again (hopefully). I will also revise the flag parsing logic ... it should catch that error anyway. Thanks a lot to all for helping me figure this out ! I really appreciate it. |
@jbrodriguez Most importanly we found the cause :) |
@ZataH I'll release a new version, since the source for all the components (server, client and plugin code) is contained in a single repo. I'll try to release it later today or tomorrow at the latest |
maybe a possible solution to implement. This to overcome this fault in the future and make it more visible for others what conf file is for what? Thanks for updating this and searching with me to solve the issue. |
@ziggyke it's a good idea but it would take a "non-zero" (tm) amount of effort to implement :) unbalance.conf should really be transparent to the user, it shouldn't be touched directly. I think the changes I'll be making should prevent further recurrence of this issue. |
ok fair enough. |
Hmm it is still not working. It is creating the .conf file now though. But I have no idea why it is not working
no logs in /boot/logs Tried to remove and reinstall the plugin several times
But still nothing when i try to reach the address |
Thanks @ZataH I actually failed to add some flags on the server side of the code. And turns out there were many other instances of unbalance.cfg I had to replace 😳 |
I've updated the unbalance plugin and it behaved the same way as before, still everything was in place and should be fine. I needed to re-install the plugin and know everything is working again. Thanks for the quick fix although! |
Just tried to reinstall it @jbrodriguez and both the server and webui button are working now :) Thanks |
mmm on second though I needed to reboot server, because I bougth unRAID Basic key.
If I do it like you described previously then it gives also an error that flag isn't defined:
I noticed that there isn't a unbalance.cfg anymore, so I created it:
But even after that still starting the plugin provides the same error as mentioned in the beginning of my comment. The unbalance log gives this error:
|
I honestly don't know how the settings/flags system has been "working" since I changed from docker to plugin :) You should use PORT not port. Can you show me your unbalance.conf ? |
right forgot to post it.
which the plugin itself had created, because when uninstalling the plugin it deletes everything (config, logs, plugin itself) which is a good thing! |
Well, turns out 1.8.0 used unbalance.cfg for the plugin system and unbalance.conf for the unbalance settings ... just what you had mentioned @ziggyke What I did now, was to account for /boot/config/plugins/unbalance/unbalance.conf possibly not being present and handle accordingly. I think this will fix the issue. @ziggyke your unbalance.conf is corrupt, you need to delete it and install 1.8.3 |
I removed the plugin again and yaj! It's working again! |
that's good to know ! |
@jbrodriguez you probably can add milestone (as off 1.8.3) to this issue and close it as solved. |
sure I don't have milestones, but I'll close the issue 👍 |
i have a strange problem trying to start unbalance and i have no idea why it is happening LOG |
Never saw this error before, it's quite unusual. I guess that you can see your array normally from the unRAID webGUI right ? Can you do $ df --block-size=1 /mnt/* What does it return ? |
I don't know what those cache/socket/tmp files/folders are ... if someone with more linux knowledge can weigh in, I'd appreciate it. In the meantime, let me give this some thought. |
yea i have no idea what they are or why they are there but they have been there for a while now |
unBALANCE fails due to these 'pseudo'-folders. I'm not sure where they come from, I'll do some research |
i am also still on unraid 6.4.1 with 6.5 waiting to install also i have a dyeing drive in my array that i cant do anything about until next week |
so i still have no idea what happened as far as the phantom folders but after updating to unraid 6.5.0 everything seems fine. could have been a problem with the last update or the dying drive that is not gone and a new one in its place. |
Hey, that's good to know ! Glad it's working now. |
I have the same issue .. nothing above helped. i would start it per command line and see that a nother file is missing in conf dir: unbalance.hist .. so i created it and no he says EOF (end of file?) "netstat -an | grep LISTENING" is also not showing this port log file: I: 2018/09/03 02:15:41 app.go:51: unbalance v5.2.1-1075-77e21d9-v2018.06.05 starting ... |
delete unbalance.hist |
Hi
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:
Then I checked the permissions on the folder and files for unbalance and this is the output:
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:
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
The text was updated successfully, but these errors were encountered: