Back-off restarting failed container - Boot Loop

Gavineitor

Cadet
Joined
Nov 28, 2022
Messages
1
I'm deploying an image for tile-card-maker. The docker manages to deploy and do its thing, when it's finished it goes from active to deploying and sometimes goes active again but eventually gets stuck in deploying.

The image has a scheduling feature so it should stay active.
[DEBUG] frequency : {'interval': 12, 'unit': 'hours'}
And eventually, I want to learn how to change the 12h interval.

For now, I don't get any errors in the logs and these are my application events

2022-11-29 12:06:19 Back-off restarting failed container
2022-11-29 12:04:39 Started container ix-chart
2022-11-29 12:04:39 Created container ix-chart
2022-11-29 12:04:37 Container image "collinheist/titlecardmaker:master" already present on machine
2022-11-29 12:04:37 Add eth0 [172.16.28.5/16] from ix-net
Successfully assigned ix-title-card-maker/title-card-maker-ix-chart-76bc8684c4-lmthv to ix-truenas
2022-11-29 12:04:34 Created pod: title-card-maker-ix-chart-76bc8684c4-lmthv

Logs just in case

2022-11-29T18:34:01.358690435Z usermod: no changes
2022-11-29T18:34:43.233037074Z [DEBUG] Runtime arguments:
2022-11-29T18:34:43.233067847Z [DEBUG] preferences : /config/preferences.yml
2022-11-29T18:34:43.233073607Z [DEBUG] run : True
2022-11-29T18:34:43.233077755Z [DEBUG] sync : False
2022-11-29T18:34:43.233085687Z [DEBUG] frequency : {'interval': 12, 'unit': 'hours'}
2022-11-29T18:34:43.233089818Z [DEBUG] missing : /maker/missing.yml
2022-11-29T18:34:43.233093599Z [DEBUG] log : INFO
2022-11-29T18:34:43.233097368Z [DEBUG] no_color : True
2022-11-29T18:34:43.233101184Z [DEBUG] tautulli_frequency : {'interval': 4, 'unit': 'minutes'}
2022-11-29T18:34:43.233107471Z [INFO] Read preference file "/config/preferences.yml"
2022-11-29T18:34:43.233111546Z [DEBUG] Using "" ImageMagick command prefix
2022-11-29T18:34:43.233115447Z [DEBUG] Read 4 show records
2022-11-29T18:34:43.233119338Z [INFO] Starting TitleCardMaker (v1.12.0)
2022-11-29T18:34:43.233125586Z [DEBUG] Latest remote version is v1.12.0
2022-11-29T18:34:43.233130315Z [DEBUG] Tautulli integrated detected
2022-11-29T18:34:43.233134262Z [INFO] Starting to sync to series YAML files..
2022-11-29T18:34:43.233138167Z [INFO] Synced /maker/yaml/sonarr_sync.yml from Sonarr
2022-11-29T18:34:43.233142004Z [INFO] Synced /maker/yaml/plex_sync_anime.yml from Plex
2022-11-29T18:34:43.233147994Z [INFO] Synced /maker/yaml/plex_sync_tv.yml from Plex
2022-11-29T18:34:43.235601798Z
0%| | 0/2 [00:00]
Reading tv.yml: 0%| | 0/2 [00:00]


Reading tv.yml: 0%| | 0/2 [00:00]
Reading anime.yml: 0%| | 0/2 [00:00]
2022-11-29T18:34:43.235694121Z [WARNING] Series file "/config/yaml/tv.yml" has no entries
2022-11-29T18:34:43.236188462Z
Reading entries 0%| | 0/3 [00:00][A
2022-11-29T18:34:43.236201823Z
2022-11-29T18:34:43.236226936Z
Assign interfaces 0%| | 0/1 [00:00][A[A
2022-11-29T18:34:43.236234579Z
2022-11-29T18:34:43.236369247Z
[A[A
2022-11-29T18:34:43.236380149Z
2022-11-29T18:34:43.607613558Z
Setting series IDs 0%| | 0/1 [00:00][A[A
2022-11-29T18:34:43.607631658Z
2022-11-29T18:34:43.607779736Z
Setting series IDs 100%|██████████| 1/1 [00:00][A[A
.
.
.
2022-11-29T18:34:46.248321967Z
Updating Plex for "Demon Slayer: Kimetsu no Yaiba 100%|██████████| 1/1 [00:00][A[A
2022-11-29T18:34:46.248333138Z
2022-11-29T18:34:46.248422229Z
[A[A
2022-11-29T18:34:46.248560530Z
Reading entries 100%|██████████| 3/3 [00:03][A
2022-11-29T18:34:46.251782145Z
[A
Reading anime.yml: 100%|██████████| 2/2 [00:03]


0%| | 0/2 [00:00]
Reading tv.yml: 0%| | 0/2 [00:00]
Reading anime.yml: 0%| | 0/2 [00:00]
2022-11-29T18:34:46.252430902Z
Reading entries 0%| | 0/3 [00:00][A
2022-11-29T18:34:46.302874909Z [INFO] Wrote missing assets to "/maker/missing.yml"
2022-11-29T18:34:46.363567394Z
[A


0%| | 0/4 [00:00]
Reading source files for "Demon Slayer: Kimetsu no 0%| | 0/4 [00:00]
Reading source files for "Demon Slayer: Kimetsu no 0%| | 0/4 [00:00]
 

ZeroNyte

Cadet
Joined
Apr 5, 2023
Messages
9
Every got it working? trying to redo my very basic server from scratch but for some reason all I get right now is also "Back-off restarting failed container" but can't seem to fix it or find an answer to it.
 

haifisch

Dabbler
Joined
Jun 2, 2022
Messages
19
I would love to know whats going on too. In my case there are no logs for the container either.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
It seems to me that the container does its work and then exits... so the assumption that some kind of scheduler is running in the container may be false as far as I can see.

If somebody who uses this elsewhere and knows how the container is meant to work wants to chime in, maybe that will provide the definitive answer.

I don't know if it is based on the same code, but I note from the docs of a similar container:

-t, --time, --runtime​


Schedule the Maker to run on a set interval, starting on this time. Should be specified in military/24-hour time - i.e. 17:30 would be 5:30 PM, 9:00 is 9:00 AM. If specified, the Maker will never exit on it's own (unless an error occurs).


-f, --frequency​


On what interval to run the Maker. This should be specified as INTERVAL[unit], with the acceptable units being s, m, h, d, and w for seconds, minutes, hours, days, and weeks respectively. For example, providing --frequency 12h would run the Maker every 12 hours, --frequency 1d is once a day.


Must be used in conjunction with the above -t/--time/--runtime argument. If provided on its own, nothing will happen!

 
Top