#Critical Error on TV Overlays -

1 messages Β· Page 1 of 1 (latest)

hollow stag
#

Getting this error when working on my TV Overlays

[2023-12-10 15:49:00,791] [plex_meta_manager.py:642] [CRITICAL] | (500) internal_server_error; (redacted)/library/metadata/40901/children?excludeAllLeaves=1&index=None <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html> |

I'm also attaching my logs, and my config.yml in case that helps.

Thanks in advance

sage radishBOT
#

YAML checked and is NOT valid. Error message:

while scanning an alias
in "<unicode string>", line 640, column 10:
token: Redacted
^
expected alphabetic or numeric character, but found '*'
in "<unicode string>", line 640, column 19:
token: Redacted
^

#

πŸ“ If you want to review this again, .kel.:
: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> πŸ“

#

Welcome @hollow stag!

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.

sage radishBOT
#

πŸ“ 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> πŸ“

sage radishBOT
sage radishBOT
idle moth
#

We only need meta.lig as we can extract your redacted config.yml directly from the log file

#

On my phone but what is happening at line 1222 in your log file. There should be an indication why pmm went Critical

hollow stag
#

That line says this;
[2023-12-10 15:49:00,791] [plex_meta_manager.py:642] [CRITICAL] | (500) internal_server_error; (redacted)/library/metadata/40901/children?excludeAllLeaves=1&index=None <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html> |

sage radishBOT
#

(500) internal_server_error detected in message, would you like to learn more about this error?

#
500 Internal Server Error

A 500 Internal Server Error happens when the server has an unexpected error when responding to an API request.

There could be any number of reasons why this happens and it depends on what server PMM is talking to although its most likely coming from your Plex Server.

Most of the time these errors need to be resolved by changing something specific to your set up but some do come up that can be fixed (i.e. Plex throws one if you upload a photo larger then 10 MB)

Many Appbox Setups will throw this error when too many requests are sent

Take a look at the following logs:

:one: Settings | Manage | Console -> then filter on Error and Warning to see what might be going on
:two: Check the plex logs (container or other) for the "Busy DB Sleeping for 200ms)

hollow stag
#

Plex server errors around that same time.

Dec 10, 2023 15:48:59.314 [0x14f684dd7b38] ERROR - [Req#21df00f] Unknown metadata type: folder

Dec 10, 2023 15:48:59.516 [0x14f687c08b38] ERROR - [Req#21df074] SQLITE3:0x80000001, 1, no such column: None in "select count(*) from (select distinct(metadata_items.id) from metadata_items join metadata_items as parents on metadata_items.parent_id=parents.id join metadata_items as children on

Dec 10, 2023 15:48:59.517 [0x14f687c08b38] ERROR - Got exception from request handler: sqlite3_statement_backend::prepare: no such column: None for SQL: select count(*) from (select distinct(metadata_items.id) from metadata_items join metadata_items as parents on metadata_items.parent_id=parents.id join metadata_items as children on children.parent_id=metadata_items.id where metadata_items.library_section_id in (1) and (metadata_items.index=None and metadata_items.metadata_type=3 and metadata_items.parent_id=40901) )

Dec 10, 2023 15:49:10.307 [0x14f68b466b38] WARN - Held transaction for too long (/data/jenkins/server/3537899744/Statistics/StatisticsManager.cpp:301): 0.160000 seconds

Dec 10, 2023 15:49:25.618 [0x14f687c08b38] ERROR - [Req#21df1a7] Unknown metadata type: folder

#

I'm also still running Plex Version 1.29.2.6364 because of the database/api slowness issues that were going on, not sure if that's been resolved yet

silk swallow
#

PMM has nothing to do with what SQL Plex generates internally, so that really seems like something going wrong inside Plex; perhaps database problems.

hollow stag
#

Just ran a PRAGMA integrity_check on the Plex DB and that came back OK. Is there anything else I should try next?

silk swallow
idle moth
hollow stag
#

Yeah we can close this, It's defintly something with my database. Thanks for your help