| 00:21:36 | | cyan_box joins |
| 00:25:29 | | cyanbox_ quits [Ping timeout: 272 seconds] |
| 01:18:06 | <Ryz> | That was a bit of a weird hiccup I encountered, after a week or so of not checking the laptop, I came to check and see although the VM says the Warrior was running, I was unable to check the dashboard, so I had to shut down the VM from the program itself and not the dashboard |
| 01:18:16 | <Ryz> | I started it back up and sure enough it worked fine |
| 01:19:15 | <Ryz> | This seems to be really uncommon encountering that, not sure how much people have the same experience as me, and how often this particular scenario is encountered |
| 01:22:20 | <Reedy> | it happens |
| 02:23:06 | | Suika quits [Quit: Server is ded] |
| 02:24:25 | | Suika joins |
| 03:42:06 | | PredatorIWD256 joins |
| 03:43:46 | | PredatorIWD25 quits [Ping timeout: 256 seconds] |
| 03:43:46 | | PredatorIWD256 is now known as PredatorIWD25 |
| 04:33:13 | | nexussfan quits [Read error: Connection reset by peer] |
| 05:04:48 | | n9nes quits [Ping timeout: 256 seconds] |
| 05:05:08 | | n9nes joins |
| 05:12:23 | | Webuser532163 joins |
| 05:14:49 | | Webuser532163 quits [Client Quit] |
| 06:04:05 | | nexussfan (nexussfan) joins |
| 06:23:57 | | nexussfan quits [Client Quit] |
| 06:46:08 | <@arkiver> | Reedy: does that mean you have seen it before too? how often did this happen for you? |
| 07:09:05 | | sec^nd quits [Remote host closed the connection] |
| 07:09:39 | | sec^nd (second) joins |
| 07:11:39 | | s-crypt quits [Quit: Ping timeout (120 seconds)] |
| 07:11:59 | | s-crypt (s-crypt) joins |
| 08:22:31 | | Shard114 (Shard) joins |
| 08:23:08 | | Shard11 quits [Ping timeout: 256 seconds] |
| 08:23:08 | | Shard114 is now known as Shard11 |
| 10:35:45 | | simon816 quits [Quit: ZNC 1.10.1 - https://znc.in] |
| 10:40:42 | | simon816 (simon816) joins |
| 12:00:01 | | Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat] |
| 12:02:53 | | Bleo182600722719623455222 joins |
| 12:44:16 | | irisfreckles13 joins |
| 14:27:11 | | sec^nd quits [Remote host closed the connection] |
| 14:27:39 | | sec^nd (second) joins |
| 16:18:29 | | DogsRNice joins |
| 18:11:55 | | irisfreckles13 quits [Read error: Connection reset by peer] |
| 21:09:46 | | BearFortress quits [] |
| 21:50:53 | | BearFortress joins |
| 22:01:59 | | Sluggs (Sluggs) joins |
| 22:50:08 | | PredatorIWD25 quits [Quit: Ping timeout (120 seconds)] |
| 22:50:31 | | PredatorIWD25 joins |
| 23:00:21 | | nexussfan (nexussfan) joins |
| 23:03:29 | | sec^nd quits [Remote host closed the connection] |
| 23:05:15 | | sec^nd (second) joins |
| 23:05:53 | | mrminemeet quits [Ping timeout: 272 seconds] |
| 23:05:57 | | mrminemeet_ joins |
| 23:16:46 | | atphoenix_ (atphoenix) joins |
| 23:19:49 | | atphoenix__ quits [Ping timeout: 272 seconds] |
| 23:20:41 | <nyakase> | Not the same, but I've noticed that occasionally the Docker warrior will have stopped, even though I didn't ask it to |
| 23:21:04 | <nyakase> | if i sudo docker ps --all i see "Exited (0) 12 hours ago" |
| 23:23:09 | <nyakase> | last logs of the container: https://pastebin.com/raw/JJaNziqy |
| 23:26:12 | <nyakase> | "after a week or so" from Ryz and "Running for more than 7 days. Time to schedule a reboot." seems curious |
| 23:28:00 | <@JAA> | Hmm, I see that the recommended Docker command has `--restart=on-failure` rather than `--restart=unless-stopped`. |
| 23:30:55 | <@JAA> | (No idea what the VM does.) |
| 23:38:25 | | mrminemeet joins |
| 23:39:26 | | mrminemeet_ quits [Ping timeout: 256 seconds] |
| 23:59:55 | <klea> | JAA: wasn't this discouraged?: docker create --name watch-once-tower --rm -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --cleanup --include-stopped --run-once |