#Whats the coursing this error with collection operations?

1 messages ยท Page 1 of 1 (latest)

outer dune
devout karmaBOT
#

๐Ÿ“ If you want to review this again, morpheus2n2:
: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 @outer dune!

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.

echo tundra
#

Can you provide the full log?

#

I looks like Kometa made a boring request to Plex to ask for collections:

all_collections = self.library.get_all_collections()

But something went wrong inside Plex.

#

The specific error is coming from down inside the third-party library [plexapi] that Kometa uses for communication with Plex.

|   File "/usr/local/lib/python3.11/site-packages/plexapi/utils.py", line 168, in cast               |
|     raise ValueError(value)                                                                        |                                                                

This isn't something Kometa has anything to do with directly.

outer dune
#

Sorry about the other post completly forgot I had made this one, full log coming up ๐Ÿ˜„

devout karmaBOT
#

๐Ÿ“ If you want to review this again, morpheus2n2:
: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 01** - ๐Ÿ’ฅ **[CRITICAL]**

๐Ÿ’ฅ [CRITICAL]
Critical messages found in your attached log.
There is a very strong likelihood that Kometa aborted the run or part of the run early thus not all of what you wanted was applied.
For more information on handling these, [https://kometa.wiki/en/latest/kometa/logs/?h=[critical]#critical]
2 line(s) with [CRITICAL] messages. Line number(s): 907, 1062

echo tundra
#

On those two libraries, Kometa is making a plain boring request to Plex to get a list of the collections in the library:

all_collections = self.library.get_all_collections()

Something is failing, possibly inside Plex, such that this boring request returns something unexpected.

You're running in docker, so all the dependencies will be up-to-date, which would probably indicate that the problem is inside Plex.

This isn't an orderly error, so there isn't a single known cause. Were it happening to me, I would create replacements for these two libraries to see if the problem clears on the new versions.

outer dune
#

very interesting, Ill do some playing around with Plex and see what happens, other than that all my other issues have no gone :D, I want to thank you so much for your help and patience, Now to play making actual custom collections ๐Ÿ˜„