needo

Members
  • Posts

    301
  • Joined

  • Last visited

Posts posted by needo

  1. shfs is not accurately displaying hard link information

     

    When accessing a hardlink file through shfs it is showing up twice in ls/du/etc.

     

    root@Tower:/mnt/user/Test# du -h
    5.3G	./Dir1
    5.3G	./Dir2
    11G	.
    
    root@Tower:/mnt/user/Test# ls -i Dir1/File1
    142 Dir1/File1
    root@Tower:/mnt/user/Test# ls -i Dir2/Hardlink 
    562 Dir2/Hardlink

    But if you go to the disk itself...

     

    root@Tower:/mnt/disk1/Test# ls -i Dir1/File1 
    102 Dir1/File1
    root@Tower:/mnt/disk1/Test# ls -i Dir2/Hardlink 
    102 Dir2/Hardlink

    However df -h reports the disk space usage correctly.

     

    Thank you!

  2. I'm trying to use your transmission docker but I am running into a wall it installed correctly but when it ask for the username and password it rejects it

    I am using "admin" and "password" not quotes and it will not log in. Any suggestions?

    Thanks.

     

    By default transmission does not have a username/password set. So it is whatever you configured it as.

  3. Does anyone know how to get Sonarr (aka NZBDrone) to update to the latest build inside the docker? I ran the Update from the web app. It appears to go through but then fails:

     

    [info] InstallUpdateService: Downloading update 2.0.0.2500 
    [info] InstallUpdateService: Verifying update package 
    [info] InstallUpdateService: Update package verified successfully 
    [info] InstallUpdateService: Extracting Update package 
    [info] InstallUpdateService: Update package extracted successfully 
    [info] BackupService: Starting Backup 
    [info] InstallUpdateService: Preparing client 
    [info] InstallUpdateService: Starting update client /tmp/nzbdrone_update/NzbDrone.Update.exe 
    [info] InstallUpdateService: NzbDrone will restart shortly. 
    [info] Bootstrap: Starting NzbDrone - /opt/NzbDrone/NzbDrone.exe - Version 2.0.0.2341 
    [info] SingleInstancePolicy: 1 instance(s) of NzbDrone are running 
    [Warn] SingleInstancePolicy: Another instance of NzbDrone is already running. 
    [info] Bootstrap: Application is being terminated. Reason : Another instance is already running 

     

    It appears that the update fails or the old version doesn't close correctly. Has anyone been able to run updates?

     

    This might be the issue:

     

    https://forums.sonarr.tv/t/upgrade-fails-due-to-permissions-issue/2578/2

     

    You cannot update software after Docker is already running. Well technically you can, but it is against all standards and practices. To get the latest updates click on the update button in the DockerMan part of the unRAID UI.

  4. Im new to Docker and thought i had everything figured out with it but apparently not. Ive spent the last hour or so searching the forums for a solution and may have missed it so i apologize if this solution is found elsewhere.

     

    I just installed the SABnzbd app from needo's repo and when i start it i am unable to access the web gui for it. I have attached a screenshot of what everything looks like in the docker configuration screen. I am using the docker tab on the unraid menu to start my containers, etc.

     

    When i try to access the web interface for sab or any of the others i have tried (couchpotato, nzbdrone) i just get a web page cannot be displayed error

     

    Hopefully its a dumb mistake on my part that you guys can point out so i can keep moving with this.

     

    The defaults are right. It should work. To verify you are going to http://unraid-name:8081/ correct? Replace unraid-name with the IP Address or name of your unRAID box.

     

    If that doesn't work you have larger networking issues that are outside my scope.

  5. Hi Needo

     

    Do you have any thoughts around SAB? Can it be configured with EDGE so that it can update itself without you having to update your Docker? As you may have seen 0.7.20 was released, but we can't currently update SAB without you updating your Docker. I tried updating the Docker via the GUI, as well as deleting and re-creating, but both still come back with 0.7.19.

     

    It would be great to get this container away from dependency on you (or any one person).

     

    I'll work on it. I updated sab to the latest version this morning.

  6. The update to Deluge Docker (commit: "Update to latest version of deluge") has broken deluge.

     

    I think the problem lies with the apt-get install command after adding the new deluge:ppa (thanks for adding that!!):

     

    Apt-Get was previously:

    apt-get install -qy deluged deluge-web unrar unzip p7zip

     

    but now it is:

    apt-get install -qy deluge unrar unzip p7zip

     

    We need the deluged and the deluge-web apps or else a change to the run command:

     

     

    Below are the logs after the container is started:

     

    setuser: cannot execute deluge-web: [Errno 2] No such file or directory
    setuser: cannot execute deluged: [Errno 2] No such file or directory

     

    Hope this helps in fixing the issue,

     

    The Capt.

     

    Updated!

  7. I'm on

     

    plexWatch/Web Version: v1.5.4.2

    plexWatch Version: v0.3.1

    PMS Version: v0.9.11.4

     

    and everything is working great for me.

     

    Im on the same as you and it doesn't work.  But it did work before the update to Plex Server v0.9.11.4.

     

    Apparently there is a plexWatch Version v0.3.2 which fixes this issue.

     

    Sorry for the late replies. plexWatch.pl lives outside the docker. You need to downloaded the latest plexWatch.pl from the author's site and put it in /mnt/cache/appdata/plexWatch/

  8. Trying to get Plex Media Server docker to see my movies. The web GUI works fine (can also see my windoze plex server). I added UNC paths pointing to my movie folders and it scans for a half second and stops. No titles get added.

     

    I had similar issue when I tried to install on 5.05 and ended up going to Windows install that works great. Problem is the laptop can't handle transcoding very well so I wanted the unRaid 6-core CPU to handle it. Just can't get it to see the movies.

     

    Upgraded to v6 10a and installed a cache disk to run dockers. Install went without a hitch and Plex is running on Tower.

     

    I have tried local paths (e.g. /mnt/disk1 etc), UNC paths pointing to both local & other uR server (e.g., //tower/disk1 or //tower2/disk2, etc). In the 5.05 attempt I ran the perms script multiple times (no effect).

     

    Any ideas?

     

    Ps. the windows install sees all the movies and sets them up as expected.

     

    Why are you using /mnt/disk1,etc. instead of setting up a TV or Movie share and using /mnt/user/TV or /mnt/user/Movies ?

  9. Ouch! This is the risk with running betas! We knew the job was dangerous when we took it! Considering this is my second round of betas with LimeTech (6 and 5) and this is the first "possible" data corruption issue that has occurred I still consider this pretty good.

     

    Unfortunately I have been running 6b7 and 6b8 for so long and recently replaced my parity drive so if my data is corrupted then it is. Ill wait patiently for b9.

     

    The best thing you can do to protect yourselves right now is this:

     

    DO NOT WRITE ANY DATA TO A REISERFS DISK IN THE ARRAY

     

    XFS and BTRFS filesystems remain unaffected by this issue.

     

    I am doing this by disabling mover for the time being.

  10. Ouch! This is the risk with running betas! We knew the job was dangerous when we took it! Considering this is my second round of betas with LimeTech (6 and 5) and this is the first "possible" data corruption issue that has occurred I still consider this pretty good.

     

    Unfortunately I have been running 6b7 and 6b8 for so long and recently replaced my parity drive so if my data is corrupted then it is. Ill wait patiently for b9.

  11. needo, is there a reason why PMS didn't run as user "nobody" ?

     

    I just messed up my Library here with the newperms command....  :-[

     

    Plex by default runs as a non-privileged user on every Linux platform. I did not want to make the Docker "special" and harder to support. Plus the vast majority of people already had their databases set as unraid-plex:unraid-plex as they converted over to Docker and I wanted the transition to be as seamless as possible.