dikkiedirk

Members
  • Posts

    2255
  • Joined

  • Last visited

Everything posted by dikkiedirk

  1. Glad to see my issue was solved so quick. Hope it doesn't have any negative effects.
  2. It was more involved than I thought. It is related to doing a 'df' to get the size of the mounted device. Doing a 'df' will hang if a device is offline. I had to do 'df /dev/sdX', etc. I only partially solved it in 29a. I will be releasing a 29b today. EDIT: 207.01.29b is available. Much better already, the spiining wheel only appeared a few seconds and GUI is responsive immediately.
  3. Updated to the latest 29a version. I'll see what happens later this evening when my NAS goes off line.
  4. Thanks for the fast reply. At the moment I have my shares deleted but I am glad to set them up again and test. Is the new version released yet? I'll be glad to update the plugin.
  5. I experience some trouble with the unassigned devices plugin. I use it to get access to shares on 2 Qnap NASes. But when these shares go off line the plugin slows down unraids GUI. The plugin shows a spinning wheel on the webpage after it finally opens, which already takes fairly long. Switching from Main to settings or docker or whatever tab takes several minutes, making the UI useless until UD gives up on the shares that are setup. Is there a work around for this? Or can UD wait less longer for the shares to appear, say 1 minute?
  6. It was fixed after uninstalling the user scripts plugin, by deleting the .plg and folder it created of the flash and a reboot. Personally, I find that hard to believe (as the plugin only scans the flashdrive when it loads the UI and then does absolutely nothing at all under any other circumstances), but if you're up and running fine now then so be it. My sincere apologies, I was too fast with my assumption. I also have unassigned devices installed in which I have some shares on an other NAS mounted. If this NAS is off line for whatever reason then unassigned keeps waiting indicated by a spinning wheel but als slowing down the UI?
  7. This plugin seems to have brought the UI to a crawl, it took ages to switch from tab to tab, dashboard main, settings etc. Deleting the plugin from flash brought my system back to normal.
  8. It was fixed after uninstalling the user scripts plugin, by deleting the .plg and folder it created of the flash and a reboot. I was experimenting with this plugin to powerdown the server at night. Server is back to normal performance now.
  9. Running 6.2.4 on te Main server in my sig. I experience a rather slow UI at the moment. It first takes several minutes to open and when I am finally in going from main to docker or any other tab really is a waiting game. I am not able to pull diagnostics because of this. Even pressing the log or info button takes ages. What can I do to troubleshoot. Access to my shares seems normal either from Windows or Dune mediaplayer. Please help. I do see many of these lines in the log appear: Jan 22 02:02:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:03:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:03:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:03:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:03:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:03:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:03:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:03:22 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:05:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:23 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:24 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:24 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected Jan 22 02:18:24 Tower1 emhttp: err: need_authorization: getpeername: Transport endpoint is not connected
  10. Did as instructed and created the script file in the scheduled powerdoen folder. But don't see where I can set the * 2 * *. I see the Apply Done and How to add scripts button but nothing else.
  11. Thanks, what exactly does * 2 * * do? How do I change the time at which the server powers down?
  12. yes, can I just add something like echo "powerdown" | at 02:00 to a scripts file in the config/plugins/user.scripts/scripts folder?
  13. I added this plugin But how and where should I add which line. What should it contain to powerdown down at 01:00 for instance? Can't just a simple line be added to the go file?
  14. True, a block account is an option. But this isn't any help if a small .nfo file is missing that is in the nzb. sabnzb wants to repair this, taking quit some time and loading the cpu where nzbget ignores the .nfo file and starts unpacking. There might be a switch in sabnzb to do the same but I haven't found it yet.
  15. Let sabnzbd run from the cachedrive and do its processing on there, then make sure you have the folders on the array with cache enabled.. Thats what I am doing.. works fine.. Thanks. Will changing my cache drive to a SSD speed up things significantly. Or is it better to switch from SABNZBD to NZBGet? NzbGet is only quicker if you have seriously low powered hardware.. I dont know what you are expecting.. There will be some time difference, but personally I would not care if unpacking a movie would take 3 minutes instead of 5.. I do it this way because it keeps my array spun down (which is also is of no use but I like for some reason ;-) I am not so concerned about the unpacking but more about repairing which sometimes take quit some time. I sometimes try to get older stuff of 1500+ days old which sometimes need a lot of fixing. I think repairing takes cpu power but also a lot of disk I/O.
  16. Let sabnzbd run from the cachedrive and do its processing on there, then make sure you have the folders on the array with cache enabled.. Thats what I am doing.. works fine.. Thanks. Will changing my cache drive to a SSD speed up things significantly. Or is it better to switch from SABNZBD to NZBGet?
  17. Yes to all questions. running from cache drive.
  18. Will adding a SSD to an unraid server speed up the verifying,repairing and unpacking that SABNZBD and NZBGet do? If so, what would be the best scenario: adding it as a cache drive and let SAB and NZBGet do their work there or adding the SSD as an unassigned device and let SAB and NZBGet use it upto their repairing job and unpack it to a share? I still have my shares set up to use a cache drive, so the unpacked files wil end up on the cache drive first. Would a lower priced low end ssd already give a decent speed increase?
  19. I am in a discussion with a sabnzb developer and he suggest that the problem with dir scanner crashing lies in the fact that sabnzb isn't started with UTF8 encoding, probably because unraid dictates another encoding. What is unraid using?
  20. Did my configuration cause the unpack failure I asked about? I don't use CP or Sonarr BTW.
  21. Doesn't it allow the mnt/user structure because it is in a docter? What if I want to use categories where mkvs need to go mnt/user/movies/mkv?
  22. My first download with NZBGet resulted in a unpack failure. Perhaps a configuration error. I enclose the NZBGet log and the docker settings I used. Is it a beginners error? La_Grande_Vadrouille_1966_Louis_de_Funès_1080p_NL_Subs.zip
  23. Thanks Squid. Gonna try NZBGet again and this time a bit longer, trying to get used to it.