jbrodriguez

v2.4.0 is now available on both stores (or should be pretty soon) ! 2.4.0 - 2017-02-10 This is a maintenance release, with updates to core app libraries. Also in this release: - Fix warning message created by missing token in api call - General improvements and bug fixes As previously mentioned, this is mainly to catch up with many libraries that were updated in the past weeks and to fix the warning about the missing token. @johnnie.black, would you let me know if the visual issue persists ?

No, no need for the plugin for over-the-air to work. Are you on iOS or Android ?

As in swiped it from recent apps and re-opened it? Many times, yes. I'll try a 'Force close' and see if it helps. The way over-the-air works is an red badge appears on the settings icon to draw attention, when you press Settings, it shows a message saying restart to update (or something close to that). It's strange that it seemingly didn't work for you. In any case, I have a new version on review in the stores, hope it becomes available soon. I'll also create a FAQ in the App's website ... there's too much info scattered around in the forum pages, it will be better to have a central location for common questions.

I found out I missed updating a call to server with the new security token (thanks to Marv for bringing this up). You will get Jan 30 09:43:10 Tower root: error: webGui/include/DeviceList.php: missing csrf_token messages in the log, whenever you refresh the server in ControlR. I've fixed this in the latest code and I'm also upgrading core libraries in the app, so I'll release a new version in the next few days.

v2.3.3 is available as an over-the-air release (won't appear in the App/Play Store) 2.3.3 Proper support for shutdown/reboot commands in unRAID 6.3.x Also in this release: - Improve reboot logic - General improvements and bug fixes Well, 2.3.2 supports the new security features, but unRAID 6.3.x also changed the invocation of the shutdown/reboot commands. @jademonkee, this release (2.3.3) should fix the shutdown command not working issue you raised. I checked the link you posted. I don't think they are related.

Thanks jademonkee ! It should work, but I'll check it.

Thanks for the comment ! Glad to know it's working

Do not do this if you have docker applications running. Yes, I remember Squid mentioning that FCP's newperms is Docker-safe.

v2.1.0 is now available ! 2017-02-03 - 2.1.0 This release implements real time move progress ! Progress is synchronized with rsync transfer updates. Also in this release: - Bug fixes and improvements The default rsync flags are now: -avPRX (previously "avRX --partial") The -P represents "--progress --partial", so this change is basically adding --progress, which is required to make rsync show progress as it transfer files.

Should work

Hi thejamkel, what version of unraid are you running ? Can you send me the plugin log for that session (pm if you want) ?

v2.3.2 is available as an over-the-air release (won't appear in the App nor Play store) 2.3.2 This release adds support for unRAID 6.3.0-rc9, which brings some internal changes in the way it operates. Also in this release: - General improvements and bug fixes If you're running rc9, let me know how it works for you.

Sparkum, thejamkel, I found an issue with the ControlR plugin that didn't allow logs to display, if the server didn't have a password. Please upgrade the plugin to v1.1.5 and let me know if that solved it for you.

v1.1.5 is available ! 2017-02-02 - 1.1.5 This release provides the following fixes: - Support getting logs for servers with no password set - Support 6.3.0-rc9 Should fix the issue where some users were not seeing logs in the ControlR app.

Hi thejamkel, I think that should work. Let me check the code and get back with what I find. thejamkel, do you get a line starting with "auth:usr:..." in the plugin's log (/boot/logs/controlr.log) ? Did you add the server by ip or by hostname ?

Hi thejamkel, I think that should work. Let me check the code and get back with what I find.

oh, thanks a lot Squid ! I'll check what changes are needed.

Hi, I suggest that you select the sub-folders of the main folder. Or whatever level of granularity you want to work with. What the app does is (roughly): Given a folder, get the sizes of the first-level folder/files Allocate them across the target disk(s) (recreating the whole tree) An example If you have a folder structure such as this: - films -- bluray --- Movie1 --- Movie2 ... --- Movie 999 -- dvd and select films, it will try to allocate bluray (which might be in the TB range) and dvd. Unless you have an empty target disk, most likely it won't be able to allocate the bluray folder. If you select films/bluray, it will try to allocate the individual MovieX's, which will be roughly 50GB each, and that is very likely to succeed. The app depends on the user providing the "work unit" to operate on, to put it in other words.

Yes it does! But I guess I am expecting "Real Time" statuses. See attachment; using Chrome, statuses are now shown but has been stuck in this state for about 2hours. I'm noticing it only being refreshed after the transfer of an entire share is complete. Should this be expected behavior or should the status be refreshed more often? Currently transferring 1.5TB of data to clear a disk for format to xfs. Oh ok. Currently, that's expected behavior. It refreshes after each rsync command has completed. I wrote about that when I first introduced the progress feature, but forgot to mention it in the updated github README. The thing is rsync's progress is somewhat difficult to parse, so I just track the whole operation, not the individual files. I'll eventually look into improving that

It shows no activity (other than starting/stopping). Can you access the plugin's web ui (http://<server>:2378/) ? That should log something. Let me know how it goes, eventually I'll pm you to further troubleshoot.

Hi cpthook, I generally use Chrome and it works fine for me Ff you check the raw log (/boot/logs/unbalance.log), does it show any progress ?

Hi thejamkel and Sparkum, Can you check the plugin logs (/boot/logs/controlr.log) ? Do they show anything unusual ? Like a warning or error ? Let me know.

Thanks mata7, I'll see if I can improve that.

Honestly, I'm not completely sure, but I'll look into it. If this means I need a separate codebase, I'll most likely not do it.

Yes, that's really strange ! The next release is an update to the core libraries, I'll check if there's something that may fix this.