Jump to content

Yagami

Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by Yagami

  1. On 1/25/2023 at 2:02 AM, dlandon said:

    Yes.

     

    Please answer my question about an error message or blank screen when you try to access the GUI.

     

    You should try to starting from scratch.  Delete the Docker Container, delete the appdata/LogitechMediaServer folder and start over.  Be sure to watch the log and wait for the Start Logitech Media server message before stopping it.

    Hey @dlandon
    I finally got it to work, i followed the steps above (remove container, delete Appdata folder, re-install, launch, watch for Start, stop container, then restart).

    A note on the container's page on community apps might be helpful for new comers, as this is a bit strange.

     

    Thanks again for looking into it and fixing it.

  2. Hi,
    I been playing around with the VM section for a little while now, and i feel confident enough to use a windows VM as my primary machine in the near future.

    I've passed an AMD Radeon RX580 GPU to the VM, and after facing the issue of 100% fan blowing (there are a couple of topics here and on reddit ), i found out that the solution is to install the correct drivers within the VM so software will take care of fan management.

    Which i did, however i'm not able to launch the Radeon software (screen is working, resolution is correct, Fan issue disappeared).
    Is there something i'm missing ?  the Radeon pro software is visible when right clicking on the desktop but clicking it doesn't bring anything up; neither going to program files and launching the software (i also tried run as administrator).

    I'm not sure what logs or details to attach, so i will wait for the first responses to provide whatever details needed.

     

    Thanks

  3. On 1/23/2023 at 10:25 PM, dlandon said:

    Do you get an error message when you try to access the GUI?

     

    On 1/23/2023 at 10:43 PM, dlandon said:

    I just fired up a new LMS Docker from scratch and there is an issue with the WebGUI pn an initial install.  I updated the Docker and it seems to work now.  I'll do a bit more testing and put out an updated Docker if it tests out.

     

    On 1/24/2023 at 12:09 AM, dlandon said:

    I'm trying to understand why a first time setup is having issues.  In the meantime, I've found that you can stop and restart the docker and it will settle down and you'll be able to access the web page.

     

    Thanks @dlandon for acknowledging the issue.
    I updated the container, launched it again, Gui not working, i stopped it and restarted it and still no luck.
    Do you want me to provide the logs ? 

  4. 1 hour ago, dlandon said:

    Use all the default values.  Don't change anything.  Once you get access to the GUI working, you can make changes.

    Thanks.

    My issue is that i'm not able to get to the GUI, i'm using all default values of the container, When i click on "WebUi" button on the container the page doesn't load.

    FYI i have a 20ish dockers working, and im pretty decent at managing basic stuff, i checked all allocations and no other docker uses the 9000 nor the 9090.

     

    If you can think of anything i should troubleshoot i would be thankful, otherwise i guess no chance to get this container to work.

     

    Thanks again for your time.

  5. 46 minutes ago, trurl said:

    post docker run

    Here it is : 

    docker run
      -d
      --name='LogitechMediaServer'
      --net='bridge'
      -e TZ="America/Los_Angeles"
      -e HOST_OS="Unraid"
      -e HOST_HOSTNAME="Multiverse"
      -e HOST_CONTAINERNAME="LogitechMediaServer"
      -e 'PUID'='99'
      -e 'PGID'='100'
      -l net.unraid.docker.managed=dockerman
      -l net.unraid.docker.webui='http://[IP]:[PORT:9000]/'
      -l net.unraid.docker.icon='https://github.com/dlandon/docker.templates/raw/master/logitechmediaserver.png'
      -p '9000:9000/tcp'
      -p '3483:3483/tcp'
      -p '3483:3483/udp'
      -p '9090:9090/tcp'
      -v '/mnt/user/classical music/':'/music':'rw'
      -v '/mnt/user/appdata/LogitechMediaServer':'/config':'rw'
      --log-opt max-size=50m
      --log-opt max-file=1 'dlandon/logitechmediaserver'

    25a9f2bebff38fa026048b9e2019f0147358c9f492ed4992c422ba74e7e70910

    The command finished successfully!

  6. On 9/2/2022 at 3:01 AM, Ashepp said:

    Did you ever figure this out? I have the same issue.

     

    On 11/29/2022 at 1:57 PM, steve1977 said:

    It seems to be working for others then? ;-) Let me file a bug report. Maybe you can add to it to get developer attention?


    I did get it to work again, by going to the file config and change the token after re-authenticating plex and linking it to Trakt.
    It was pure intuition, but it's bad that the container never tells you what's wrong even in the logs.
    One more thing, each time you update the container, you have to redo the login on console, so i would suggest to leave it as is if you manage to make it work.

  7. Hi @dlandon

    I have installed the docker image, and for whatever reason im not able to access the GUI nor find the server through a controller app.
    I checked if there were any conflicts with other docker allocations which i found (Twonky Server) : 
    - I changed the ports for Twonky (LMS still doesn't load GUI)
    - I changed the ports on LMS ((LMS still doesn't load GUI))
    - I completely removed Twonky, and checked all my allocation, no other docker uses 3483 nor 9000 nor 9090 (LMS still doesn't load GUI)
    - I used : Host / Bridge / Customer network (LMS still doesn't load GUI)

    attached are logs after i started the container.

    Anything else i should be looking at to make it work ?

    Thanks

    Edit 1 : the docker forces a specific TZ which is different from where im based, could that create the issue ? 



     

    LMS Logs.txt

  8. Hi,

    The container just stopped working, i did a re-install in both methods described in Github but nothing.

     

    When i start the container and i click on console it gives me the following error : "Error response from daemon: Container 943cde93235b54242f7acccc4276d7dbba31b408da2bcc3439e36d28d9afc048 is not running"

     

    These are the logs from the container itslef : nection error: (401) unauthorized; https://192-168-X-XXX.50da8a33f5144102804b184ce28118b2.plex.direct:32400/ <html><head><script>window.location = window.location.href.match(/(^.+\/)[^\/]*$/)[1] + 'web/index.html';</script><title>Unauthorized</title></head><body><h1>401 Unauthorized</h1></body></html>, local url http://172.18.X.X:32400 didn't respond either. Check PLEX_LOCALURL in .env file.

     

    I have tried to put both Plex and this docker in the same customer network on docker, both of them as host, one host and one on the custom network, but in vain.

     

    Any help would be appreciated.

  9. Hi Everyone,
    Rebooted the server to make some changes, and now the nvme cache is showing me the below error (error log below also).

    Couple of notes :

    - I run all dockers in this Cache and set to prefer cache

    - I chose the "directory" mode in intial set-up for docker and not Vdisc)

     

    The drives are still detected, and showing on the list of usable drives, but unraid is asking me to format

     

    The error :

     

    image.png.5933875a6c0fc81b711cf675855b36b2.png

     

    The Log :

    Jan 9 06:15:51 Multiverse kernel: nvme0n1: p1
    Jan 9 06:15:51 Multiverse kernel: BTRFS: device fsid 765f6f1d-a3a7-487b-a5db-2c284bf3918d devid 1 transid 21878 /dev/nvme0n1p1 scanned by udevd (1687)
    Jan 9 06:16:16 Multiverse emhttpd: Sabrent_Rocket_Q4_7D37071518CD00000204 (nvme0n1) 512 3907029168
    Jan 9 06:16:16 Multiverse emhttpd: import 31 cache device: (nvme0n1) Sabrent_Rocket_Q4_7D37071518CD00000204
    Jan 9 06:16:16 Multiverse emhttpd: read SMART /dev/nvme0n1
    Jan 9 06:16:23 Multiverse kernel: BTRFS info (device nvme0n1p1): turning on async discard
    Jan 9 06:16:23 Multiverse kernel: BTRFS info (device nvme0n1p1): using free space tree
    Jan 9 06:16:23 Multiverse kernel: BTRFS info (device nvme0n1p1): has skinny extents
    Jan 9 06:16:23 Multiverse kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizations
    Jan 9 06:16:23 Multiverse kernel: BTRFS info (device nvme0n1p1): start tree-log replay
    Jan 9 06:16:23 Multiverse root: mount: /mnt/nvme: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
    Jan 9 06:16:23 Multiverse kernel: BTRFS: error (device nvme0n1p1) in btrfs_replay_log:2279: errno=-22 unknown (Failed to recover log tree)
    Jan 9 06:16:23 Multiverse kernel: BTRFS error (device nvme0n1p1): open_ctree failed

     

×
×
  • Create New...