#Running kometa stalls and causes computer freeze
1 messages · Page 1 of 1 (latest)
You can press the "Close Post" button above or type /close at any time to close this post.
Hey guys!
Basically I followed the config updates (I hope I haven't missed anything) but when I run it, it freezes in the same part: "Downloading IMDB Interface: 96.60%"
I attach my current config:
Also my computer froze to the point I had to hard reset
📝 If you want to review this again, rafa130397:
: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> 📝
Using Asset Directory: config/assets
Connected to server rafa-mini-pc-ubuntu version 1.32.5.7349-8f4248874
Running on Linux version 6.2.0-34-generic
Plex DB cache setting: 40 MB
PlexPass: True on Public update channel.
Scheduled maintenance running between 2:00 and 6:00
Connected to library Movies-Test
Type: Movie
Agent: tv.plex.agents.movie
Scanner: Plex Movie
Ratings Source: Rotten Tomatoes
Movies-Test Library Connection Successful
📝 If you want to review this again, antwanchild:
: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> 📝
Use Kometa caching where possible: https://kometa.wiki/en/latest/config/settings/?h=cache#cache
Run Kometa after PLEX scheduled tasks so 5am is a good time for that since PLEX runs scheduled tasks between 3-5am
Consider Database Cache Size (MB) settings in PLEX under Settings, Library, Database Cache Size (MB). 2GB = 2048MB or set it in Kometa config.yml file: https://kometa.wiki/en/latest/config/plex/?h=db_cache#plex-attributes
Look into using the ChuckPA dbrepair tool to deal with plex db issues/fixes(He is an employee of Plex)
:one: - remove video thumbnail creation on your libraries (Plex Web UI settings for the Library under Advanced)
:two: - remove credit detection on your libraries (Plex Web UI settings for the Library under Advanced)
:three: - remove intro detection on your libraries (Plex Web UI settings for the Library under Advanced)
:four: - Ensure that other apps that touch Plex do not coincide with each other. Think of TCM, Plex Autoscan, Refresh Metadata, Plex Maintenance
At the end of the day, everyone's system will have different performance characteristics. Some have to implement all of these before MOST of the Busy DB Sleeping 200ms issues go away.
all i can see is that the log suddently ends, so something outside of Kometa is killing it
the only thing in your config that it's correct is reapply_overlay, it should be reapply_overlays but that's not going to kill your run
what are you running kometa on?
If you’re not running with the —run flag, the script starts and waits to run the operations until 5am by default
The script ran fine at that time
Its just that it gets killed
I am running in docker
Please use codeblocks when posting things like that rafa130397, here is your message with codeblocks applied to it. pmm: <<: [*common-restart-policy] container_name: pmm image: kometateam/kometa:latest user: '${USER_ID}:${GROUP_ID}' environment: - TZ=${TIMEZONE} - PMM_CONFIG=/config/config.yml - PMM_TIME=18:00,06:30,21:33 - PMM_RUN=false - PMM_TRACE=false - PMM_OPERATIONS_ONLY=false volumes: - ${ROOT_DIR}/${CONFIG_DIR}/pmm:/config depends_on: - plex
The log ends here: [2024-04-29 20:58:42,019] [operations.py:815] [INFO] | Processing Masters of the Air S01E01 |
Did you kill it because it froze?
what was plex doing at the time?
Nothing
something happening outside of kometa that is causing Kometa to fail.
have you looked to see what else the computer might be doing when Kometa is running?
I blame OOM
usually if a log ends abrutly it means i was killed by OOM
increase the amount of ram you have as you are likely running out of memory and its being killed
oh yeah, i hate OOM
have enough memory and OOM wont be a problem. or if on a budget use swap space
What is oom?
Also, it now continued but it is taking sooo long
And this is a test library with 2 movies and 2 tv shows
Out of memory
Are you running anything new on docker that you weren’t previously?
Check system monitor when Kometa is running to see if CPU/RAM are maxed
47 min in took to run
So it completed this time?
my runs take at least an hour
@mossy rampart not sure what the issue is to be honest? the start of your run, to where the logs end is only 3 minutes long
It compelted this time yes
can only go off the logs
The issue right now is just that it took way too long and I notice plex is slower
post logs
Sure
but to me it sounds like a memory issue
📝 If you want to review this again, rafa130397:
: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> 📝
there wasn't any code changes what would affect performance
that is why it is so weird
on the recent run, your runtimes were normal
it usually takes 20 mins
and this was tried on a test library
so it was even a smaller
could it be because it was a new library?
And when I run it normally there is no posters to apply?
you were apply overlays on EVERY item, which can be expensive
Exacrly
And what about plex performance?
I noticed somebody else posted about this as well
you would have to look at your plex logs
!afnh
Anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.