๐ If you want to review this again, encognico:
: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> ๐
#Troubleshooting Errors
1 messages ยท Page 1 of 1 (latest)
Welcome @cedar coyote!
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.
Noticed my kometa docker setup had stopped working about 10 days ago but no changes were made so wondering if i need to update or amend any configs. Sharing my log + config
**User Info**
Author of Linked Message: Incognico
Person who Invoked the Command: Incognico
File Name: meta.log
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation โ
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Plex Configuration - Section 3
Page 08: Plex Configuration - Section 4
Page 09: Rec 01 - ๐ VERSION UPDATE AVAILABLE
Page 10: Rec 02 - ๐ฅ [CRITICAL]
Page 11: Rec 03 - โ [ERROR]
Page 12: Rec 04 - โ ๏ธ MEMORY RECOMMENDATION
Page 13: Rec 05 - โ ๏ธ RUN_ORDER WARNING
Page 1/13
seems to break at my oscars config but it feels like theres more going on, any ideas where to start?
Kometa is unable to connect to Plex, according to that log.
As a result, nothing's getting processed:
| requests.exceptions.ConnectionError: HTTPConnectionPool(redacted): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f4b9e410590>: Failed to establish a new connection: [Errno 113] No route to host')) |
Also, you're running a very old version.
gah - okay my "static" ip changed... thank you for pointing that out. ive corrected it on my config and seem to be running without issue now.
definitely noted on being outdated, but generally it has not felt like staying up to date was essential unless a larger change was implmented or happened say on a 3rd party end
I'll give updating via docker a shot, thank you for the wisdom