ShadeZeRO

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by ShadeZeRO

  1. 43 minutes ago, ZosoPage1963 said:

    I turned off GPU transcoding and my users are able to stream again.   

    Doesn't that mean it uses your CPU?
    Also - I did some (more) testing.

    GPU transcode works fine if I don't stream at original quality.  Uses the transcode folder properly.
    If doing direct play the docker image fills up and the stream stutters.

    Edit: Disabling Direct Play on the client seems to fix it for now.

  2. Same issue here.  After this most recent update my Plex container using tons of CPU.
    Transcoding does not seem to be using my GPU.  Heck, even the transcode folder was acting up and using the docker image instead of /dev/shm.  Took a reboot of the entire server to fix the folder issue.  GPU still not working though.

    Edit: Looks like if I restart the container, the Transcode folder issue comes back.  I have to restart the whole server to fix it and nobody can watch without buffering.

    Edit2: Rolled back to 1.30.1.6562-915986d62-ls148 - same issue.  Trying a different nvidia driver version.

    Edit3: Tried latest production branch driver and same issue.  Plex is using CPU & Docker Image for transcoding.  Seems to be a Known Issue

  3.  

    I seem to be getting an incompatible version error when connecting.

    Most of the posts on here involved restoring from backup, but this is a brand new server.  I have even deleted the "worlds" folder so it recreates it.
     

    I do have 'validate' enabled to make sure the files are correct.  Ports are forwarded, the server shows up on the main list.

     

    I've attached the logs.  

    Edit:  Ignore this.  I had "valheim plus" enabled in the settings.  Once I disabled it, I could connect to the server again.  

     

    ValheimLogs.txt

    • Like 1
  4. 16 hours ago, andrew207 said:

    If you have your indexed data stored in the container rather than on an external volume this will accentuate your docker.img disk usage.


    Hi, thank you for looking into this.  Just for clarification:

    My indexes were stored on /splunkdata (mapped to my disk pool on Unraid).


    image.png.8abbc145baaecae17c08365ad29ddc1b.pngimage.png.2afce4b3d3973ab3123334fe8e918fcb.png

     

    Where does the image build script download/untar the installer to? Maybe that path needs to be mapped externally as well.
     

  5. 22 hours ago, John_M said:

    You could try narrowing down the problem by running only some of your containers for a while. With the various tools and charts you've shown you should be able to eliminate several of them quite quickly.


    I did some considerable digging.  It ended up being the "splunk" container.  
    This was determined by doing a "force upgrade" and seeing the behavior after a restart.  The docker image usage spiked every time that action was performed.

     

    After that, I shutdown docker, deleted the vdisk, and recreated (as XFS since this was a good opportunity to move off BTRFS) and re-imported my templates (except Splunk).

    The usage has been exemplary now.  

     

    Thank you to everyone who offered support.

  6. On 1/18/2021 at 1:51 PM, Mervin said:

    First, thank you for creating this! It's super smooth!

    I'm not sure if the issue I'm experiencing is due to something I'm doing wrong related to this splunk docker or if it is just a coincidence, but I notice it specifically here so figured I'd start here.

     

    Any time I adjust ports or change paths on my splunk docker config my total used docker image storage goes up by a few gigs. Despite this, the container sizes stay reasonable. I searched around the internet a bit, and found info on pruning, but that doesn't seem to do the trick. I deleted all my containers, and the seemingly zombie used storage remains behind. After deleting the docker.img file, and rebuilding all containers the size is again reasonable, but each time I change settings on the splunk container it rises and space is not returned to free.

     

    I assume there is something obvious I have not yet learned in regards to Docker, but my searches thus far have not lead me in the right direction. Is there anything obvious that jumps out at you @andrew207? Thank you so much for your help!


    Hi, did you ever find a solution to this?  I seem to be having issues with this container using up docker image space as well.
    I can easily replicate it by doing a "force upgrade" on the container itself.

  7. 22 minutes ago, jonathanm said:

    Have you matched what's in the mappings to the internal configuration of each app? If the app is set to write to /Downloads and the mapping is /downloads you will end up writing to /Downloads inside the docker image.


    NZBGet is the only application that downloads anything.  It's been working fine over over a year.
    Anytime I select a path, I choose it through the drop down so anything case-sensitive is preserved. 
    image.thumb.png.8141d39b711f53ca5aa906b654b07c8d.png

    image.thumb.png.ce3c0b43eadd4b54a7a5e058833f8a01.png


    Reslio is another App that pulls data in occasionally:
    image.png.0f262251c75d55bfe66069f2b2bda935.pngimage.thumb.png.4052e789dbffa580089d6a2d9ef7375d.png

     

    Plex (mostly default settings)
    image.thumb.png.54ccbddd33f6963420c9fe7394f2081a.png

    image.png.9ea38ce2624f9789e3daf27abe51dc83.png


    Splunk:

    image.png.53000c24bae6c57c543f530d9bd3d4f2.png

    image.png.2bde167831c0febe771a16ee35616a84.png

     

  8. 9 hours ago, John_M said:

    You probably have a bad mapping somewhere and one of the containers is storing files internally instead of externally. You could try looking at the docker run command for each container.

     

    I've gone through all my mappings and they seem correct.  They all are defined based on the template, docker run shows the prefixed "/"

     

    Output of Command:

    du -h -d 1 /var/lib/docker/

    image.png.e8033a20eef737bafc80cb21bf7af85d.png

     

    I've also been running the following command to see file size changes

    docker ps | awk '{print $1}' | grep -v CONTAINER | xargs -n 1 -I {} sh -c "echo -e \\\n#================\\\nDocker container:{}; docker exec {} du -hx -d1 / "

     

  9. Hi, 

     

    I've been trying to track down my docker image usage. 
    I haven't found much in the way of rhyme/reason on how it's getting larger.  Seems to be about 3% at a time though.

     

    • System Version: 6.9.1
    • System Memory Usage:
      image.png
    • Docker Information:
      image.png.8bfafb102dd685203ee2f84aed33e46a.png
    • Docker Settings:
      image.png.07f851e01ba749eef06eb642bce9ea77.png
    • All docker containers have a "/" prefix before their path
    • Log rotation is enabled
    • Container size output:
      image.png.f8baec12b2890a1f896a415f08ea1a83.png
    • Output of command
      du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60
      image.png 
    •  Output of command
      find /var/lib/docker/containers/ -type f -exec du -Sh {} + | sort -rh | head -n 15

      image.thumb.png.fdb8dd255f14871b7ea09b1722b93587.png

    •  Output of command
      docker system df -v
      image.thumb.png.723cd09697f845631c50efa38c3de6c9.png
    • I've been using this to find the largest folders on some containers
      du -Sh | sort -rh | head -5

       

    • I've been using this to find the largest files on some containers 
      find -type f -exec du -Sh {} + | sort -rh | head -n 5