HomeSearchPrevious dayNext day

00:36:31qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
01:44:50ScenarioPlanet (ScenarioPlanet) joins
02:07:20ScenarioPlanet quits [Ping timeout: 240 seconds]
04:00:20monoxane quits [Read error: Connection reset by peer]
04:11:23monoxane (monoxane) joins
05:20:22DogsRNice quits [Read error: Connection reset by peer]
06:50:54monoxane quits [Client Quit]
06:56:20monoxane (monoxane) joins
07:47:01qwertyasdfuiopghjkl quits [Remote host closed the connection]
08:20:14Wickerz joins
08:21:33<Wickerz>Hi guys! Looking for some help with my Warrior instance.
08:21:36M--mlv|m joins
08:22:28<Wickerz>Yesterday evening it stopped, and in the log I could see a message saying something in line with "Have been running for 7 days, time for a restart" or something like that.
08:23:08<Wickerz>This morning however the warrior was not restarted and the docker container wasn't active again. I restarted it manually this morning. Any tips on how to avoid this in 7 days again?
08:37:40<Wickerz>If it helps at all I ran it initially with the code from the wiki
08:37:40<Wickerz>docker run --detach --name archiveteam-warrior --label=com.centurylinklabs.watchtower.enable=true --log-driver json-file --log-opt max-size=50m --restart=on-failure --publish 8001:8001 atdr.meo.ws/archiveteam/warrior-dockerfile
08:55:52qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
08:58:34Wickerz quits [Ping timeout: 265 seconds]
09:29:33<that_lurker>why do they always leave so soon
10:00:01Bleo18260 quits [Client Quit]
10:01:28Bleo18260 joins
10:02:00qwertyasdfuiopghjkl quits [Remote host closed the connection]
10:06:44Wickerz joins
10:07:36<Wickerz>I disconnected from the channel :( but saw there were some unread messages. Did someone reply?
10:07:39<Wickerz>Yesterday evening it stopped, and in the log I could see a message saying something in line with "Have been running for 7 days, time for a restart" or something like that.This morning however the warrior was not restarted and the docker container wasn't active again. I restarted it manually this morning. Any tips on how to avoid this in 7 days
10:07:40<Wickerz>again?Wickerz09:37:39If it helps at all I ran it initially with the code from the wikidocker run --detach --name archiveteam-warrior --label=com.centurylinklabs.watchtower.enable=true --log-driver json-file --log-opt max-size=50m --restart=on-failure --publish 8001:8001 atdr.meo.ws/archiveteam/warrior-dockerfile^
10:30:15<that_lurker>it's odd that it did not start properly after the restarts.
10:30:43<that_lurker>I just run mine with "docker run --detach --name archiveteam-warrior --label=com.centurylinklabs.watchtower.enable=true -e DOWNLOADER=<LeaderBoardUsernameHere> -e HTTP_USERNAME=<DashboardLoginUsernameHere> -e HTTP_PASSWORD=<DashboardPasswordHere> -e CONCURRENT_ITEMS=6 -e SHARED_RSYNC_THREADS=20 -e SELECTED_PROJECT=auto --log-driver json-file
10:30:43<that_lurker>--log-opt max-size=50m --restart=unless-stopped --publish 8001:8001 atdr.meo.ws/archiveteam/warrior-dockerfile"
10:32:21<that_lurker>If it fails to restart or crashes the error should show up in the containers logs. So with docker logs archiveteam-warrior
10:40:18Wickerz quits [Remote host closed the connection]
10:40:26Wickerz joins
10:43:25<Wickerz>that_lurker thanks! I just checked. I see: at 21:12 "Running for more than 7 days. Time to schedule a reboot."
10:43:43<Wickerz>Then a lot the normal debug things
10:44:30<Wickerz>and last command yesterday at 22:31 "INFO - Runner has finished" and then finally sudo: shutdown: command not found
10:45:22<Wickerz>is it caused by some permission error then?
10:46:52<that_lurker>Sounds like this could help; Stop the container and do a docker system prune -a and then run the docker run command again.
10:47:41<Wickerz>would that kill all docker containers?
10:48:13<that_lurker>if you run docker stop archiveteam-warrior, then it will only stop the warrior container.
10:48:37<Wickerz>so docker stop archiveteam-warrior and then run the docker command again?
10:49:00<that_lurker>docker system prune -a before running it again so it will fetch the latest image
10:50:09<Wickerz>alright, I'll try that
10:50:09qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
10:50:19<that_lurker>you could target the prune to only that container, but doing a complete system prune is good from time to time to get rid of dangling images, networks and such
10:51:12<Wickerz>And the one from this site, yes?
10:51:13<Wickerz>https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior#Installing_and_running_with_Docker
10:51:23<Wickerz>docker run --detach --name archiveteam-warrior --label=com.centurylinklabs.watchtower.enable=true --log-driver json-file --log-opt max-size=50m --restart=on-failure --publish 8001:8001 atdr.meo.ws/archiveteam/warrior-dockerfile
10:53:24<that_lurker>yep, you can add the environment variable also though so it will remember them on restart. https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior/Docker_environment_variables
10:57:01<Wickerz>Do I just add each variable with --e? I.e. like this
10:57:02<Wickerz>docker run --detach --name archiveteam-warrior --label=com.centurylinklabs.watchtower.enable=true --log-driver json-file --log-opt max-size=50m --restart=on-failure --publish 8001:8001 --e SELECTED_PROJECT=auto --e CONCURRENT_ITEMS=6 atdr.meo.ws/archiveteam/warrior-dockerfile
10:58:21<Wickerz>.... just -e I see now :)
10:59:21ScenarioPlanet (ScenarioPlanet) joins
11:00:34<Wickerz>Up and running again, thanks! Hope that fixed it
11:05:04Wickerz quits [Remote host closed the connection]
12:27:46jacksonchen666 quits [Remote host closed the connection]
12:28:23jacksonchen666 (jacksonchen666) joins
13:08:07<@JAA>I don't see how the Docker container could restart itself without access to the Docker socket.
13:08:18<@JAA>The reboot thing is intended for the VM, isn't it?
13:08:42<@JAA>And I think it predates all container usage here by years.
13:09:12<@JAA>Well, I guess it could restart itself indirectly via --restart=on-failure and then crashing.
13:11:41qwertyasdfuiopghjkl quits [Remote host closed the connection]
13:13:15qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
13:27:20Arcorann quits [Ping timeout: 240 seconds]
17:04:25ScenarioPlanet quits [Client Quit]
17:34:39IndustrialRobot|m quits [Remote host closed the connection]
17:34:41jwoglom|m quits [Read error: Connection reset by peer]
17:34:45x9fff00 quits [Read error: Connection reset by peer]
17:34:45s-crypt|m|m quits [Read error: Connection reset by peer]
17:34:45Thibaultmol quits [Read error: Connection reset by peer]
17:34:45theblazehen|m quits [Read error: Connection reset by peer]
17:34:45mpeter|m quits [Read error: Connection reset by peer]
17:34:45mind_combatant quits [Read error: Connection reset by peer]
17:34:45igneousx quits [Remote host closed the connection]
17:34:51M--mlv|m quits [Read error: Connection reset by peer]
17:34:58manu|m quits [Write error: Connection reset by peer]
17:35:02Roki_100|m quits [Read error: Connection reset by peer]
17:35:02tech234a|m quits [Read error: Connection reset by peer]
17:35:03Exorcism quits [Read error: Connection reset by peer]
17:35:03MaxG quits [Read error: Connection reset by peer]
17:35:03Hans5958 quits [Read error: Connection reset by peer]
17:35:03@Sanqui|m quits [Read error: Connection reset by peer]
17:35:03moe-a-m|m quits [Read error: Connection reset by peer]
17:35:06jkap quits [Remote host closed the connection]
17:35:15yetanotherarchiver|m quits [Remote host closed the connection]
17:35:15piraces|m quits [Read error: Connection reset by peer]
17:35:16nathanielcwm quits [Remote host closed the connection]
17:35:16octylFractal|m quits [Read error: Connection reset by peer]
17:35:16Minkafighter|m quits [Read error: Connection reset by peer]
17:35:16phaeton quits [Read error: Connection reset by peer]
17:35:16nstrom|m quits [Remote host closed the connection]
17:35:16Vokun quits [Read error: Connection reset by peer]
17:35:16britmob|m quits [Read error: Connection reset by peer]
17:35:16DigitalDragon quits [Read error: Connection reset by peer]
17:35:16JC|m quits [Remote host closed the connection]
17:35:17akaibu|m quits [Read error: Connection reset by peer]
17:35:17schwarzkatz|m quits [Read error: Connection reset by peer]
17:35:17jackt1365|m quits [Remote host closed the connection]
17:35:17vics quits [Remote host closed the connection]
17:35:17CrispyAlice2 quits [Remote host closed the connection]
17:35:18wrangle|m quits [Remote host closed the connection]
17:52:48mpeter|m joins
17:52:58mpeter|m quits [Read error: Connection reset by peer]
17:55:17mpeter|m joins
18:00:36mind_combatant joins
18:00:36theblazehen|m joins
18:00:36Hans5958 (Hans5958) joins
18:00:36jackt1365|m joins
18:00:36DigitalDragon (DigitalDragon) joins
18:00:36britmob|m joins
18:00:36igneousx (igneousx) joins
18:00:36tech234a|m joins
18:00:36Sanqui|m (Sanqui) joins
18:00:36schwarzkatz|m joins
18:00:36Thibaultmol joins
18:00:36akaibu|m joins
18:00:36CrispyAlice2 (CrispyAlice2) joins
18:00:36Minkafighter|m joins
18:00:36x9fff00 (x9fff00) joins
18:00:36moe-a-m|m joins
18:00:36wrangle|m joins
18:00:36jwoglom|m joins
18:00:36octylFractal|m joins
18:00:36@ChanServ sets mode: +o Sanqui|m
18:00:36MaxG joins
18:00:36Roki_100|m joins
18:00:36yetanotherarchiver|m joins
18:00:36Vokun (Vokun) joins
18:00:36nstrom|m joins
18:00:36nathanielcwm joins
18:00:36phaeton (phaeton) joins
18:00:36s-crypt|m|m joins
18:00:36JC|m joins
18:00:36manu|m joins
18:00:36Exorcism (exorcism) joins
18:00:36vics joins
18:00:37piraces|m joins
18:00:37jkap (jkap) joins
18:00:51IndustrialRobot|m joins
18:04:44qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds]
18:55:48ScenarioPlanet (ScenarioPlanet) joins
19:15:04qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
19:52:15magmaus3 (magmaus3) joins
21:27:32jacksonchen666 quits [Client Quit]
22:46:42ScenarioPlanet quits [Client Quit]
22:55:27DogsRNice joins
23:04:53abirkill quits [Quit: Let us prepare to grapple with the ineffable itself, and see if we may not eff it after all.]
23:14:55Arcorann (Arcorann) joins
23:25:50abirkill (abirkill) joins

HomeSearchPrevious dayNext day