jbrodriguez

I've published an update for the app, this should fix the issue with the scrolling stats. They will not auto scroll anymore (if there are enough separate stats), you now scroll it manually.

v4.5.0 is available on the App Store / Play Store ! This release updates replaces the scrolling marquee for server stats, with a fixed scrollable view. Also, base components have been updated.

Thanks, I'll look into this next week. Sent from my iPhone using Tapatalk

Hi, thanks for the report. This just started happening ? Did you upgrade iOS ? Just looking for something that may have triggered it. I'll take a look. I've been thinking to make that section fixed, but scrollable, for a while, mostly considering battery consumption. If I can reproduce the issue, I'll probably end up doing it.

Thanks for presenting this scenario jonathanm. I was surprised by how much overhead xfs had, the last time I formatted a disk. I'm thinking about raising the hard limit to 1Gb, although one can always go above it in the settings, if so preferred. Sent from my iPhone using Tapatalk

The plugin reserves a minimum of 512Mb as a hard limit, but you can go higher in the settings. There are some forum members very knowledgeable on the hard disk subject matter and they prefer not to have disks "filled to the brim". On the other hand, if you use your hard disk as "read-only" (fill it with contents, start with a new disk, repeat), it shouldn't really be a problem, and you skip the fragmentation you mentioned.

Hi, Short Answer Use unbalance exclusively. No other dockers/vms/plugins/mover touching the disks. Long Answer The bottom line is if you're moving content outside unbalance when it's running, the assumptions it made may no longer be valid. That is, it thought you had 40Gb free on disk1, but a docker or mover dropped it to 35Gb. Maybe it will still work, but it's very possible that it won't (out of space, source not found, etc) If you know what you're doing, that you won't be touching the disks that unbalance is operating on, then keep running dockers/vms, but you want to be sure that doing so won't have side effects.

It skips deletion when there was an error with the rsync command, specifically error 23, which is quite generic. When that happens the rsync command is flagged and when you look at the operation in the History tab, it appears with a yellow icon and an 'rmsrc' button on the left. The idea is that you check why it was flagged (permissions, timestamps, etc) and if you want, you manually remove the source with the 'rmsrc' button (some more details here) You have performed some other operations, so you can't replay that specific operation. Why don't you delete the sources manually, not optimal but it should work.

It looks fine. Yet the plugin can't connect to port 443 (connection refused). It seems that the webGUI isn't actually listening on 443, but I can't really tell.

v4.4.0 is available on the App Store / Play Store ! This release adds support for Unraid 6.6 (docker operations). It brings back the web ui icon for dockers (it wasn't showing in v.4.3.0)

Hi, Yes, I didn't address this issue because I'm not sure how to solve it from my end. If you go to Settings > Identification, what port is ssl is set to (I guess it's grayed out) ?

v2018.10.03 (2.14.0) is out ! This release always starts the api endpoint on https. Other changes: - Remove $GOPATH from stack trace - Go lint (revive) - Fix Go lint errors

v4.3.0 is available on the App Store / Play Store ! This release adds support for Unraid 6.6 (docker operations). Additionally, it improves the connection logic with the companion plugin. Finally, an icon is now shown next to the server name, to identify if it was added via http or https. Make sure to upgrade the ControlR plugin to the latest version as well.

Thanks for reminding me about this. You can connect with other users but you need to use the root password (this is due to how Unraid currently operates). I have to update the FAQ to inform about this properly. About the docker operation, the latest app release I'm about to publish adds support for 6.6.x

Try ss -p on the backup server, it should show which process owns port 443. In any case, I'm getting ready to publish a release that improves the app/plugin connection logic.

Cool ! What's the size of your cache drive ? Is it a pool of drives ? Could you run df --block-size=1 /mnt/* and send me the output (pm if you prefer). It would also help if you could send me /boot/logs/unbalance.log, to further understand. I do take some precautions with the cache drive, but maybe something changed or I had it wrong.

Hi denishay, If not offered, it's almost certain that the size of the entire share is 4Tb+. Try running du -h /mnt/user/<your share name> Should give you the approx size of the whole share. If it turns out to be 4Tb+, not sure how your content is organized, but try selecting folders off the main share.

Awesome !

I remembered I had this kind of reports a while back, checked your log again and see you're doing a Scatter/Move. I run an additional "purge" routine, for parent folders that are empty, but it applies only for the Gather operation. I don't remember why that's the case, may it was because it was reported on the Gather operation only. I can't find a reason currently not to do it for the Scatter/Move operation, I will look at some other scenarios, but will most likely add it for Scatter/Move in the next release. In any case, please do remember that unBALANCE should run exclusively. If you have other apps/plugins/etc, moving content around, the results are unpredictable.

Hi, Hadn't had the chance to post a reply. There are a couple of things, from checking your logs. There are many instances where the plugin isn't deleting folders, by design, because the rsync operation was flagged with code 23 (which can mean permission issues, datetime issues and honestly pretty much anything). The plugin doesn't delete the source in these cases and shows these commands with a yellow icon and an rmsrc label in the history page, so you can eventually remove the source (rmsrc), after you manually check it's ok to do so. Many commands are being flagged due to the file seemingly not being present: "rsync: link_stat "/mnt/disk2/media/films-auto/City Lights (1931)/City Lights (1931) - Bluray-720p.mkv" failed: No such file or directory (2)" Are you running mover while unBALANCE is running ? Or perhaps a nzbget/torrent docker that move folders around ? Is the only thing I can think of.

Great news ! I'll try to replicate your scenario, to do some poking. Thanks for reporting and going through the process.

Oh, yes. The 401 Authorization Required message is due to an incorrect password. Thanks for helping both figure it out !

Is it possible you have an ip clash ? 192.168.1.9 may be actually reaching the main server ? or something else on your lan ? I don't think the server itself is the issue, I think maybe you have some rules set up in your router ? P.D: or perhaps something like planetwilson mentioned ?

Are you adding it using port 80 or 2382 ? If it's the former, now that you installed the plugin, can you debug the connection process again and show me me error screenshot ? Are you running a reverse proxy, doing some port redirection on the server ?

Hi, there's something other than the webGUI answering on port 443 of that server. If you debug adding the main server securely on 443, do you get the same error ? Is there any redirection of port 443 happening on your lan ?