📝 If you want to review this again, xapslock:
: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> 📝
#Time out or dns problems
1 messages · Page 1 of 1 (latest)
Welcome @wispy acorn!
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.
Greetings,
i have a fresh kometa installation but it won´t work.
Running a TrueNas with Plex and Kometa on the same maschine, my config is quite simple:
libraries:
Movies:
collection_files:
- default: imdb
- default: genre
overlay_files:
- default: resolution
- default: ribbon
plex:
url: http://192.168.178.67:32400
token: (redacted by Luma)
tmdb:
apikey: (redacted by Luma)
When i trigger a run it always time out after a minute or so. The logs show some "Failed to resolve 'raw.githubusercontent.com'" stuff, but i checked pi-hole and also whitelistet that domain.
Any Ideas?
📝 If you want to review this again, antwanchild:
: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> 📝
**User Info**
Author of Linked Message: Luma
Person who Invoked the Command: Antwan
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: Rec 01 - 💥 [CRITICAL]
Page 06: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 07: Rec 03 - Error: Plex scheduled time is missing.
Page 08: Rec 04 - Error: Memory value not found in content.
Page 1/8
This is a DNS problem:
| socket.gaierror: [Errno -3] Temporary failure in name resolution
...
| urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPSConnection object at 0x7f0a1269ad50>: Failed to resolve 'raw.githubusercontent.com' ([Errno -3] Temporary failure in name resolution)
Kometa tries to make a request to github to find out the current Kometa version, and the domain 'raw.githubusercontent.com' can't be resolved to an IP.
Then the run gets killed:
[CRITICAL] | RetryError[<Future at 0x7f0a121ff1d0 state=finished raised ConnectionError>]
Thanks, I just noticed that the 5am run was successful.
Am I using the correct command to run it manually?
"sudo docker run --rm -it -v "/mnt/pool1/apps/kometa/config:/config:rw" kometateam/kometa --run"
Sure, that's fine. That will spin up a new container, run Kometa immediately, then delete the container.
chazlarson used !afnh
@wispy acorn, anything further needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.
Thanks for the help. I rolled back by pihole setup and now kometa is working properly, so it was indeed a dns miss-config on my side.