Support Doc for Database Cache Size (MB)?

$(grep docker /proc/1/cgroup | wc -l)" -gt 0 ] || [ "$(grep 0::/ /proc/1/cgroup)" = "0::/"

This line wasn’t working because I’m using podman.

This is what it returns if I manually cat:

cat /proc/1/cgroup
12:freezer:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
11:perf_event:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
10:hugetlb:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
9:cpuset:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
8:net_cls,net_prio:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
7:rdma:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
6:memory:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
5:blkio:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
4:devices:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
3:pids:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
2:cpu,cpuacct:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope
1:name=systemd:/machine.slice/libpod-3244a83ecff652b24bdd0f4f08ae4e6f174e59bec250db7d1d8be8ab49387fe3.scope

Care to join us?

To all following here:

Podman support has been added to the DBRepair tool.

Per-container rules still apply.

2 Likes

for some reason I can’t run this on my W11 system, my install is all in the default locations, i’ve checked all the variables in the batch file and all locations exist and are accessible but when i run it, it just stops after trying to export the DB with

the system cannot find the path specified

but the path in the file is correct. even tried with hardcoding the location

Make sure you have these set correctly, including the quotes:

set “PlexData=D:\Programs\Plex\Data\Plex Media Server\Plug-in Support\Databases”
set “PlexSQL=C:\Program Files\Plex\Plex Media Server\Plex SQLite”

As you can see, in my case the database is in a custom location, while SQLite is default. Also check Program Files vs Program Files (x86), depending on whether you’re running the 32- or 64-bit version of PMS.

Many thanks, I have checked and rechecked those locations and all are correct but still see the same error.

Did you check if the dbtmp folder gets created? (mkdir “%PlexData%\dbtmp”)

I’m getting exactly the same thing on WIN10…

image

Everything is in the default locations and I am running the 64bit version…

image

It seems its tripping up here…

I’m not entirely sure you can use pipe in the same way on Windows…

Yes dbtmp folder is created as is the log file but it stops in same place as axemanuk666 has shown

2 Likes

Can you guys try adding .exe at the end of Plex SQLite, here:

set “PlexSQL=C:\Program Files\Plex\Plex Media Server\Plex SQLite.exe”

That was one of the 1st things I tried…

1 Like

What about running the BAT file as admin?

Did it stop – AND – return to the command prompt

-OR-

did it sit there for a long time until you interrupted it ?

From looking at his screenshot, I’d say it just aborted right away by itself.

Same thing…

Stops and immediately returns to prompt…

I wrote this in Win10 VM and several people checked it.

How can windows be different from machine to machine
when those two variables are defined ?

I tested this with Chuck a few weeks ago, and I was able to run the script successfully on Server 2016. All I had to do was adjust the paths.

It’s choking on this…

echo .dump | "%PlexSQL%" "%PlexData%\com.plexapp.plugins.library.db" > "%DBtmp%\library.sql_%TimeStamp%"

As I said earlier, I’m not entirely sure you can use pipe like that on Windows.

I’m happy to do a remote AnyDesk session with you if you want to use my machine as a test bed.

Windows has allowed pipes like that since Win 95 ( remember that much haha)

Ah, OK :+1: