ausrhino

Hey guys - like Gracey400 I am having the worst time trying to activate a licence. @coppit I have read the github page and there is nothing there about the process to undertake for the activation. On the current versions there is no Offline Activation mode, nor is there the ability to install a licence server on another networks pc. Any help going through this process would be appreciated.

Hey guys, Upgraded to the new version. I have been having some problems though with (what appear to be incomplete) files not completing and remaining in the queue unfinished. I have been going over the settings and I can't seem to resolve this issue. I have attached some screens of the settings and hoping someone can see where I have gone wrong. Thanks in advance.

Reporting in similiar to other users. After upgrade to Unraid 6.1.8 I have lost GUI access to Deluge. Deluge - 1.3.12-20 My brother who runs this as well is also experiencing the same. Any thoughts? Module Size Used by md_mod 30680 6 xt_nat 1665 11 veth 4401 0 ipt_MASQUERADE 981 12 nf_nat_masquerade_ipv4 1649 1 ipt_MASQUERADE iptable_nat 1615 1 nf_conntrack_ipv4 5626 2 nf_nat_ipv4 4111 1 iptable_nat iptable_filter 1280 1 ip_tables 9310 2 iptable_filter,iptable_nat nf_nat 9789 3 nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4 k10temp 2684 0 i2c_piix4 7688 0 ahci 24107 8 r8169 57464 0 libahci 18687 1 ahci mii 3339 1 r8169 acpi_cpufreq 6074 0

Here are some other threads that have had similiar issues. I think this is Docker related. I had the same issue as described. Some light reading anyway - with some good ideas on how to troubleshoot the problem. https://lime-technology.com/forum/index.php?topic=39510.0 http://lime-technology.com/forum/index.php?topic=45286.0

That's great news. I am happy you were able to get it working. Although you got this working - hopefully the daily restarting will stop SAB from locking up and taking down DOCKER, which in turn (for me anyway) - was taking down my system. Please report back in a week or so and let us know if the lock-up has returned. It is definitely something to do with SAB locking up DOCKER - then taking down UNRAID - something I thought was supposed to not be able to occur by using DOCKER. The problem then compounded for me where I couldn't run DIAGNOSTICS (no access to GUI and Telnet command hung). Anyway - daily restarting DOCKER via this method has stopped the 5 to 6 day lockup that I was having. I hope it works for you as well.

Where both files created in notepad++? Just checking that you wrote the files on the server *BEFORE* restart? You are using the Docker Tab - Advanced View to see the up time. You are correct that the uptime should always count back to it being restarted at 5:10am each morning. From your settings it is clear that it didn't restart for some reason. I would suggest to check your folder names to make sure they are correct. In saying that I have attached a zip file with my files to show you my exact setup. Hope that helps. If you are wanting to test, without having to wait all day. What I did was change the CRON file time to say 10 minutes ahead of current time. Wrote the file. Then restarted Unraid. Waited past the time and checked to see if the files worked. example:- Time is now 9:00am. changed the cron file time to # Daily Docker Restart - 9:10am 10 9 * * * /boot/custom/docker_restart.sh &> /dev/null Understanding that * * * * * command to be executed - - - - - | | | | | | | | | +----- day of week (0 - 6) (Sunday=0) | | | +------- month (1 - 12) | | +--------- day of month (1 - 31) | +----------- hour (0 - 23) +------------- min (0 - 59) Then log back in and check after that time on the Docker tab to see if it worked. That might be a quicker way for you to test instead of waiting each day. If the job worked - change the CRON time to what ever you prefer. Restart your Unraid and check again the following day to make sure it has worked. If it doesn't work on the test come and report back. Unraid_Docker_Restart.zip

See the attachment.

Yes you can use notepad to create the files and name the file as required. docker_restart.sh #!/bin/bash #Stop plugin services located in /etc/rc.d/ # enter in plugins to stop here, if any #stop dockers docker stop $(docker ps -a -q) #Start plugin services # enter in plugins to start here, if any #start dockers /etc/rc.d/rc.docker start docker_restart.cron # Daily Docker Restart - 5:10am 10 5 * * * /boot/custom/docker_restart.sh &> /dev/null I missed the .cron on the original post. Edited now. I use a program called notepad++ - grab it here https://notepad-plus-plus.org/

This problem seems to be a long running problem and has been reported here https://lime-technology.com/forum/index.php?topic=39510.0 I also had this problem and and it directly seems to be connected with SAB. My issue was that I was having a recurring issues with the GIU becoming unresponsive. I tried a number of things - specifically CPU pinning http://lime-technology.com/forum/index.php?topic=36257.0 - which solved the issue for a time - however the hanging did start again (over longer periods). I ended up setting a daily CRON job to restart my dockers. This stopped my GUI hang problem. UNDER Flash (folder) - created folder custom flash\custom created the following script docker_restart.sh #!/bin/bash #Stop plugin services located in /etc/rc.d/ # enter in plugins to stop here, if any #stop dockers docker stop $(docker ps -a -q) #Start plugin services # enter in plugins to start here, if any #start dockers /etc/rc.d/rc.docker start Unraid supports CRON jobs now. I then created a CRON job under flash\config\plugins\dockrestart (dockrestart was folder I created to store the file) docker_restart.cron # Daily Docker Restart - 5:10am 10 5 * * * /boot/custom/docker_restart.sh &> /dev/null Obviously the code - /boot/custom/docker_restart.sh is referring to the location and script name where you placed and named the docker_restart.sh script. You have to restart the server for the job to be loaded. Since doing the above my server has been back to good ole rocksolid. I have not had a GUI hang since, however I dare say I have not fixed the underlying problem (it will still be there) - and on the basis of the defect thread - it is clear I do not possess the skill or technical ability to fix it. For your info the dockers I run are Couchpotato Delugevpn Plex Sabnzbd Daapd Sonarr Ubooquity So my daily restarting them is not an issue. I do the restart when the server is run up about 15 minutes after mover has started. It has been working flawlessly. The issue of my daily restarting the dockers is not issues - but it might be something you want to explore dependant on what dockers you are running - and the viability if they can be restarted daily. Hope this helps. I am no guru by any means - if there are any errors in the above - can a more knowledgeable user point it out. Credit here - https://lime-technology.com/forum/index.php?topic=43431.msg414779#msg414779 http://www.nncron.ru/help/EN/working/cron-format.htm - use this to assist in determinng the time you want for the CRON job to start. Explains the time format

Ok - thanks for the help guys. The problem has been fixed. Stopped the Array Removed the USB to a windows machine On doing so it came up with a Disk Check Completed Disk Check (confirmed no presence of second key) Back into Unraid Server Booted and now back to normal with Pro slots Thanks for your replies guys. It seems to have been a USB related error.

There are no keys on the flash drive other then the pro key.

Hey guys, I did a restart on my UNRAID server today. Clean shut down - no problems. On boot up I lost all the assigned drive placements and I also lost my PRO Key settings. My server dropped back to a 5 slot. I readded the Pro Key - rebooted and I am still restricted. Does anyone have any ideas on this. First time I have hit this problem. Thanks