Jump to content

Leverz

Members
  • Content Count

    32
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Leverz

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Why would you wish to go back to 4.1.9.1? Is it due to the password and username reverting back to default? If this is the case, then the reversion will not help. Correct the problem by following frollay's advice. If you are unsure how to edit the files, one method would be to use a config editor, you can get one in the apps section, called CA Config Editor, and follow the advise above. If you cannot navigate to the location, it is /mnt/user/appdata/... the rest of the address depends which docker version you have installed, but I'm sure you can figure it out.
  2. Thanks for the reply, got it sorted now!
  3. When I set up a call in cron it will work fine, however after a reboot it is reset. I have tried this a few times and it keeps doing it. I'm not sure what I'm doing wrong here as it states at the bottom that the file was wrote to.
  4. I'm guessing you have already done it, but have you restarted Unraid? I'm sorry for the "have you tried turning it off and on again", but you would be surprised at how many times people forget this simple task. While you have a lot of dockers from Binhex here, it seems like a system error, you could try a simple ping from the terminal to see if the system is able to resolve a destination. ping www.bluesnews.com -c 2 I would of guessed it is something like a cached DNS issue, hence the reboot suggestion, but unless it has been added by Lime Technology, I do not think Arch uses a cache. However it has been many years since I used any distro in a great depth. To get more eyes on this you may want to open a thread on General Support, as people there may be more people there with a greater understanding of the underlying system. I would be interested in finding out what is up with this myself.
  5. Is it one day out, or is it starting the week on a different day? I mean, is it just a display issue you are having, as you can change the day of the week from Monday to Sunday in the settings. It is highly unlikely for any modern system, with an internet connection to have, and maintain, an incorrect date and/or time, especially after running an update on it, but lets check. If it is not the Sonarr settings displaying something different from what you expect, open the terminal and enter : date do you get the expected day, date, time, timezone and year? E.g. Wed Aug 21 10:00:15 BST 2019 Also check to see if it matches with the hardware clock. hwclock --show This will output the date and time, are they both set to the same date, with similar times? If so then the problem is not there. if there is a problem, you could run a command to correct the problem, use 'hwclock --help' and then look at 'hctosys' or 'systohc' to clarify which one is required.
  6. Have you tried running the Date and Time option in settings, updating the time and checking the time zone? That would be the first thing to check.
  7. Everything was working fine, then I rebooted and the only docker that is not working is sonarr. I try to reset the docker settings, to what was working before, it starts, but I get the same error. I tried to restart again, this time I get the error, something like docker is not there. So I refreshed the page, and the docker is not listed. I navigated using the terminal and checked that the docker was there. Trying a few times to get it up and running, including reinstalling the app, and I could not get it to start at all. I checked and radarr was still working and I could bring up the WebUI. I removed the docker again, and then removed the docker container in appdata. I had a backup so I reinstalled and restored getting it to work (mostly) again. I have come across the bug where new shows added (files and/or through UI) are shown and act like they are un-monitored, even through the UI shows the flag that they are monitored. If this happened only once, I would shrug it off, but this is the third time Sonarr has become unresponsive for no apparent reason. Is there a know problem? If so is there a fix or a work around? What about the adding of new shows? Is this a known problem?
  8. Not sure what happened, but trying to fix it 20 hours later, by adding a new show I noticed it was adding correctly. So I deleted (not files) and then scanned again and everything working as it should.
  9. I have added a few shows to my library, however they are showing up as unmonitored. Is there a fix for this? When I go to each series, they are marked as monitored. I have tried to toggle this and save, but it makes no difference. Restarting the Sonarr instance and/or rebooting the Unraid system also make no difference.
  10. How do you get this to work? Python or Bash. Don't care. /script/ is a path mapped into the docker for qbittorrent.
  11. Anyone know how to run a bash or python script when download completes? I have tried setting a few options in "Run external program on torrent completion" but nothing seems to work.
  12. Thank you Johnnie for your time and help. I think my understanding of High-Water may be lacking.
  13. I started with 2 empty disks. With the settings my understanding (simplifying this) is that it would copy 1 series to a disk, then next series to a different disk, then all following series to what ever disk has (roughly) the most space and repeat until done. However, all shows went to one disk, and keep doing so. It is working like "Fill-up" not "High-Water". Am i missing something here. Ignore the fact its at 100% thing of it one is at 50% and one at 0%, and it keeps writing to 50%. Is it, I have the wrong settings, or is there another issue?
  14. Are you saying that my settings are right? If so, then why has one disk filled up and the other one is basically untouched? I actually read that post of yours before I ever downloaded Unraid, research into if Unraid would do what I wanted and what settings I was going to use.
  15. My point is, if there is almost 4TB on another disk, this should never happen, as it should do next series on a different disk. I understand your reference to, if a disk is full, the next season cannot be written to it, BUT, it should, by my understanding, split everything across the disks with the current setup. This is not an old NAS, this is a newly setup system.