#fizzyelf0863 needs assistance. Invoked by bullmoose20

1 messages ยท Page 1 of 1 (latest)

copper juniperBOT
#

fizzyelf0863, please continue the conversation here.

Content: How would one get rid of these warning? Back when I set it up a few months ago, I think I remember something about radar/sonarr that can be added to avoid these, but I could be misremembering. I didn't have either at that time so I didn't really look into it.
Is that something that can be avoided without adding use_<SOMETHING>: false manually?

Attachments:(if any)

#

Welcome @minor osprey!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

peak plinthBOT
#

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ยฏ\(ใƒ„)/ยฏ

Log file too big? USE PASTEBIN or ZIP THE FILE

unique nacelle
#

we need logs, but those overlays really have nothing to do with radarr / sonarr.

#

@minor osprey uparrow

copper juniperBOT
#

๐Ÿ“ If you want to review this again, fizzyelf0863:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐Ÿ“

unique nacelle
#

@minor osprey most of those have nothing to do with radarr

#

you can either not use those editions or ignore the error

minor osprey
unique nacelle
#

yep, i get some of those, cause some of those editions are pretty rare as in you only have one option

minor osprey
#

Do you see anything that can be changed in the config to eliminate anything else?

unique nacelle
#

not that i can see now

minor osprey
copper juniperBOT
#

๐Ÿ“ Great! Let's start to review and make recommendations, bullmoose20... ๐Ÿ“

#

๐Ÿ“ If you want to review this again, bullmoose20:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐Ÿ“

light egret
#

@minor osprey the last 3 recommendations could be addressed

minor osprey
minor osprey
#

Does it have an expiration time or something?

copper juniperBOT
#

๐Ÿ“ Great! Let's start to review and make recommendations, fizzyelf0863... ๐Ÿ“

#

๐Ÿ“ If you want to review this again, fizzyelf0863:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐Ÿ“

#
**Rec 04** - ๐Ÿ’ก๏ธ**PLEX DB CACHE ADVICE**

๐Ÿ’ก๏ธPLEX DB CACHE ADVICE
Consider updating the Plex DB cache setting from 0.04 GB, to a value greater than 1 GB based on the total memory of 31.00 GB.
For more info on this setting: https://metamanager.wiki/en/latest/config/plex.html#plex-attributes
NOTE:The number you choose can vary wildly based on a number of factors (such as the size and number of libraries, and the amount of files/operations/overlays that are being utilized).

light egret
#

1 hour of inactivity

minor osprey
#

Yep just generated a new one, thanks

light egret
#

everytime you change pages, the 1 hour timer restarts

minor osprey
#

4096 is a decent option I guess?

#

Oh I had it empty

light egret
#

start with 1024

#

default is 40 MB

#

1024 makes it 1GB

#

the default is set by PLEX

#

blank from a PMM perspective means only read the value

#

if you set it in PMM, then it will set that value

minor osprey
# light egret start with 1024

How would I know if increasing it could improve or worsen things? Just to see how it works and see if it makes things slower/faster I guess?

#

And to see if it affects other processes? I think 4GB should be fine as well, my RAM usage is quite low in general because I don't do much on it

#

The question is I guess how much improvement one sees with going 1GB to 4GB

light egret
#

its really hard to say... lots of different factors

#

what is the size of your plex db?

#

if its less than 1GB, no need to go to 4096

#

however, setting it to 4096 wont mean much as it wont get reserved from what I have seen in the mem usage of PLEX

minor osprey
light egret
#

think of it this way... if your DB is 100MB, and your cache is 40MB, then it means that only a part of the DB is cached and you could suffer some performance issues

#

if you can fit all of your DB into the cache, that is optimal

minor osprey
#

Does this file look right?

#

I think so

light egret
#

110MB

#

so bump db_cache to 1024 is fine and youd have room to grow

minor osprey
#

Actually could be more

light egret
#

those are not all "active"

minor osprey
#

Based on this

thick coral
#

the date ones are backups

minor osprey
#

Yea I mean the top one

#

213 MB

light egret
#

which is still below the 1024MB

minor osprey
#

Yep just wondering which one is the actual one

light egret
#

you can quadruple the size of your Plex DB and still be OK

thick coral
#

did you happen to try a different plex image at one point?

light egret
#

top one

thick coral
#

like linuxserver io vs binhex

#

vs the official one

light egret
#

versus hotio

#

lol

#

so many

#

plex images

thick coral
#

some use different paths

minor osprey
#
/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases

vs

/Plex/Plug-in Support/Databases
#

The top location is 213MB
Bottom location is 110MB

thick coral
#

binhex uses this and hotio too

#

/Plex/Plug-in Support/Databases

light egret
#

timestamps?

thick coral
#

linuxserver io and official uses this path /Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases

#

but yes timestamps will be your best clue as to which one is the correct one

minor osprey
#

So the other one

light egret
light egret
#

^^ sorted by timestamp

light egret
#

or leave it and look at timestamps

minor osprey
#

So yea the databases folder in the shorter location path is old

light egret
#

Anything else needed here?