#Item: One Way Labels failed to load

1 messages · Page 1 of 1 (latest)

rigid zinc
#

My Kometa instance keeps getting a Critical Error, as the title says.

I have recently played around with moving the 720P from the top-left corner down a bit.

I checked the Wiki but there is no mention on this error nor any previous one.

I also see a few errors in the log that I don't know how to fix.

radiant caveBOT
#

Welcome @rigid zinc!

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.

rigid zinc
radiant caveBOT
#

📝 If you want to review this again, sideh:
: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 06** - ⚠️🖥️ **LINUXSERVER IMAGE DETECTED**

⚠️🖥️ LINUXSERVER IMAGE DETECTED
You are not using the official Kometa container image.
In the Kometa discord thread, type !lsio for more information.
For more information on this, [https://kometa.wiki/en/latest/kometa/install/images/?h=linuxserver#linuxserver]
1 line(s) with LINUXSERVER IMAGE issues. Line number(s): 10

mint sierraBOT
#
LinuxServer (LSIO) Issues

The Linuxserver.io image [linuxserver/kometa] is different to the OFFICIAL image [kometa-team/kometa] in a few ways that cause problems.

It keeps the Kometa files in a different place inside the image compared to official, so when you exec into it you can't just run Kometa, you need to cd into another dir first.

The default run time is 3:00am which coincides with Plex maintenance.

Generally speaking, we suggest you use the official Kometa image instead of lsio. Type !repos for more info.

#
Kometa Repos & Images

These are the only approved Kometa repositories and build images, please ensure that you use the correct image.

PRIMARY REPOSITORIES:

Kometa [formerly Plex Meta Manager]: https://github.com/kometa-team/Kometa

Overlay Reset: https://github.com/kometa-team/Overlay-Reset

ImageMaid [formerly Plex Image Cleanup]: https://github.com/kometa-team/ImageMaid

Community Configs: https://github.com/kometa-team/Community-Configs

Default Images: https://github.com/kometa-team/Default-Images

All of our other repositories can be found by clicking here

IMAGES
Docker Image: kometateam/kometa
unRAID Image: kometateam/kometa

Branches are master, develop, nightly

hoary shore
#

The cause of the titular error is that something inside Plex is exploding when Kometa asks for the labels on an episode:

[2024-05-20 18:01:12,780] [plex.py:1292]              [INFO]     | S1E9 One Way Poster | Reset from Plex                                                              |
...
                                                                 | plexapi.exceptions.BadRequest: (500) internal_server_error; (redacted)/library/metadata/37782?checkFiles=1&includeAllConcerts=1&... |
...
[2024-05-20 18:01:12,919] [kometa.py:730]             [CRITICAL] | Item: One Way Labels failed to load                                                                |
#

A 500 error is [typically] a catastrophic unforeseen error inside the server.

#

There are a bunch of other issues in there.

rigid zinc
#

I ran the PlexDBRepair (https://github.com/ChuckPa/PlexDBRepair) and this seems to have fixed this, it hasn't crashed (yet).

Still see some smaller errors:
| 18 | Plex Error: resolution: No matches found with regex pattern (?i)2160 | | 6 | Overlay Error: No poster found | | 5 | MDBList Error: Not Found | | 2 | Invalid Root Folder: 'config/movies' Options: [[1:/movies]] | | 2 | Invalid Root Folder: 'config/tv' Options: [[1:/tv]] | | 2 | Collection Error: No builders were found |

These seem trivial and I will continue to look through the config and work it out.

GitHub

Database repair utility for Plex Media Server databases - ChuckPa/PlexDBRepair