plain wasp
Hello,
I have kometa running under Docker (on Synology)
Unfortunately i cant see any log, just a cron-like output
mellow spearBOT
Welcome @plain wasp!
It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.
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.
mellow spearBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
sour viper
You need to use the --run argument from that link
The default behaviour is that Kometa will run at 5AM
inland light
When the default container is started, Kometa will determine the current time and the default is to run at 5am. When 5am comes around, the script starts and when it finishes, it will wait until the next run at 5am.
It will continue to do this as long as the container is running. If the container is offline, then Kometa cannot start.
plain wasp
Got it, thank you vey much, and happy christmas.
inland light
Merry Xmas to you as well.
plain wasp
I have directly another question. Kometa container stopps once in an hour unexcpetedly.
But i have in my docker no log entry with level error
plain wasp
I cant find out the reason. Also exported the full log in html but also at the timing the container restarted i could not see a reason
do i have to remove the dummy configurations for tautull, radarr and sonarr from config file? I just kept it from the template
inland sinew
The log is on disk; we don't want the html version.
inland sinew
do i have to remove the dummy configurations for tautull, radarr and sonarr from...
No.
What environment variables are set on the container?
plain wasp
The log is on disk; we don't want the html version.
and how to cut it ? Thats >30MB 🙂
inland sinew
and how to cut it ? Thats >30MB 🙂
You can just drag the whole thing in here.
inland sinew
KOMETA_RUN tells Kometa to run immediately when the container starts and then exit the container. If what you want is for Kometa to wake up at 3AM every day, remove that env var.
You also have auto-restart enabled, so this container will run, exit, get restarted, run, exit, get restarted, repeat forever.
plain wasp
Thanks i would check that now
limpid trellisBOT
antwanchild used !aenh
@plain wasp, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.
