IanB

Members
  • Posts

    54
  • Joined

  • Last visited

Everything posted by IanB

  1. Great, thanks! I pushed a few updates to the store over the weekend to fix the reported connection issues... ### 1.4 ### - Fix issue preventing dashboard loading when no cache was being used. - Support servers where no password is set. ### 1.3 ### - Fix minor clipping of cards - Fix crash when IP/host included additional whitespace.
  2. @MMW - Thanks for the logs, it looks to be failing to either retrieve the Array information or the Cache info. Do you have an array configured and not using any cache drives?
  3. I've pushed a fix (v1.3) to Google Play to fix the crash when the IP address includes a space either at the beginning or the end. I'll probably need to do some additional validation of the input (rather than crashing) but wanted to get this fix out ASAP for you. I'm not sure how long Google is taking now, but hopefully you'll receive the update soon.
  4. >With just the server ip in a new connection it still just crashes. @MMW Sorry about this. Are you able to send me a bug report from the app? If you're at the Server List page, in the top right the "..." option includes an option "Send Bug Report". This will let you send yourself an email with app logs, which you could upload here for me to take a peak. EDIT: I just checked the crash reporting and see a repeated attempt to add an IP address that includes a trailing space. Looks like i'm not trimming what is entered (sorry). I'll get that fixed ASAP but if that is you, hopefully you can just delete the space character at the end to let you proceed.
  5. Thanks @HynesJeff, I really appreciate the support! I don't suppose you could leave an (honest) review via Google Play. I'm hoping that with more feedback, the discoverability of the app will improve via Search. As for your requests, i'd love to implement that (given time), the problem is that with the lack of a real (stable) Unraid API, the more features I add the risk I am at new updates completely breaking everything and needing to rewrite, while still trying to support older server versions - so a headache. It has been suggested that an API is on the way though, and once released I would hope to be able to quickly switch over to it unlocking the potential of additional features like the ones you suggested. My short term plan is to continue working on the core features and the application host itself to make the experience as good as possible, so it's ready for the API to quickly add lots of great new features.
  6. And another quick update to resolve an important DNS rebinding issue, along with a small bucketful of fixes. I also gave larger tablets some love with some small optimisations for their screen size. The update should hopefully be available via Google Play soon: ### 1.2 ### - [NEW] Optimised tablet layout support - Display disk state correctly (spun up or down) - Fix issue with self-signed certificates failing DNS rebinding protection - Fix crash when backgrounding app after connecting to server - Fix pie chart when displaying more than 12 shares - Sort disks so that Parity drives are always first
  7. Just pushed a new build to Google Play after some great feedback from testers. It should hopefully already be available. ### 1.1 ### - [NEW] Support for self-signed certificates - [NEW] Improved Add Server screen - [NEW] Allow offline servers to be added - Add message to server list when no servers added - Fix crash if trying to add server before providing any host information - Fix share information populating wrongly - Update persisted server information when connecting - Fix crash restoring app - Fix timeout when calculating sizes of large shares
  8. Hey 👋 This started off as a bit of a hobby project that slowly become something that I thought could be useful to others. It was an exercise for me in writing a new app from scratch and the different choices I would make, compared to having to constantly iterate on an existing (large) code base. After sharing this with some of the community in the unofficial discord channel, I was encouraged to get it into a state where it makes sense for others to use. https://play.google.com/store/apps/details?id=uk.liquidsoftware.companion I've already received some great feedback as well as a number of issues and requests for new features, that I hope to add soon. I hope others will find this as useful as I do in managing your UNRAID servers. Enjoy
  9. I've been able to actually update the app and have it mostly working. There is still some issues I need to iron out, as well as potentially some UX nits that I would clean up first if I was to launch this. Is there anyone at Unraid that I can (or should?) talk too regarding this app? I'm still in two minds what to do with it (it was a hobby project), but it could provide some value to users. I would be happy to share details of the app, a video or even an APK for feedback/thoughts from the team. @Squid Sorry for the ping, but do you know who would be best to contact and how?
  10. Sorry, I haven’t had time in a while. Due to no official API, the Unraid updates have broken what I previously had working. Hopefully I’ll have time soon but my job keeps me busy 😅
  11. Does anyone know if Unraid do any request limiting for clients? I've been making good progress with my application but finding that when it initially loads, it can be pretty slow. Debugging it shows that there is an unexpected delay when making a number of requests to the server. If I delay (myself) between the requests, the response are very fast... Sequential ========== [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 - 2.332s Sequential (Reverse Order) ============================== [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 - 2.228s Sequential (Delay between requests) =================================== [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 - 0.267s [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 - 0.143s Individual ========== [IABI]: getting /state/var.ini... [IABI]: finished getting /state/var.ini... 2918 - 0.165s ... [IABI]: getting /Dashboard... [IABI]: finished getting /Dashboard... 65720 - 0.306s Any help would be appreciated
  12. Sorry @Squid, not sure I follow. I'm basically trying to programmatically determine the same details presented here by the Web interface: Thanks in advance
  13. @Squid Don't suppose you know an easy way to obtain the `Uptime` from the server? I had hoped to also find it in the same var.ini file, but doesn't seem to be present...
  14. Thanks @Squid! I totally missed that, accessible via "/state/var.ini".
  15. I decided to explore the possibility of writing my own Android application for Unraid. This was more of an opportunity for me to explore some areas of Android that I hadn't played around with, along with building a new app from scratch. Development was pretty quick/rapid and was able to throw together something that I personally liked. It's now mostly functional, but the key areas missing are not really programming challenges, but more challenges with continuing to try and reverse engineer the API to extract the necessary information from an Unraid server (since there isn't any official supported API). Where is the best place to ask for help? Just ask the individual / specific questions in the forums? I've also not decided if i'd actually release the app for others - I guess it will depend on any interest there is in it. I'd probably want to seek permission though to make sure the Unraid team area happy with it first. Some of the types of questions I hate: What is the correct way to extract the "csrf_token" for the server? And how often should I refresh it? Is there a way to update/obtain share sizes individually? I've been playing around with the "/webGui/scripts/share_size" script exectued via "/update.htm" followed by grabbing the generated "/state/x" file - but it doesn't seem to be correct? In case people are interested in seeing some screenshots, here's a few (slightly out of date)...
  16. I'm trying to setup a High Sierra VM on my 6.6.3 Unraid Server. I've followed the video multiple times to verify i'm doing everything. However, after Force Stopping my VM (after updating the BIOS resolution) and trying to first boot into the OSX installer things start to go wrong. I'm initially presented with an Apple logo for ~5 seconds (no progress bar). After this, the VM appears to reboot back into Clover. This will then repeat a number of times until finally Clover gives up and i'm displayed with a large X. Does anyone have any useful tips to get additional information from Clover as to what is failing? Thanks in advance
  17. Just thought i'd give a quick update, in case anyone else in the future hits this issue... After reading about the kernel issue, I first tried updating my BIOS as my motherboard shipped with a pretty old version. This didn't make any difference. From the description of the kernel issue, it talks about it only happening when Spread Spectrum is enabled, for which my motherboard supported being manually disabled. After I did this though, I unfortunately still found that the clock would drift. There is however a linked (dupe) issue here which suggested another workaround: https://bugzilla.kernel.org/show_bug.cgi?id=198137 I was able to follow these steps, and resolve the clock drift: /etc/rc.d/rc.ntpd stop sudo adjtimex -p ** The tick parameter shows set to 10000 sudo adjtimex -c ** Shows a correct tick value of 10400 (ie.. +4% adjustment) audo adjtimex --tick 10400 sudo adjtimex -p ** Now checking the command-line "date" to the wall clock shows no appreciable drift over a few minutes. /etc/rc.d/rc.ntpd start My server has been running the full day without any noticeable drift. I'm sure that after i reboot, it may lose the adjtimex value and if so, i'll have to look at how to add it to my /config/go. Will keep an eye out for Unraid updates which include any kernel patches for this bug, and test them.
  18. >Possible, but related to Intel Skylake Yeah, it's an issue with Skylake X - like the 7980XE that i'm using. Sounds very similar... If the bug turned out to be this kernel issue, how frequently does Unraid receive updates for kernel patches, etc? I've not been running it long enough to know what their update strategy is. Thanks again for the help!
  19. This actually looks pretty relevant: https://bugzilla.kernel.org/show_bug.cgi?id=197299
  20. >There must be something wrong with your machine or hardware. That's worrying The hardware is all pretty new, Asus x299 Prime Deluxe with a Intel 7980XE...
  21. Since I last ran the `ntpdate` I saw that I was already a few seconds now out of sync. I ran the command, as you suggested (the ntpd service was still running) and it updated: root@Tower:~# ntpdate -u pool.ntp.org 21 Jan 19:37:44 ntpdate[26004]: step time server 87.81.181.2 offset 26.491838 sec Does this suggest that everything appears to work when updating from a remote ntp server, but for some reason, it's not periodically happening?
  22. I managed to stop, update, and restart manually doing the following: root@Tower:~# /etc/rc.d/rc.ntpd stop Stopping NTP daemon... root@Tower:~# ntpdate -s time.nist.gov root@Tower:~# /etc/rc.d/rc.ntpd start Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp My time is now correctly in sync, but will have to now watch to see how it drifts out. Is there a way for me to validate that the NTP service is periodically updating from the remote servers?
  23. Thanks for the suggestion. Unfortunately, it complains about "service": root@Tower:~# sudo service ntp stop sudo: service: command not found
  24. I tried running `ntpdate` manually and got the following: root@Tower:~# ntpdate 21 Jan 19:07:43 ntpdate[15518]: no servers can be used, exiting Is this expected? I checked the `ntp.conf` file and it contained a number of servers defined at the bottom: # Generated entries follow: server time.google.com iburst server pool.ntp.org iburst
  25. Actually, only leaving it a few minutes shows that it's drifting: root@Tower:/mnt/user# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 29 64 77 0.000 0.000 0.000 time3.google.co .GOOG. 1 u 48 64 17 114.412 12742.3 9923.26 li1535-196.memb 89.101.218.6 2 u 16 64 77 148.922 14095.7 10737.0