Support Doc for Database Cache Size (MB)?

[ChuckPa]

@xInsertx

anyways - my cache size is 1gb (64gb system on zfs - plex instead on ssd - media on hdds) and did it make a noticeable performance difference on playlist and filters.

Cache size?

The DB is either a WAL or SHM ?

To which do you refer please ?

If you’re referring to the ‘Cache’ directory , those will grow at sometimes alarming rate. I use cron to periodically prune at MY desired rate

[Kp10031]

Hey chuck.

I get this, cat: /proc/1/comm: No such file or directory

Im not sure i understand what you mean by which native package?

I just git pulled to my script dir, and edited the DBRepair.sh, tried both to edit it the docker and native linux paths. To no avail.

I have read the README.MD several times, not sure i fully understand completely though… :S

I asked on the Seedbox discord, and he answered with,

1. 5. Elevate privilege level to root (sudo)

2. That should tell you why:)

So i guess it needs sudo which i dont have on my seedboxes…?

[ChuckPa]

Here’re the definitions:

1. Native package - The software runs on the base (normal) OS which is installed on the host

2. Docker Container - The software runs in a light abstraction from the OS (an artificial directory and username mapped environment) usually valid for one app only.

3. Linux Container (LXC) - The entire OS is abstracted, but not like a VM where the hardware is virtualized and multiple applications can run in there completely oblivious to the real OS the host is.

If they are telling you to

sudo cat /proc/1/comm

then I’m really curious because Linux must have a process #1 (what does the startup)

On Ubuntu (or any of the mainstream distributions), you don’t need elevated privilege (sudo) to look at it.

Observe

[chuck@lizum ~.1999]$ cat /proc/1/comm
systemd
[chuck@lizum ~.2000]$ 

I will start looking for seedbox info. Is it inappropriate for you to share a few provider names so I can look at some?

[Kp10031]

Hi Chuck.

Then you really are curious, because the cmd doesnt give any output.

I tried to do the sudo cat /proc/1/comm & cat /proc/1/comm for you again to no avaíl.

I did a screenshot for you so you can see.

Would be cool if you start looking at some seedbox providers, as most shared seedboxes dont come with sudo rights for good reasons.

Personally im using, edited out.

Plex is running in docker i think.

But it doesnt matter as long as the script requires some form of sudo i think.

Or i can ask them for you if you would like?

[wyldemusick]

I’ve used EVO Seedbox (https://EVOseedbox.com) and Rapid Seedbox (https://www.rapidseedbox.com/) along the way. There’s also https://seedit4.me/ which I’ve looked at but passed on for the moment.

[Kp10031]

Any updates on this for the Seedbox community?

[ChuckPa]

I have not made any advancement on “Seedboxes” which are native installations.
( I need to see / explore on one to see what it has. )

@Kp10031 if you want to have that conversation , it’s graciously appreciated. The folks at UNRAID were kind enough to grant a license for Plex support.

Since I last updated here:

1. New PlexDBRepair code is complete
2. Updating documentation nearing completion

What’s changed:

1. The whole GUI changed
   – Command # or Command NAME (or abbrev)
   – Commands now ordered in the most commonly-used sequence
   – Timestamped output when running in scripted mode

2. Can start/stop PMS on most of the supported platforms (at this point)

3. Better safeguarding against running out of space while operating on the databases (checks to confirm it has plenty of space before each operation)

4. Last, but by no means least, “automatic” mode.

Please follow up in my development thread for the latest news…

I’ll post the ‘beta’ there before making the final release on GitHub

[Kp10031]

Okay, so now i atleast get this Error instead, Unknown host. Currently supported hosts are, QNAP, Synology, Netgear, Mac, ASUSTOR, WD (OS5) and Linux Workstation/Server…

Probably because the paths on a seedbox doesn’t add up to a normal linux installation, plus, i know on my provider, that Plex should be a Docker install like most apps…

Would it help you out if you know what paths Plex are using on the seedbox for the different Dirs?

Like:
/home31/xxxx/.config/plex/Library/Application Support
/home31/xxxx/.config/plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases
And i also have a Plex procces in, /usr/lib/plexmediaserver/Plex Media Server

I will make a ticket with staff tommorow, im almost certain they will lend you a small box for testing purposes. If not, you may lend my server where my test Plex is on

Talk to you later.

[ChuckPa]

Maybe we can arrange for some mobile-mobile chat time and a teamviewer session where we work together to figure it out?

(tonight is quiet for me. I just posted the “beta1” in the other thread)

Yes, knowing directories OR which PMS ‘package’ you’re using tells me 99% of what I need (I’m the linux packaging guy )

Is it DPKG or RPM based?

I have an idea what’s happening but what’s important for me is to figure out how to DETECT the box I’m on – then load any customizations (if supported) by the box.

[Kp10031]

Was already in bed, Europe based, so that’s a bit of a challenge.

I can’t find the “Other thread”…? :S

I just made a support ticket, asking if they would be willing to let you have a Box for testing purposes, for a limited amount of time ( A month or two maybe? Should do it, right?). To get the DBRepair tool to run in a seedbox environment.

I also asked them what Plex Package we use on my provider.

If they won’t lend you a small box, we can use my “Test Box” on there, and do a Teamviewer session for sure, no problems.

You will hear from me as soon as i hear from support.

[ChuckPa]

PlexDBRepair development

Folks, I’m going to take a plunge, drive a stake into the ground and offer “v1.0.0 BETA 1” for your consideration. I do this because it feels mature at this level of development I am bumping to 1.0 because most of the code has been rewritten (consistent with software development rules about bumping major version number) Documentation is coming along. The README is still rough but new content is better structured. I expect cosmetic tweaks here and there. I also expect tweaking docker con…

[Kp10031]

Thanks.

@ChuckPa
Can you PM or email me?
Im gonna have a box for testing for you in 60 mins time i would think.

EDIT:
Box is ready for you.

[Tony_T]

Downloaded the bash script for 1.0.3
Exiting (99) does not give option to delete temporary work files.

[ChuckPa]

@Tony_T

Current is v1.0.4

Please try the ‘exit’ command form.

[Tony_T]

@ChuckPa

Please try the ‘exit’ command form.

ok, exit give option to delete, 99 does not (feature or bug?)

@ChuckPa

Current is v1.0.4

If I go to: GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases
and click DBRepair.sh
I get:

Plex Media Server database check and repair utility script.
Maintainer: ChuckPa
Version: v1.0.3
Date: 27-Mar-2023

[ChuckPa]

1. Version: v1.0.3 = OOPS Typo
2. '99 vs ‘exit’ isn’t clear enough – Thank you.

My intent is :

• 99 / quit = 'get out now - touch nothing
• exit = leave and clean up after yourself.

I’ll work on that.

We should continue discussion here:

PlexDBRepair development

Folks, I’m going to take a plunge, drive a stake into the ground and offer “v1.0.0 BETA 1” for your consideration. I do this because it feels mature at this level of development I am bumping to 1.0 because most of the code has been rewritten (consistent with software development rules about bumping major version number) Documentation is coming along. The README is still rough but new content is better structured. I expect cosmetic tweaks here and there. I also expect tweaking docker con…

[SilverSurfer-JM]

Hi Chuck, running PMS on a Synology version DS7. Downloaded the script, ran the optimisations (automatic) as per the instructions. All good, normal prompts detailing what it’s done. Within the script start PMS, Exit, but… going back to the Synology webif shows the package as stopped. Manually starting it isn’t possible, it looks to start then stops.
The only way back is to do a restore (thank you btrfs snapshots!!).
Any ideas? Permissions not resetting on the db?

[ChuckPa]

The normal sequence is:

1. Stop
2. Auto
3. Start

It will confirm PMS is started.

If you are concerned bout DB permissions (which means you didn’t run it as ‘ROOT’ user, you’ll have to manually use ‘root’ user to set PlexMediaServer:PlexMediaServer again as the owner.

[SilverSurfer-JM]

thanks Chuck. I have no concern about the permission on your script.

On my Synology, the default admin account is disabled. I run tasks under a different administrator account named ‘Stanley’ for example.
Logging in to Putty as ‘Stanley’, running the script and raising the permission with sudo bash allows everything to run, I did the stop, auto, start. The script tells me all is well at each stage and finally that PMS has started but if I check Plex it hasnt, I can see within Package Centre on the Synology, the server is trying to start but stops after 10 or 20 seconds.

Next try this morning was to enable the default ‘admin’ account. Log in to Putty under that and repeat. Same outcome.

I’m doing something stupid which is leaving the db under permissions that Plex cant start I think. Any pointers?

[ChuckPa]

@SilverSurfer-JM

Look at the instructions I show on GitHub for Syno

EXAMPLE: To install & launch on Synology DSM 6 / DSM 7

    cd /volume1/Plex    # use /volume1/PlexMediaServer on DSM 7
    sudo bash
    tar xf PlexDBRepair-x.y.z.tar.gz
    cd PlexDBRepair-x.y.z
    chmod +x DBRepair.sh
    ./DBRepair.sh

The important parts here:

1. sudo bash (gives you ‘root’ privilege regardless of username you signed in as
2. look at Sample interactive session in the README

If PMS fails to start after that,

1. Keep the ssh session open (might need it)
2. Go to the GUI and manually ZIP the ‘Logs’ directory and attach here.