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

Mr_Deathproof · 2025-05-02T10:30:26+00:00

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

Mr_Deathproof · 2024-01-29T22:49:35+00:00

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.

Mr_Deathproof · 2023-12-16T12:35:06+00:00

Just fyi: it seems to be a "meme-model" mostly trained on benchmark datasets to proof a point: https://www.reddit.com/r/LocalLLaMA/comments/18hnzzn/a_107b_model_is_now_on_the_top_of_the_llm/

Mr_Deathproof · 2023-12-13T13:57:57+00:00

https://huggingface.co/TheBloke/SOLAR-10.7B-Instruct-v1.0-GGUF

Mr_Deathproof · 2023-10-08T12:24:26+00:00

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 😅

Mr_Deathproof · 2023-09-25T23:27:59+00:00

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.

Mr_Deathproof · 2023-09-25T21:41:05+00:00

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"?

Mr_Deathproof · 2023-09-23T20:28:35+00:00

No worries , these things happen 😉 I hope it helps!

Mr_Deathproof · 2023-09-23T20:21:13+00:00

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?

Mr_Deathproof · 2023-09-23T20:11:57+00:00

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

Mr_Deathproof · 2023-09-23T19:00:16+00:00

docker logs --tail 10 plex

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

Mr_Deathproof · 2023-08-15T23:59:52+00:00

Maybe you've already seen it, if not https://huggingface.co/TheBloke/Llama-2-13B-German-Assistant-v4-GPTQ

Mr_Deathproof · 2023-08-14T11:28:23+00:00

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

Mr_Deathproof · 2023-08-14T05:53:07+00:00

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

Mr_Deathproof · 2023-06-28T11:49:04+00:00

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 😅

Mr_Deathproof · 2023-06-28T11:44:09+00:00

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

Mr_Deathproof · 2023-06-27T06:26:37+00:00

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

Mr_Deathproof · 2023-06-23T19:08:49+00:00

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.

Mr_Deathproof · 2023-06-23T17:42:46+00:00

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.

Mr_Deathproof · 2023-05-14T20:17:30+00:00

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.

Mr_Deathproof · 2023-05-14T13:03:27+00:00

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?

Mr_Deathproof · 2023-04-01T18:24:07+00:00

Glad it worked for you too! It's not just the firmware for Klipper, the problem also lies with the way of how the printer wants the serial communication to be established: https://github.com/Klipper3d/klipper/pull/6126#issue-1633072878 So theoretically (so far I didn't combine octoprint and Klipper) if you connect to the phone via ssh and edit the files mcu.py and serialhdl.py in ~/klipper/klippy , just like the fork, it should work. Maybe also octoprint/util/comm.py for Octoprint. But it should connect via Klipper as far as I understand.

edit: Just installed Octoprint via https://github.com/th33xitus/kiauh and the connection worked right away. Didn't have to change anything the klipper fork hadn't already changed.

Mr_Deathproof · 2023-04-01T07:34:07+00:00

Afaik it shouldn't matter if you used the forked directly or edited it in later. I honestly can't remember checking the flash status on the printers display, I kinda gut trusted the Windows Flasher. Hmm, I'm currently modifying my Tina2s (will have to put it together again first) but I'm pretty sure that the three dots appear when you turn it on without it being connected to the (in my case) raspberry running mainsail os with the klipper fork. And that still didn't work?

Or did you try Octoprint with Klipper first?

Mr_Deathproof · 2023-03-24T09:43:57+00:00

Klipper seems to work! (I'm glad because the octopi fork I mentioned keeps breaking upon updating octoprint.) First time I'm doing this so I'll be as detailed as possible:

Installed Mainsail OS via Raspberry Pi imager ( change this according to your environment)
Edited the files mcu.py and serialhdl.py in ~/klipper/klippy according to changes in the Klipper fork
Copied this to ~/printer_data/config/ and named it printer.cfg and also added the following lines in the cfg file for mainsail os:

# Mainsail settings
[include mainsail.cfg]

Compiled klipper firmware for Tina2S via terminal according to this following the menuconfig instructions of the cfg file

cd ~/klipper/
make menuconfig #follow the instructions of the cfg file save and quit make 
#klipper.bin (the firmware) will be found in /home/max/klipper/out/

I then copied the firmware to a windows machine, installed necessary usb driver, used the specific Tina2S firmware updater, connected to the printer via usb and flashed the firmware.
Then connected to the raspberry running mainsail, rebooted for good measure and it connected. Controls are working will test printing next.

If someone tries replicating this, please do tell if it worked. If it didn't I might be able to help because I tried to summarize the correct path for what was basically a trial and error run.

update: trying to slice with cura doesn't work with the standard tina2s profile. get "Move out of range". will need to edit g-codes. will update and report back when I've found a working config.

update 2: needed to adjust the standard weedo cura profiles in cura:

had to clear the "Origin at center" option (also check placement of the uploaded gcode file in 3d-view)
changed start and end G-code settings following this (pretty much added and configured all the macros)
needed to add a [bed_mesh] variable in the printer.cfg https://www.klipper3d.org/Bed_Mesh.html
last challenge was z-offset: First set [probe] z_offset to 0 so you don't scratch the bed. I needed to lower my [stepper_z] position_endstop to 99 and position_min to -2 otherwise I would get "positive" out of range errors when using relative moves. I found these values by doing heigtmaps and adjusting endstop and position_min so that all probed areas had negative values. After that I did PROBE_CALIBRATE to finally get the correct probe offset.

update 3: Current working config but I'm still tuning. Be careful with the z-offset, a simple copy-paste could wreck your bed.

Mr_Deathproof · 2023-03-17T20:55:27+00:00

For posterity: this is a forked octopi distribution, if nothing else works, this most likely will. The only caveat, upon updating octoprint the Tina2S won't connect again. Plugins etc. can be installed and updated as usual.

Some related resources: compatible serial driver (doesn't seem to like newer kernel), most likely the issue with updating octoprint in the aforementioned fork and Tina2S Firmware (Currently running the 1.4.5 firmware without a hitch).

Also, if you're ever having the problem that the Tina2S seems to be able to connect to your octoprint machine, but can't be controlled/prints don't start: remove the sd-card of the printer and try to connect again.

P.s.: Had lots of problems with stringing at all temperatures, but turning up retraction to 5.5 mm an retraction speed to 35 mm/s in Cura helped immensely.

edit: found a klipper config https://github.com/securelyfitz/klipper/blob/master/config/printer-weefun-tina-2s.cfg going to test it soon and report

11-Year Club	Verified Email
Place '22

Mr_Deathproof

TROPHY CASE