| 00:00:01 | | HackMii quits [Remote host closed the connection] |
| 00:00:29 | | HackMii (hacktheplanet) joins |
| 01:50:38 | | HackMii quits [Ping timeout: 258 seconds] |
| 01:52:40 | | HackMii (hacktheplanet) joins |
| 04:49:25 | | qwertyasdfuiopghjkl quits [Ping timeout: 244 seconds] |
| 07:00:52 | | Sluggs quits [Ping timeout: 252 seconds] |
| 07:25:05 | | qwertyasdfuiopghjkl joins |
| 08:44:30 | | Terbium quits [Ping timeout: 265 seconds] |
| 08:44:46 | | Terbium joins |
| 08:45:31 | | yano quits [Read error: Connection reset by peer] |
| 08:45:33 | | yano1 (yano) joins |
| 09:20:09 | | qwertyasdfuiopghjkl quits [Ping timeout: 244 seconds] |
| 13:15:18 | | HackMii quits [Remote host closed the connection] |
| 13:17:03 | | HackMii (hacktheplanet) joins |
| 15:11:41 | | Matthww quits [Read error: Connection reset by peer] |
| 15:12:29 | | Matthww joins |
| 15:50:16 | <gazorpazorp> | I can't get any project to work at all, except URLTeam 2. Blank screen (just the menu on the left), not even items saying there aren't enough items available or anything |
| 15:50:40 | <gazorpazorp> | I did a `sudo docker restart <id>` on some of the containers, still nothing |
| 15:53:55 | | Sluggs joins |
| 16:46:39 | <Jake> | Yeah, the docker image needs to be updated. |
| 17:25:42 | <@JAA> | Triggered a rebuild. Hope that's all that's needed. |
| 17:28:59 | <@JAA> | gazorpazorp: Can you repull the image and try again please? |
| 17:30:31 | <p1nk> | I'm having the same issue I think as @qazorpazorp. Commands I ran are: |
| 17:30:32 | <p1nk> | docker pull atdr.meo.ws/archiveteam/warrior-dockerfile |
| 17:30:32 | <p1nk> | docker pull containrrr/watchtower |
| 17:30:32 | <p1nk> | docker restart archiveteam-warrior |
| 17:30:32 | <p1nk> | docker restart watchtower |
| 17:31:20 | <p1nk> | I just opened up my instance - you can see what's going on @ http://159.65.204.231:8001/ |
| 17:32:43 | <@JAA> | When did you pull? |
| 17:32:55 | <@JAA> | The build finished at around 17:26 I think. |
| 17:33:06 | <p1nk> | I pulled about 5 minutes ago - after seeing Jake's message |
| 17:33:46 | <@JAA> | You'll want the image digest bce689ea91f4. |
| 17:34:12 | <p1nk> | atdr.meo.ws/archiveteam/warrior-dockerfile latest b725c800d70b 8 minutes ago 233MB |
| 17:34:12 | <p1nk> | atdr.meo.ws/archiveteam/warrior-dockerfile <none> 4781853605c9 2 months ago 231MB |
| 17:34:12 | <p1nk> | containrrr/watchtower latest dd78a816fb76 5 months ago 16.4MB |
| 17:34:13 | <gazorpazorp> | JAA: shouldn't the Watchtower update it? How do I pull the image again? Doesn't "sudo docker run --detach --name at4 --label=com.centurylinklabs.watchtower.enable=true --restart=on-failure --publish 8004:8001 atdr.meo.ws/archiveteam/warrior-dockerfile" pull it? |
| 17:34:19 | <gazorpazorp> | Because I still get the same error |
| 17:34:44 | <@JAA> | Uh right, another digest. I hate reading Docker build outputs. lol |
| 17:34:54 | <@JAA> | b725c800d70b is right. |
| 17:35:05 | <@JAA> | gazorpazorp: Yes, Watchtower should do that I think. |
| 17:36:19 | <@JAA> | Welp, I guess just rebuilding the image isn't sufficient then. |
| 17:36:30 | <@JAA> | Kaz? |
| 17:36:40 | <p1nk> | I'm purging it all and re-building |
| 17:40:35 | <p1nk> | No change. I see in the archiveteam-warrior logs: |
| 17:40:36 | <p1nk> | 2021-10-01 17:39:03,414 - seesaw.warrior - DEBUG - Select project auto |
| 17:40:36 | <p1nk> | 2021-10-01 17:39:03,414 - seesaw.warrior - DEBUG - Update warrior hq. |
| 17:40:36 | <p1nk> | 2021-10-01 17:39:03,414 - seesaw.warrior - DEBUG - Warrior ID ''. |
| 17:40:38 | <p1nk> | (EOL) |
| 17:40:58 | <p1nk> | Current project page still blank |
| 17:41:57 | <p1nk> | When I try and stop the project "ArchiveTeam's Choice", the logs say |
| 17:41:58 | <p1nk> | 2021-10-01 17:41:33,960 - seesaw.warrior - DEBUG - Select project None |
| 17:41:58 | <p1nk> | 2021-10-01 17:41:33,961 - seesaw.warrior - DEBUG - Project doesn't exist. |
| 17:42:20 | <@JAA> | Uh |
| 17:50:16 | <knecht420> | works for me after re-pulling and recreating |
| 17:51:07 | | arkiver (arkiver) joins |
| 17:51:07 | | @ChanServ sets mode: +o arkiver |
| 17:51:13 | <@arkiver> | apparently i was not in this channel |
| 17:51:26 | <@arkiver> | guess warrior-dockerfile needs to be rebuild, is that done? |
| 17:52:36 | <@JAA> | Yes, I triggered a rebuild. Two people reported it still didn't work, one person reported it working. |
| 17:53:23 | <p1nk> | @knect420 - what do you see when you run docker logs -f archiveteam-warrior |
| 17:54:49 | | Sluggs quits [Ping timeout: 252 seconds] |
| 17:55:31 | | Sluggs joins |
| 17:58:11 | <@arkiver> | if one person reported it working its probably working |
| 18:01:56 | <@JAA> | Warriors are submitting items on the Reddit tracker, so yeah, seems to be working. I wonder what's wrong on p1nk's system then though. |
| 18:03:22 | <knecht420> | i just did 'docker-compose pull && docker-compose up-d' |
| 18:03:32 | <knecht420> | p1nk ^ |
| 18:04:15 | <knecht420> | 'up -d'* |
| 18:13:53 | <gazorpazorp> | https://paste.kiska.pw/StarvesPerceval |
| 18:14:04 | <gazorpazorp> | warrior error logs |
| 18:15:16 | <knecht420> | are you sure you pulled the latest image? |
| 18:25:19 | <gazorpazorp> | I thought Watchtower would take care of that. After manually deleting the old images and pulling the new ones, it works |
| 18:25:47 | <gazorpazorp> | should I pull the new watchtower image as well? |
| 18:25:51 | <knecht420> | watchtower by default only checks once every 24h |
| 18:26:00 | <gazorpazorp> | oh, right |
| 18:26:08 | <knecht420> | so you could've waited it out |
| 18:26:18 | <knecht420> | no need to pull new watchtower though |
| 18:26:26 | <gazorpazorp> | is that so the AT server isn't overwhelmed? Is it OK to make it check every, say, 30 mins? |
| 18:27:09 | <knecht420> | watchtower is not affiliated with AT or whatever by the way, the watchtower devs chose that interval |
| 18:28:12 | <knecht420> | and it's rare for running containers to just stop functioning and requiring an update, so 24h is reasonable if it is only about getting the latest version |
| 18:33:19 | <gazorpazorp> | So I profoundly misunderstood, I thought it was developed by AT because it makes sure the old container closes gracefully when a new version of the image is available. |
| 18:34:04 | <gazorpazorp> | Actually the polling interval is 1 hour (I think) because the watchtower command from the wiki has --interval 3600 https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior |
| 18:34:22 | <gazorpazorp> | and that's what most people (me incl.) run |
| 18:37:13 | <@Kaz> | hello |
| 18:37:15 | <@Kaz> | whats wrong |
| 18:37:45 | <knecht420> | Kaz: all is well :) |
| 18:38:35 | <@Kaz> | very good, glad to hear it |
| 18:39:03 | <@Kaz> | as for you gazorpazorp, poll as often as you like (but stay sane, once per minute is plenty) |
| 18:39:48 | <@Kaz> | 24h is a pretty big window considering some of our updates also mandate blocking old versions of the project code from taking any new work, so you could be out of action for 24h |
| 18:41:44 | <gazorpazorp> | an hour seems like a good default, I'll leave it at that |
| 19:48:22 | <masterX244> | odd... warrior´not showing any projects atm. did a re-pull after removing the images with "docker rmi" on the image pathj |
| 20:11:34 | | nertzy__ quits [Ping timeout: 258 seconds] |
| 20:22:06 | <@Kaz> | uh |
| 20:22:09 | <@Kaz> | can anyone else verify that |
| 20:22:14 | <@Kaz> | did warrior.json just go walkies |
| 20:25:44 | <knecht420> | warrior is running fine, people are just having trouble manually updating |
| 20:35:13 | <p1nk> | I'm going to clear all containers again and redeploy |
| 20:48:12 | <p1nk> | Yeah - warrior still seems busted on my end - only available projects lists: "ArchiveTeam’s Choice". Side bar says "The warrior is idle" and image versions are as follows: |
| 20:48:13 | <p1nk> | atdr.meo.ws/archiveteam/warrior-dockerfile latest b725c800d70b 3 hours ago 233MB |
| 20:48:13 | <p1nk> | containrrr/watchtower latest dd78a816fb76 5 months ago 16.4MB |
| 20:59:28 | | qwertyasdfuiopghjkl joins |
| 21:09:39 | <p1nk> | Think I figured it out |
| 21:10:15 | <@arkiver> | p1nk: what was the solution? |
| 21:10:33 | <@JAA> | I'm guessing it failed to connect to warriorhq for some reason? |
| 21:11:07 | <p1nk> | That's what was happening. Looks like in an attempt to block external access to the warrior, an --iptables=false was added to the docker service |
| 21:11:27 | <p1nk> | I spun up a ubuntu container to do a ping check and that's when I realized it. |
| 21:11:37 | <p1nk> | Sorry for the spam. Thanks for the help |
| 21:12:45 | <@JAA> | Ah, yeah, that would do it. |