j0nnymoe

Members
  • Posts

    353
  • Joined

  • Last visited

Posts posted by j0nnymoe

  1. 1 hour ago, kraai said:

    I'm having an issue with Airsonic where my library scan is just extremely slow. It took over a day to scan about 2500 items. My logs show no errors or anything. The music is located on a network share. I also tried libresonic, same issue. Importing music in Emby for example is fine and quick.

     

    I've tried reinstalling and clearing the database, tried fast-access mode, tried libresonic as mentioned. I'm just not sure anymore where to start looking, the network speed is fine, considering emby and other containers run fine.

     

    Any ideas?

    Considering airsonic is forked from libresonic, I would suspect that the app just doesn't like network mounted shares.

  2. 1 hour ago, Abnorm said:

    Sorry about that! 

     

    docker run -d --name='bookstack' --net='br0' --ip='192.168.0.5' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'DB_HOST'='192.168.0.6:3306' -e 'DB_USER'='bookstack' -e 'DB_PASS'='bookstack' -e 'DB_DATABASE'='bookstack' -e 'TCP_PORT_80'='6875' -e 'APP_URL'='' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/bookstack':'/config':'rw' 'linuxserver/bookstack' 

    5f2f592ab53d59b44c1a0425323e26d9ec71c52c0b844850b4d4ff2380608451

    I might be wrong but if you have both bookstack and mariadb on their on dedicated ip's, there is a docker "security" feature that blocks them talking to each other.

    • Like 1
  3. On 8/6/2019 at 8:59 AM, SavageAUS said:

    Radarr:preview branch

    Docker on unRAID.

    Quality settings do not save. I click the save icon and it spins like it tries to save but doesn’t.  When navigating away radarr asks me to stay or leave and discard changes. 

     

    i like the new look and so far it works well. 

    Preview is unsupported. it's a use at own risk.

  4. 40 minutes ago, Ramiii said:

    Thank you

    Let me explain what I want to do. I’m good with the Picons included but I’m missing some of the channels since I’m in Egypt and they are not included. How do I add them ?

    You would need to add them upstream (picons.eu) so they get picked up by us.

    Otherwise, you'll have to re-add them everytime the image updates.

  5. 3 hours ago, MandalorePatriot said:

    Why isn't there a beta or unstable branch? Just got the USW-24-POE-BETA and have to setup a controller on a different system. If the beta branch would be too much work, then I totally understand. Just curious.

    There's alot of history with our unifi container and to be perfectly honest, unifi aren't known for quality releases. We've already been through the pain of users asking us for a new version that's been released instantly then we'd update them and then we would get complaint's that X/Y/Z wouldn't work. Adding a beta/unstable branch would increase the questions even if we stated we don't give support for it.

     

    Abit of back story: https://blog.linuxserver.io/2019/02/18/changes-to-our-unifi-image/

  6. 4 hours ago, jfabaf said:

    Same problem here, Duplicati - 2.0.4.23_beta_2019-07-14 and Linuxserver.io version:- v2.0.4.23-2.0.4.23_beta_2019-07-14-ls28 Build-date:- 2019-07-26T10:47:18+00:00

     

    Error: Only 'http' and 'https' schemes are allowed. Parameter name: requestUri

    As mentioned a couple posts back, it's an upstream issue with mono6 and duplicati, not with the container.

  7. 9 hours ago, Niklas said:

    Yep. Rolling back works.

    The packages upgraded in the latest tag should be reverted or Duplicati needs to update and bring support for the new mono packages. 

    For now, this docker will not work for new users using "latest" or old user that upgrade soon. People that hasn't configured notifications when stuff go wrong will not know that the backups fail if they don't monitor Duplicati in som way. I have configured mail and got the warning via mail after upgrade on "latest". 

    Actually, the issue is due to the upgrade to mono6 and specifically onedrive. Running latest here no problems with backblaze2 so I think it's unfair for you to make the following comment `For now, this docker will not work for new users using "latest" or old user that upgrade soon.`

     

    Right now it only seems to affect onedrive uploading and only 1 other user has reported at duplicati. https://forum.duplicati.com/t/mono-update-breaks-onedrive-v2/7569

     

    This is an upstream issue, Not an container issue.

  8. 9 hours ago, LumberJackGeek said:

    Hi everyone,

     

    Thanks for the work on this! However I realized I am currently stuck on a very old build, what do I need to do to update?

     

    Version

    3.0.0.348

    Mono Version

    5.18.0.240

    image.png.0187c43ea477f0584bb3d01d9b03b9e3.png

     

     

    image.png

    Change from the `lsiodev/sonarr-preview` to `linuxserver/sonarr:preview`

  9. 6 minutes ago, dertbv said:

    Has anyone been able to get this ti work running unsaid as a VM in esxi?  I have a 1600ti card that i installed put in pass through mode added it to unraid.  I boot fine but I am getting "Unable to determine the device handle for GPU 0000:0B:00.0: Unknown Error" .  researching this out says to edit the VM  and add hypervisor.cpuid.v0 = "FALSE", and then unraid boots extremely slow and then fails fails to fully boot.  Anyone have any pointers?

    Pretty sure someone else had this same issue before. Search the thread.

  10. 5 hours ago, andy harris said:

    right like i have sort of fixed it plex will now trans code via the p400 but i am still getting cpu usage through the roof (is that normal) i was expecting it to lower my cpu usage 

     

    i have no idea what i did different i just deleted the packages and started again 

    That's because plex doesn't take full advantage of the GPU yet, it only uses NVENC, not NVDEC. So the decoding get's done via the CPU. Plus audio is done via the CPU too.

  11. 18 minutes ago, andy harris said:

    sorry must have been one of the many time i have tried from scratch to get it working it does read the correct value 

    Capture3.thumb.PNG.cea38ae06b8cadfdec9bd070e680c87f.PNG

     

    still does not work it just seams to send cpu usage through the roof and nothing in nvidia-smi

    Are you copy/pasting stuff from the forum to setup these variables? that can cause issues.

    • Upvote 1
  12. 1 hour ago, Fiservedpi said:

    Is there any way to roll back the driver version 'm getting the error my device is not compatible with this driver version. Do I have to rollback the whole Nvidia-unraid build?

     

    ** I should note the GPU appears to be working with-in my VM but am unable to Passthrough to any Dockers "No Cuda enabled devices available"

     

     

    Using built-in stream user interface
    -> Detected 24 CPUs online; setting concurrency level to 24.
    WARNING: You do not appear to have an NVIDIA GPU supported by the 430.14 NVIDIA Linux graphics driver installed in this system.  For further details, please see the appendix SUPPORTED NVIDIA GRAPHICS CHIPS in the README available on the Linux driver download page at www.nvidia.com.
    -> Not installing a kernel module; skipping the "is an NVIDIA kernel module loaded?" test.
    -> Installing NVIDIA driver version 430.14.
    -> Skipping check for conflicting rpms.
    WARNING: The nvidia-uvm module will not be installed. As a result, CUDA will not function with this installation of the NVIDIA driver.
    WARNING: The nvidia-drm module will not be installed. As a result, DRM-KMS will not function with this installation of the NVIDIA driver.
    WARNING: You specified the '--no-kernel-module' command line option, nvidia-installer will not install a kernel module as part of this driver installation, and it will not remove existing NVIDIA kernel modules not part of an earlier NVIDIA driver installation.  Please ensure that an NVIDIA kernel module matching this driver version is installed separately.

     

    We only build releases with the current version of nvidia driver available. If you want to roll back drivers, you'll need to roll back the unraid build, though this isn't something we recommend or support for obvious reasons.