Jump to content

niwmik

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

1 Neutral

About niwmik

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. bwssytems is recommending to run the webui on port 80 due to some recent changes to Amazon echo devices. I run the following command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='habridge' --net='br0' --ip='192.168.1.7' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'TCP_PORT_8080'='80' -e 'TCP_PORT_50000'='50000' -e 'SEC_KEY'='Gh#12uis' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/habridge':'/config':'rw' 'linuxserver/habridge' 1cd31ce78e11edbac7164b5fc9d41154c71deb2842bf26682966600958e2e3e5 But the webui is still running on port 8080. Any ideas on how to fix? Thanks.
  2. My solution was to select the 5.14 tag which contains Mono 5.14. Movies are now successfully moved to a SMB share.
  3. I believe this is the issue with using a SMB share. Will have to figure out a way to downgrade Mono in the docker. https://www.reddit.com/r/radarr/comments/cikhkw/strange_incomplete_moving_of_files_all_of_a/
  4. As a test, I changed the path "/movies" from a SMB share to a user share in the radarr docker. Everything is now working again. I'll leave it like this and manually move the files over to the SMB share until I can figure out what was going on with the previous error.
  5. I have been using the following permissions setting in linuxserver/sonarr and linuxserver/radarr and everything has been working fine for some time now. After an automated docker update a couple of days ago, I am now getting the following error in radarr: Unable to apply permissions to: /movies/XXXXX: Error setting file permissions: EPERM NzbDrone.Mono.Disk.LinuxPermissionsException: Error setting file permissions: EPERM at NzbDrone.Mono.Disk.DiskProvider.SetPermissions (System.String path, System.String mask) [0x0003e] in C:\projects\radarr-usby1\src\NzbDrone.Mono\Disk\DiskProvider.cs:125 at NzbDrone.Mono.Disk.DiskProvider.SetPermissions (System.String path, System.String mask, System.String user, System.String group) [0x00000] in C:\projects\radarr-usby1\src\NzbDrone.Mono\Disk\DiskProvider.cs:74 at NzbDrone.Core.MediaFiles.MediaFileAttributeService.SetMonoPermissions (System.String path, System.String permissions) [0x0000f] in C:\projects\radarr-usby1\src\NzbDrone.Core\MediaFiles\MediaFileAttributeService.cs:88 From what I can tell, sonarr works fine because it's saving to a user share. radarr is setup to save to a SMB share (another unRaid server) with the RW/Slave option. I've changed from nobody / users to 99 / 100 in the radarr settings but still get the same error. Eventually the Unassigned Devices plugin will hang. I believe this is caused by radarr repeatedly attempting to save to the SMB share. Any dockers using the Unassigned Devices smb shares also hang and I have to then do a hard reset on the unraid machine. Both unRaid is 6.7.2 and all dockers/plugins are updated to the latest. Any ideas as why this happening?
  6. The solution for me was to switch from LTS to 5.9 and then restore from my 5.6.40 backup. I can now see all my clients.
  7. My fault, should have mentioned that Unifi is displaying the radios as disabled is incorrect. All AP's are working normally. I would normally see both wired and wireless clients.
  8. I had to replace my cache drive and recreate my docker.img. I restored my appdata using CA Appdata Backup / Restore v2 and installed Unifi-Controller LTS. Everything was working perfect before but the issue now is I can see my devices in the Unifi Controller but I can't see any clients. The next step I took was to download a backup file from Unifi Controller. I then remove the existing docker and deleted the appdata/unifi folder and created a new docker and restored from the backup file. I had the same results of seeing devices but not clients. Only thing I see different is that the current LTS is 5.6.42 and my backups are from 5.6.40. Not sure if that makes a difference. Any ideas as why I'm not seeing clients?
  9. had the 100% cpu on one core issue on 3 different unraid 6.5.3 with cache_dirs version 2.2.5. upgraded all 3 servers to 6.6.6 and within 48 hours uptime, i haven't seen the 100% cpu issue.
  10. thanks to this post: the solution was to add: {-block-as-image} .thetvdb.com to the end of the file /mnt/cache/appdata/binhex-delugevpn/privoxy/user.action
  11. When I enter the privoxy value in the Proxy host field in SickRage, everything works fine except I'm unable to download images from theTVDB. I get the following error: SHOWQUEUE-REFRESH :: Unable to look up show on theTVDB, not downloading images: error HTTP error None while loading URL http://thetvdb.com/api/F9C450E78D99172E/series/273181/banners.xml When I clear out the Proxy host field and restart SickRage, I can successfully download the images. I then tried unchecking "also use global proxy setting for indexers (tvdb, xem, anidb, etc.)" and enter the privoxy value in the Proxy host field in SickRage and restart SickRage. I then get the following error: SHOWQUEUE-REFRESH :: Request failed: 403 Client Error: Request blocked by Privoxy for url: http://thetvdb.com/banners/fanart/original/121361-84.jpg Do you know what I can do to fix this?
  12. Already done Sent from my LG-D852 using Tapatalk Thank you. Except the fix is in the .plg file and won't change anything for people who already had that installed (since its part of the one-time conversion from the old version of the plg to the new). You just have to make a change (any change) on the plugin settings schedule. Where am I suppose to make this change? I've tried the Community Applications Auto Update Settings, Community Applications General Settings, and Scheduler but still receive the email. TIA
  13. I'm using this card on unRaid 5.0.6 (thanks guys) and would like to upgrade to the latest stable unRaid 6. Would the steps be: 1. run the 6.01 Upgrade Plugin for V5 and reboot 2. verify that 60-persistent-storage.rules is still at \\tower\flash 3. update the fresh ‘go’ file with the 4 lines of script before loading emhttp and reboot
  14. On my working server, I'm seeing the same numbers as you with 50 MB/second write and 100 MB/second read. On the test server with the ARC-1260, I have 2 disks connected directly to it with one being parity and the other being data drive which is parity protected. I'm surprise I'm getting 80 MB/second write to the data drive but I thought I would at least get the same read speed from the data drive since the parity drive is not involved. Googling shows some issues with read speed but that was in RAID mode.