#Ratings Overlay Run Times out and is Freezing Plex
1 messages ยท Page 1 of 1 (latest)
Welcome @lilac vapor!
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
Please provide a full log
@lilac vapor please stick to using one thread, let's use this one.
This is a connection to Plex which is timing out; there isn't anything Kometa can do about that except waiting longer.
Kometa is asking Plex to set the overlay label on the item, and Plex is just not responding.
BTW, that error above doesn't appear in this log. In this log the same error happens on Gravity Falls.
yes I did another run and provided the log for it
So the issue is with Plex? Actually the overlays is causing Plex to hang
once i stop the overlay run with Kometa, Plex starts working again. Otherwise during the process when it times out in Kometa everything stops working in Plex
The issue is the combination of Plex and Kometa. Overlays generate a lot of activity with Plex, so if Plex is busy or resource-constrained, it may have trouble responding.
All we can tell from this log is that Kometa attempted to contact Plex and Plex did not respond.
The funny thing is there is no activity in Plex when i do the run. no playback or scheduled tasks running
Kometa overlays do not generally cause Plex to become non-responsive.
You don't seem to have an outrageous number of overlays; nothing on the episode level. This seems to argue for resources constraints in Plex.
Is it possible it is a limitation of the API calls?
Unlikely; nothing you have here in terms of the Kometa config is remarkable.
If there's something else communicating with Plex, that could be an issue.
Tautulli?
but I tried shutting down tautulli as well and doing the run and same thing so that can't be it
The Plex Media Server folder is over 170GB and I'm running it on Windows but on a very high end PC
Is the Plex metadata maybe on slow or remote storage?
it's on an M.2 NVME
When was the last time you validated the integrity of the Plex DB?
DBRepair provides database repair and maintenance for the most common Plex Media Server database problems. It is a simple menu-driven utility with a command line backend.
DBRepair is run from a command line (terminal or ssh/putty session) which has sufficient privilege to read/write the databases (minimum). If sufficient privleges exist (root), and supported by the environment, the options to start and stop PMS are presented as well. (Some envionments require DBRepair to run as the 'root' user.)
You can learn more about this tool and download/use it on ChuckPA's GitHub Repository https://github.com/ChuckPa/PlexDBRepair
Also...
Why is yours???
what else did you do to the Kometa python folder in terms of names and files???
what is kometa-ratings.py?
Incomplete logs makes sense as you terminated the run early
You are hitting the 1000 requests per day limit for mdblist
You can increase your timeout to a larger number.
Trakt connection errors should be resolved
The run_order you have picked is suboptimal and should be fixed
Details on all that found here:#bot-spam message
thanks bullmoose so the imdb ratings are pulling from mdblist or omdb?
I noticed the issue is mainly with the imdb rating overlay
imdb is pulled directly from imdb
mdb_tomatoesaudience is pulled from mdblist and is subject to your api allowance
i just purchase an omdb api key for 1$ which should give me a 100,000 requestes per day
nice
but when i use the omdb api key i get an invalid key error
maybe see if there's a way to refresh the omdb key?
i've tried deleting the cache and starting fresh but still no go
not sure how else to refresh the omdb key
maybe just visit the website and do the generate API key thing again?
not sure if it will give you the same api key or generate you a new one
i've created a kometa-ratings as a separate folder just for the overlays config to run it separate from everything else as it takes a lot of time. only edited the path that's all nothing else.
it's different to a paid api. the free api works fine but the paid one doesn't weirdly
maybe get in touch with them
yeah I messaged, waiting for a response
so you reckon it's the 1000 limit which is causing the timeout?
No
Maybe look into running DB Repair
Kometa makes API calls to Plex which it is designed to receive, for some reason the API calls seem to be causing Plex to get hung up. There's nothing we can really do about that.
i'll try the DB Repair
Take a backup of your DB first just in case ๐
Kometa would not be a success if it wasn't for all the people that spend hours and hours of their personal time to help others out with:
:one: creating/updating/maintaining the Kometa code
:two: creating/updating/maintaining all of the posters
:three: creating/updating/maintaining all the yml files to create the overlays and collections
:four: creating/updating/maintaining all the wiki documentation
:five: handling all the support and installation requests
:six: moderating the discord community server for Kometa
:seven: creating/updating/maintaining the logscan and other Discord bot functions/tools
As such, if ever you have used any of the above over here, why not consider a small donation (one time or monthly) to help the cause?
Click here to help us out with a donation: https://github.com/sponsors/meisnate12
Let us know if you do donate and we will give you the sponsor role
Role given
So.... I need to understand how you are running things regularly....
For example, if you are running both at the same time, that's going to be the root cause of the db Locking up
Quick question what is this? It gives you this information based on the metalog?
No I never run everything at the same time
Yes it does. As long as it contains certain tracers in the file dropped here, luma takes care of the rest
I have 4 different config files, each run one after the other
So why have two folders? Have one and just have a different config.yml file
I tried that before but I forget the reason why it didn't work it
Something was clashing
That's the point... likely the situation you are facing is because multiple instances are hitting the plex db at the same time
How are you controlling the 4 separate runs?
Task scheduler but one after the other. Never at the same time
So how do you know a run ends? And then the next starts?
I am by no means a programmer and just working with the knowledge I have ๐
It's not about the start time and more about the end time of the active run which is variable...
Plus you need to avoid plex maintenance
And not sure if you run ImageMaid or other tools like TCM or Posterizarr
I'll send you what my task scheduler looks like. Each config has it's own folder. I've set it up in a way that it runs one after another.
Trending
Airing
Ratings
Collections
I've found conflicts for these when using the same folder with different config.yml but with separate folders they just seem to work
I don't use imagemaid or other tools
My runs for example can vary by 2-8 hours....it just depends.... sure, share the task scheduler please
What kind of Plex maintenance should I be avoiding?
Never seen that conflict as you describe. Maybe something we should look into
Plex runs their own maintenance between 2-5am. Which is why we run Kometa at 5 am by default.
You may have changed that time... I dunno
Ah yes yes I don't do the kometa runs during this
Yours is currently set between 4-5am which might not be enough for plex to finish what it needs to do....
When I get back I'll try the db repair maybe that will resolve everything, but thank you guys for your patience I'll keep you posted and I'll send you my task scheduler
I manually ran an optimize library and clean bundles and then tried the ratings run in kometa but no dice
I set it to 4-5am till I can figure out how to resolve this issue
By the way when the run hangs I get this message on Plex if anything is playing
Any plex server error logs ?
I'll simulate another one and send you the log
I'm puzzled why this involves renaming and perhaps modifying the Kometa source files.
I honestly can't remember what the issue was exactly, all I know is that once i did this, what I needed to be done at the time actually worked ๐
I can't for the life of me seem to get my paid omdb api key working on kometa...
if I PM you'll the key would you mind having a look as to why it isn't working with kometa?
Does the key contain a #?
no just alpha numericals
it's like a regular free api key
but when i put it in my config file kometa just comes back with invalid key
only the free unpaid key works
i've done the plex db repair, am doing another run on the ratings overlay. Let's see if it still hangs. Fingers crossed!
This is the email i got from omdb for the paid key
Do those links work?
yes the links work
The following was shared by @honest goblet and was automatically redacted by Luma as it may have contained sensitive information.
If you feel this message should not have been redacted, resend it with !noredact in your message to avoid redaction.
And the spacing in the config file matches this precisely? No extra characters or spaces?
omdb:
apikey: (redacted by Luma)
cache_expiration: 60
You have multiple configs, right? Are you editing the correct one?
yes precisley, no extra characters or spaces
doesn't work for any of them
Well, I can certainly try it.
but when i use a free key it works fine
great how can i PM it to you?
regular Discord DM
You probably want to take it up with OMDB; if I replace my key with yours I get the same error.
hmmm yeah was afraid of that
alright no worries, I've messaged them still waiting for a reply
thanks for trying
Stumped
If you are using the default ratings overlays, the rating should be pulled by the time the overlays are being applied.
If you are using the special-text to pull the rating at the moment the overlay image is generated, then sure, it might be implicated, but I wouldn't expect that to cause a timeout connecting to Plex, since all Kometa does with Plex in this situation is to upload a single image [regardless of the number of overlays on it] ad set a label on the item.
Can you provide a full log of the working and failing cases?
Can we move this to another thread instead of hijacking @lilac vapor post
Processing your request...
A message by Kometa Newbie (kometanewbie_94890) was moved to #1322727936939266068 message by Antwan
I moved your discussion to a new thread
I feel like @lilac vapor and @jaunty mural are the same person. I asked one of them a question and the other one answered.
Yes I'm the same person on my phone it must be kometa newbie but my laptop it's rechcraze but it's the same account? I used the qr code from my phone to sign in? Or am I being stupid
They are for sure 2 separate accounts and confused me. Lol
Hi Again attached is the Plex Medai Server Log of the last run where it timedout again
This is the meta log for kometa for the run
It timed out on Guy Martin: Arctic Warrior
I tried the run from a different PC with a fresh installation of Kometa but still the same
I don't know why the run is making Plex Media Server hang.
Initially everything was working fine. Did my entire Movie library and then it was doing my TV Shows. But now it just hangs when I try to finish the rest of the overlays for my TV shows. In alphabetical order it's done from A-G. I still have the rest of my TV shows pending G-Z to finish the overlays for but just keep getting timed out and Plex Server hangs cause of the run.
Would you be able to share your scheduled task manager setup please?
Additionally, what did the dbrepair find if anything?
Thirdly, I'd like to understand the 4 runs you do so we can get you back to 1 Kometa folder instead of 4 Kometa folders....
All of these logs are confusing for me at least...
There is going to be nothing that can be done directly on the Kometa side about the timeout aside from extending the timeout in the config to wait longer for a response.
This is the same as you visiting a friend who doesn't answer the door. You can't knock any differently, or force them to come to the door. All you can do is wait longer.
As of now I am not doing any other runs. Only the run for the ratings overlay.
This is the plexDBrepair log
I've got a plex server running on a synology and setup kometa in the same way for that and it doesn't seem to hang the way it does on Windows
For sure it is not Kometa itself but rather the Plex Medai Server. But what is the cause I don't know
PMS Scans on Windows take significantly longer than they do with PMS on Synology NAS. And the same applies for the Kometa runs
Could be some Windows related issue? Or Python related? Network adapter?
The "Gathering Items for Overlay" is painfully slow along with the "filtering"
So everytime Kometa freezes when updating an overlay this is what the Plex console shows
Further to this, I don't receive the timeout errors in Kometa for my movie library. It only happens with the TV Shows.
Ok... so to level set, it now seems like you have moved PMS from the windows machine to the synology machine as a container AND Kometa is running as a container on the synology machine?
Hard to keep up here... sorry...
Again.... with all the moving parts and have 4 types of runs with additional folders makes this really difficult to troubleshoot.
Before going to that 4 folder setup with task scheduler, we likely would have solved the challenges you were facing without all of these hoops you are going through.
We could also try to get you setup in a more standard way and take it from there?
And a comment on the logs, you can see the duration of time that each transaction is taking... also seems like your pms machine is transcoding which can be heavy...
Hi guy just an update, I bit the bullet and just re-did a new library for my TV shows and boom it was working fine. But I may eventually ask for your help to try and simplify everything. Thanks so much!
bullmoose20 used !aenh
@lilac vapor, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.