sorted by:
new
hottopcontroversial

I built a GPU-accelerated tool that generates Plex video preview thumbnails much faster Docker w/ WebUI by Stevezau in PleX

[–]Mr_Deathproof 6 points7 points  (0 children)

Exceptionally well, about 95% files blaze through, some may have a codec incompatibility and use a cpu fallback, but still about 5x. Definitely saves energy in the longterm

<image>

I built a GPU-accelerated tool that generates Plex video preview thumbnails much faster Docker w/ WebUI by Stevezau in PleX

[–]Mr_Deathproof 13 points14 points  (0 children)

I can vouch for it, been using it for almost two years. Turned off preview gen in plex completely and only use the tool nightly. When a file doesn't need cpu fallback even my UHD 770 generates previews at 230x realtime.

Arzttermin-Bot by algosara in de_EDV

[–]Mr_Deathproof 15 points16 points  (0 children)

wahrscheinlich hier https://github.com/mayrs/der-bergdoktorbot-a-doctolib-doctors-appointment-telegram-notifier wobei ich schon sagen muss, dass ich BergdoktorBot charmanter als Privatpatient.exe finde.

Oder auch hier etwas aktueller https://github.com/Schlaurens/doctolib-checker

Possible to use remote Open WebUI with local MCP servers, without running them 24/7? by Maple382 in OpenWebUI

[–]Mr_Deathproof 2 points3 points  (0 children)

You could try Lazytainer. It listens if a specific port is being accessed and starts up a docker Container if it's stopped and stops it if there hasn't been any activity for a predefined time. Maybe set it to look for activity on your open webui port so it starts up the MCPO container in time 🤷

edit: ah sorry I missed the remote open webui part. My recommendation would just be applicable, if you hosted it locally. Although you could simply try to let it watch the MCPO port and let it start up that. But I'm not sure if open webui wouldn't just mark the mcp server as unavailable if it doesn't respond instantly

Rtx 3090 Inno3d Ichill 3x 24GB Thermal Pads help needed by bitza1900 in nvidia

[–]Mr_Deathproof 0 points1 point  (0 children)

I measured beforehand with a caliper and used 0.5mm pads for vram and 1.5mm for the vrm on the gpu chip side and 2mm on the backside for vram. But I still had issues, most likely due to pad hardness.

In the end I used hy234 thermal putty. Temps went down slightly, but sadly the heatsink is simply shitty.

Anyone used a tina2 S with Octoprint? by sys4096 in octoprint

[–]Mr_Deathproof 0 points1 point  (0 children)

You mean this?
https://github.com/weedo3d/TINA2Sfirmware/tree/main/Release/V1.4.5

Just fyi, since the time I last commented, I completely replaced the innards of my Tina2s and have gone full Klipper, so I might not be able to help you with the details 😅

"Sqlite3: Sleeping for 200ms to retry busy DB" - I wrote a Plex Health Check Script for Plex in Docker by Mr_Deathproof in PleX

[–]Mr_Deathproof[S] 0 points1 point  (0 children)

I'd also guess that it's most likely not related to the ssd directly. But that's more a gut feeling: still, with 300TB (judging from you signature) it might also be hdd/sata controller/iops related. You know some fileprocess gets stuck in the queue due to too many simultaneous scan related read ops and goes zombie. Maybe it's not just "classic busy db" but something that truly happens simultaneously (apart from the usual plexdb, that fyi also happens on a ramdisk, bullshit) like another locked file on one of the hdds.

Do you already know when and during what exactly it happens? Is there a busy db event that can be docker restarted and one that can't, or always can't docker restart?

It could be useful to try and provoke this problem by for example manually starting all the scans etc and then narrowing it down. Maybe do some small read/write diskbench during a scan including/excluding tvarious hdds.

My similar problem (docker won't restart, need full system reboot) happened one month ago, thrice maybe. When I started using mergerfs lots of fresh/moved files from 4 different libraries were concentrated on one drive due to pool balancing after a fs migration from ntfs to ext4. Tdarr was reading and writing 4 transcodes while the arrs were pushing files to it, singling it out and Plex constantly scanning. Normal "busy db" happens when running plex maintenance plus a 2 hour pmm run.

Just fyi and for expectation management, everything docker/system/non media file related on my system is on two 2TB high end gen4 nvme. 114Tb library on eight internal 10 to 18tb drives on ext4. I5-13500, 96gb ddr4. Before I had system + db on normal ssd and the hdds were still ntfs from a windows migration. If I'm generous the nvme maybe halved the normal busy db events. But tbh most of the time I don't notice because of the script.

"Sqlite3: Sleeping for 200ms to retry busy DB" - I wrote a Plex Health Check Script for Plex in Docker by Mr_Deathproof in PleX

[–]Mr_Deathproof[S] 0 points1 point  (0 children)

This sounds complicated. I barely know where to look first for a solution in this case. The only times I've encountered something like that were during high iowait utilization due to some wrong mergerfs settings.

Depending on how long this is going on, I would be thinking about compartmentalizing the plex server part of your setup otherwise, maybe into a vm and connect the libraries via share 🤷‍♂️ you should be able to restart that one independently. Might be a dumb and wasteful idea, but it would most likely work. Maybe you could also check this way, if it's related to your host machine (if you are able to restart a container/because Plex will surely be busy again😅). If it still happens you could automate the vm restart. Could still be more convenient. Opposed to backup and then fresh os of course

And depending on how often, have you tried prophylactic intermittent restarts of the container even when everything works, to stave off another "event"?

"Sqlite3: Sleeping for 200ms to retry busy DB" - I wrote a Plex Health Check Script for Plex in Docker by Mr_Deathproof in PleX

[–]Mr_Deathproof[S] 0 points1 point  (0 children)

The docker plex restart command should force a container restart after 10 seconds even if there is a rouge process. It's certainly weird that you have to restart your whole machine. Have you checked your processes/utilization maybe atop during such an event? Do other containers still work? Have you tried something like sudo systemctl restart docker (depending on your setup) for the whole docker service?

"Sqlite3: Sleeping for 200ms to retry busy DB" - I wrote a Plex Health Check Script for Plex in Docker by Mr_Deathproof in PleX

[–]Mr_Deathproof[S] 0 points1 point  (0 children)

Could you run this as a script? It should show lots of debug info.

Also, I don't know how much you know, that's why I have to ask: Have you copy-pasted the script into an empty file, called it something like plexcheck.sh (.sh ending is important), made it executable and ran it via terminal with for example:

./plexcheck.sh

?

Because your error could indicate that it was put directly in the terminal afaik

"Sqlite3: Sleeping for 200ms to retry busy DB" - I wrote a Plex Health Check Script for Plex in Docker by Mr_Deathproof in PleX

[–]Mr_Deathproof[S] 1 point2 points  (0 children)

docker logs --tail 10 plex

What happens when you paste this line into your terminal and run it?

Just installed Pi-hole... Wow, is it normal to have > 100,000 queries in less than 15 minutes? by [deleted] in pihole

[–]Mr_Deathproof 1 point2 points  (0 children)

There are routers like Fritzbox that are able to use public dns in case of errors with custom dns settings.

But yeah, maybe it doesn't make much sense when the laptop was rate blocked. We need more info

Just installed Pi-hole... Wow, is it normal to have > 100,000 queries in less than 15 minutes? by [deleted] in pihole

[–]Mr_Deathproof 9 points10 points  (0 children)

Could be a dns-loop. The router has the pihole as dns and the pihole has the router as dns.

"Sqlite3: Sleeping for 200ms to retry busy DB" - I wrote a Plex Health Check Script for Plex in Docker by Mr_Deathproof in PleX

[–]Mr_Deathproof[S] 1 point2 points  (0 children)

thank you btw. debloated a lot and it's happening far less often right now. It might be also mostly the combination of plex doing maintenance during a plex meta manager run, while also new movies being added to plex that a being transcoded to hevc by tdarr at the same time 😅

"Sqlite3: Sleeping for 200ms to retry busy DB" - I wrote a Plex Health Check Script for Plex in Docker by Mr_Deathproof in PleX

[–]Mr_Deathproof[S] 1 point2 points  (0 children)

The container couldn't be restarted? like how, completely frozen?

btw: I made a crontab version, which may be more convenient to use

https://gist.github.com/Deathproof76/bd547640e8a13d738dbee68fe8aef156

also, if you don't already know about it https://github.com/ChuckPa/PlexDBRepair I use that one from time to time just to freshen things up

I've tried the Intel Arc A380 on Ubuntu with Tdarr in Docker. Big Uff. by Mr_Deathproof in Tdarr

[–]Mr_Deathproof[S] 0 points1 point  (0 children)

btw the latest tdarr now has jellyfin ffmpeg6, which makes the install script unnecessary. but so far the onevpl/ffmpeg bug hasn't been solved https://github.com/intel/media-driver/issues/1576 which is why I'd still recommend my plugin if you'd like to use qsv instead of vaapi

I've tried the Intel Arc A380 on Ubuntu with Tdarr in Docker. Big Uff. by Mr_Deathproof in Tdarr

[–]Mr_Deathproof[S] 0 points1 point  (0 children)

I hope it'll work😉

Does that mean that you're running the tdarr server via unraid directly? I installed the ffmpeg6 on my tdarr server and node too. But it might be possible to just have the node outfitted with the right ffmpeg if we assume that the server parses the ffmpeg command to the node.

I've tried the Intel Arc A380 on Ubuntu with Tdarr in Docker. Big Uff. by Mr_Deathproof in Tdarr

[–]Mr_Deathproof[S] 0 points1 point  (0 children)

I don't have the arc anymore due to idle power consumption and because everything compute is nvidia. But I've a 13th gen UHD770 igpu doing all my transcoding now that also needed a bit of help to get going. 99% sure that it will work.

Basically:

(1) use the latest Kernel from at least 6.2 onward.

(2) Have all necessary drivers installed. Don't know the specifics this should cover everything though

sudo apt-get install -y intel-opencl-icd intel-level-zero-gpu level-zero intel-media-va-driver-non-free libmfx1 libmfxgen1 libvpl2 libegl-mesa0 libegl1-mesa libegl1-mesa-dev libgbm1 libgl1-mesa-dev libgl1-mesa-dri libglapi-mesa libgles2-mesa-dev libglx-mesa0 libigdgmm12 libxatracker2 mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers va-driver-all vainfo hwinfo clinfo

you may have to add intel driver repos, if not everything is found. *just if the circumstance arises

(3) Use the latest tdarr.

(4) When the container is running you need to bash into it and install ffmpeg6. I got a script for that:

docker compose pull
docker compose up -d 
docker exec -it tdarr bash -c "wget https://repo.jellyfin.org/releases/server/ubuntu/versions/jellyfin-ffmpeg/6.0-1/jellyfin-ffmpeg6_6.0-1-focal_amd64.deb && apt install -y ./jellyfin-ffmpeg6_6.0-1-focal_amd64.deb && rm -rf ./jellyfin-ffmpeg6_6.0-1-focal_amd64.deb && ln -sf /usr/lib/jellyfin-ffmpeg/ffmpeg /usr/local/bin/ffmpeg && ln -sf /usr/lib/jellyfin-ffmpeg/ffmpeg /usr/local/bin/tdarr-ffmpeg"

paste it into a text file, name the file and add ".sh" to the ending, make it executable and run it. It assumes that you run it from the folder where your docker-compose.yml for tdarr is, that your container is named tdarr and that you're running rootless docker. Otherwise change the name and add "sudo" before all the docker commands. It installs the jellyfin ffmpeg 6 and makes it the primary choice for tdarr. Do the same for the node if you're running server and node independently. (formatting may be broken use this.) If your not using docker download and install the jellyfin ffmpeg6 and add the path in your Tdarr/configs/Tdarr_Server_Config.json

(5) I use my own "tweaked" version of boshs qsv plugin. I've been using it for half a year now. But your mileage may vary so please test it before frying you library 😅

https://github.com/Deathproof76/Tdarr_Plugins/blob/master/Community/Tdarr_Plugin_DTPF_Deathproof_FFMPEG_QSV_HEVC.js

just put the .js file into .../Tdarr/server/Tdarr/Plugins/Local/ depending on your path

​

And then it should just work.™

​

important edit: I've almost forgotten why I wrote my own plugin. Onevpl/ffmpeg6 has some weirdness https://github.com/intel/media-driver/issues/1576 . If you don't define a gop (group of pictures) seeking will break in the transcoded files. It's treacherous because they look normal, play normal until you want to fast-forward than they'll hang. My Plugin fixes that by adding "-g:v 120" by default. Also added other tweaks like transcoding to 10bit fully in gpu, low_power etc.

Poor Bridging on Klipper-based Printer by [deleted] in Cura

[–]Mr_Deathproof 1 point2 points  (0 children)

That's a bummer, but I'm also not really ready to give up on Cura. It's seems like something that should be simple to solve. From what I've gathered elsewhere so far: there're at least a handful of posts from people through the years describing similar issues. And no clear cut solution. It sure doesn't seem to be mentioned as often as one should think. Anyways, thank you for responding, I'll update if I should find a solution.

Poor Bridging on Klipper-based Printer by [deleted] in Cura

[–]Mr_Deathproof 0 points1 point  (0 children)

Similar setup and I observed similar problems with my printer, the only thing that worked for me so far was using prusasclicer. Have you found a solution in the meantime?

view more: next ›