| 02:17:21 | <Ryz> | I'm not sure if it's just me, or is the Warrior instance not working? I'm looking at the dashboard via the web and it's not showing stuff? I'm not sure if it's picking up any tasks assigned when selecting a project |
| 02:21:37 | <Ryz> | fatal: unable to access 'https://github.com/ArchiveTeam/telegram-grab/': getaddrinfo() thread failed to start |
| 02:21:40 | <Ryz> | ...Huh? |
| 02:23:31 | <Ryz> | I tried to switch to another project and I got the same result? |
| 02:24:18 | <Ryz> | JAA or anyone else? |
| 02:24:46 | <Ryz> | This on a new Warrior install; I encountered it earlier and thought it didn't install correctly so I did a new install, same the same result |
| 02:28:09 | <Ryz> | Feels like a first I encounter this glitch or bug, since I semi-regularly uninstall and reinstall because of hard drive space concerns |
| 02:32:26 | <@JAA> | Hmm, maybe something broke with last night's updates? |
| 02:32:28 | <@JAA> | arkiver: ^ |
| 03:09:30 | | nathanielcwm quits [*.net *.split] |
| 03:09:30 | | yetanotherarchiver|m quits [*.net *.split] |
| 03:09:30 | | IndustrialRobot|m quits [*.net *.split] |
| 03:09:30 | | M--mlv|m quits [*.net *.split] |
| 03:09:30 | | jkap quits [*.net *.split] |
| 03:09:30 | | piraces|m quits [*.net *.split] |
| 03:09:31 | | jwoglom|m quits [*.net *.split] |
| 03:09:31 | | akaibu|m quits [*.net *.split] |
| 03:09:31 | | JC|m quits [*.net *.split] |
| 03:09:32 | | Max|m12 quits [*.net *.split] |
| 03:09:32 | | octylFractal|m quits [*.net *.split] |
| 03:09:32 | | wrangle|m quits [*.net *.split] |
| 03:09:32 | | tech234a|m quits [*.net *.split] |
| 03:09:32 | | Roki_100|m quits [*.net *.split] |
| 03:09:32 | | moe-a-m|m quits [*.net *.split] |
| 03:09:32 | | schwarzkatz|m quits [*.net *.split] |
| 03:09:32 | | jackt1365|m quits [*.net *.split] |
| 03:09:33 | | Minkafighter|m quits [*.net *.split] |
| 03:09:33 | | x9fff00 quits [*.net *.split] |
| 03:09:33 | | Exorcism quits [*.net *.split] |
| 03:09:33 | | phaeton quits [*.net *.split] |
| 03:09:33 | | manu|m quits [*.net *.split] |
| 03:09:33 | | CrispyAlice2 quits [*.net *.split] |
| 03:09:33 | | s-crypt|m|m quits [*.net *.split] |
| 03:09:33 | | Hans5958 quits [*.net *.split] |
| 03:09:33 | | Thibaultmol quits [*.net *.split] |
| 03:09:33 | | nstrom|m quits [*.net *.split] |
| 03:09:33 | | mpeter|m quits [*.net *.split] |
| 03:09:33 | | theblazehen|m quits [*.net *.split] |
| 03:09:33 | | Vokun quits [*.net *.split] |
| 03:09:34 | | britmob|m quits [*.net *.split] |
| 03:09:34 | | mind_combatant quits [*.net *.split] |
| 03:09:34 | | DigitalDragon quits [*.net *.split] |
| 03:09:34 | | @Sanqui|m quits [*.net *.split] |
| 03:09:34 | | igneousx quits [*.net *.split] |
| 03:25:26 | | mpeter|m joins |
| 03:25:54 | | mpeter|m quits [*.net *.split] |
| 03:27:22 | | mpeter|m joins |
| 03:28:47 | | mind_combatant joins |
| 03:28:47 | | theblazehen|m joins |
| 03:28:47 | | Hans5958 (Hans5958) joins |
| 03:28:47 | | jackt1365|m joins |
| 03:28:47 | | DigitalDragon (DigitalDragon) joins |
| 03:28:47 | | britmob|m joins |
| 03:28:47 | | igneousx (igneousx) joins |
| 03:28:47 | | tech234a|m joins |
| 03:28:47 | | Sanqui|m (Sanqui) joins |
| 03:28:47 | | @ChanServ sets mode: +o Sanqui|m |
| 03:28:47 | | schwarzkatz|m joins |
| 03:28:47 | | Thibaultmol joins |
| 03:28:47 | | akaibu|m joins |
| 03:28:47 | | Minkafighter|m joins |
| 03:28:48 | | CrispyAlice2 (CrispyAlice2) joins |
| 03:28:48 | | x9fff00 (x9fff00) joins |
| 03:28:48 | | moe-a-m|m joins |
| 03:28:48 | | wrangle|m joins |
| 03:28:48 | | jwoglom|m joins |
| 03:28:48 | | octylFractal|m joins |
| 03:28:48 | | Max|m12 joins |
| 03:28:48 | | Roki_100|m joins |
| 03:28:48 | | Vokun (Vokun) joins |
| 03:28:48 | | nstrom|m joins |
| 03:28:48 | | phaeton (phaeton) joins |
| 03:28:49 | | s-crypt|m|m joins |
| 03:28:49 | | JC|m joins |
| 03:28:49 | | Exorcism (exorcism) joins |
| 03:28:49 | | manu|m joins |
| 03:29:17 | | piraces|m joins |
| 03:29:17 | | jkap (jkap) joins |
| 03:29:18 | | IndustrialRobot|m joins |
| 03:29:19 | | yetanotherarchiver|m joins |
| 03:29:19 | | nathanielcwm joins |
| 04:04:11 | | saumon quits [Ping timeout: 272 seconds] |
| 04:55:26 | <@arkiver> | Ryz: thanks! that is odd, i'm checking it |
| 04:55:28 | | M--mlv|m joins |
| 04:55:48 | <@arkiver> | it also somewhat sounds like a possible github error |
| 04:55:54 | <@arkiver> | or... not sure |
| 04:55:57 | <@arkiver> | let me run it myself |
| 04:58:25 | <@arkiver> | Ryz: are you using the warrior-dockerfile? |
| 04:58:30 | <@arkiver> | (the warrior-dockerfile works for me) |
| 04:58:34 | <@arkiver> | what exactly are you using? |
| 05:13:57 | <Ryz> | arkiver, I just use https://warriorhq.archiveteam.org/downloads/warrior3/archiveteam-warrior-v3.2-20210306.ova - from https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior via https://warriorhq.archiveteam.org/downloads/warrior3/ |
| 05:14:27 | <Ryz> | I downloaded it back in 2023 April and kept reusing it |
| 05:23:16 | <@arkiver> | Ryz: btw there is a new one :) warrior4 |
| 05:23:25 | <@arkiver> | but the projects should still work with warrior3 |
| 05:23:54 | <Ryz> | That's strange arkiver, I was selecting the Telegram and Reddit project, and both of those didn't work for me :c |
| 05:23:57 | <@arkiver> | the warrior3 is https://github.com/ArchiveTeam/Ubuntu-Warrior |
| 05:24:06 | <@JAA> | Maybe it's unhappy about bookworm inside warrior-dockerfile? |
| 05:24:17 | <@arkiver> | could be |
| 05:26:19 | <Ryz> | What do? Get the new version? |
| 05:26:51 | <Ryz> | A bit odd since it doesn't seem to be warning me to upgrade or something |
| 05:35:38 | <@arkiver> | Ryz: normally it should just work |
| 05:39:33 | <@arkiver> | warrior reboots every 7 days |
| 05:47:45 | <@arkiver> | Ryz: i'm working on replicating the issue |
| 05:50:58 | <Ryz> | I did a fresh install on my main computer (my Warrior work mainly takes place on my gaming laptop), just to see if it's somehow just the gaming laptop; nope, same dealio |
| 05:51:15 | <Ryz> | I could give you the debug log and the details via the 'About' section if you want |
| 05:51:18 | <Ryz> | arkiver ^ |
| 05:51:44 | <@arkiver> | sure, you can post it to transfer.archivete.am |
| 05:54:27 | <Ryz> | Here you go arkiver: https://transfer.archivete.am/z0ywT/archiveteam-warrior-v3.2-20210306.ova-debugging |
| 06:05:05 | <@arkiver> | chfoo: i believe you may be most experienced with this, we recently updated warrior-dockerfile to Debian bookworm. and Ryz is seeing the error in the above log in the warrior3. do you have an idea what may be going on here? |
| 06:06:20 | | myself quits [Ping timeout: 240 seconds] |
| 06:09:02 | <Ryz> | Mmm, I tried three different projects since arkiver has told me that there are projects that work with warrior3, but they don't work :c |
| 06:12:00 | <@arkiver> | no |
| 06:12:12 | <@arkiver> | i said warrior-dockerfile still seems to be working |
| 06:12:25 | <@arkiver> | but apparently warrior-dockerfile is not working when used inside warrior3 |
| 06:17:45 | | myself (myself) joins |
| 06:21:05 | <Ryz> | That's so strange~ |
| 06:24:53 | <@arkiver> | i can't test it well at the moment with my current setup :/ |
| 06:25:00 | <fireonlive> | oh no eggdrop here |
| 06:25:08 | | eggdrop (eggdrop) joins |
| 06:45:09 | <@arkiver> | tech234a: i see you also did some work on the warrior with chfoo . do you perhaps have an idea on the above issue? |
| 06:45:41 | <@arkiver> | and does anyone else have the issue from Ryz ? (i can't replicate it well with my current setup) |
| 06:50:50 | <tech234a> | Just tried it out on 3.2 and I can reproduce |
| 07:16:22 | <@arkiver> | tech234a: well that is good and not good. do you have any idea what may be going on? |
| 07:16:38 | <tech234a> | likely related to an outdated version of Docker on the Alpine VM I think https://github.com/nextcloud/docker/issues/2049 |
| 07:17:12 | <tech234a> | seems like it's not really easy to upgrade the Docker version used within Alpine 3.13.2 at this point though |
| 07:22:10 | <@arkiver> | tech234a: i have little experience with alpine linux. could we just `apk add` a new version of Docker in startup.sh ? |
| 07:22:40 | <tech234a> | weirdly enough I get errors when trying to upgrade the packages on the system |
| 07:22:58 | <tech234a> | otherwise that would probably be the most direct solution |
| 07:31:46 | <@arkiver> | what are these errors? |
| 07:32:16 | <tech234a> | as a test I rebuilt the Warrior 3.2 image using Alpine 3.19.0, which has a newer version of Docker. That seemed to work, I'll see if the newer Docker package can run on an older Alpine |
| 07:32:33 | <tech234a> | let me check the error again |
| 07:34:27 | <@arkiver> | thanks a lot tech234a |
| 07:35:04 | <@arkiver> | if we do have to update Alpine, that is not something that can be done though `startup.sh` I believe? so people would have to manually get the new ova and set it up |
| 07:35:33 | <@JAA> | What's the status of warrior4, and why is it only mentioned in the warrior3 readme but not on the wiki? Not stable yet? |
| 07:38:03 | <tech234a> | warrior4 also worked fine when I tried it just now |
| 07:38:25 | <tech234a> | but I don't think you can automatically migrate people to that |
| 07:39:39 | <@JAA> | Yeah |
| 07:42:09 | <tech234a> | ERROR: http://dl-3.alpinelinux.org/alpine/v3.13/community: No such file or directory |
| 07:42:21 | <tech234a> | which loads just fine in my browser |
| 07:49:29 | <tech234a> | looks like switching to HTTPS fixes that issue per https://github.com/gliderlabs/docker-alpine/issues/386#issuecomment-880561565 |
| 07:53:42 | <tech234a> | ok it looks fairly simple to do an in-place Alpine upgrade and that seems to fix the issue |
| 07:54:09 | <@JAA> | But we can't run anything at the VM layer on existing workers, can we? |
| 07:54:39 | <@JAA> | So we could build a 3.3 image or whatever, but people would still need to replace it manually. |
| 07:55:38 | <tech234a> | JAA: in startup.sh we can |
| 07:56:02 | <tech234a> | I'm taking a look at that now |
| 08:01:02 | <@JAA> | tech234a: But startup.sh is part of the VM, not the Docker container, no? |
| 08:01:35 | <tech234a> | JAA: boot.sh can't be updated but startup.sh can. boot.sh downloads and executes startup.sh from GitHub |
| 08:01:41 | <@JAA> | Ah |
| 08:01:54 | <@JAA> | Scary but neat :-) |
| 08:02:06 | <tech234a> | I used this to upgrade Warrior 3.0 and 3.1 the last time changes needed to be made around the time 3.2 was released |
| 08:02:32 | <tech234a> | Someone theoretically could have a VM running untouched since 2017 |
| 08:39:28 | | saumon (saumon) joins |
| 10:30:46 | <tech234a> | https://github.com/ArchiveTeam/Ubuntu-Warrior/pull/30 |
| 10:32:22 | <tech234a> | This installs the necessary upgrade and fixes the issue on version 3.2 of the VM. Version 4 is unaffected. The PR EOLs 3.0, 3.1, and 3.2-beta because the upgrade doesn't seem to be possible on those versions; I'm not sure how many people still run those versions. |
| 10:33:05 | <tech234a> | One potential issue with this approach: this updates to the latest Docker/package versions available for Alpine Linux 3.19 at the time the upgrade occurs. As a result, different users may end up running slightly different versions of Docker and other packages. However, this will stabilize when Alpine Linux 3.19 loses support. |
| 10:55:39 | <@arkiver> | tech234a: awesome :) |
| 10:55:52 | <@arkiver> | is it save to simply update to Alpine 3.19 like this? |
| 10:56:50 | <@arkiver> | hmm should be fine |
| 10:57:13 | <tech234a> | I basically followed their wiki: https://wiki.alpinelinux.org/wiki/Upgrading_Alpine#Upgrading_an_Alpine_Linux_Hard-disk_installation |
| 10:59:15 | <tech234a> | The upgrade completes in about a minute and upgrades about 80 packages |
| 11:00:56 | <@arkiver> | sounds good |
| 11:01:01 | <@arkiver> | thanks for looking into this! |
| 11:07:34 | <tech234a> | one other minor issue occurred to me: if the upgrade gets interrupted for some reason, it probably wouldn't be automatically attempted again. I don't really see how that could happen, and if people do have that issue it would be fixable by adding more checks to startup.sh |
| 11:09:41 | <tech234a> | once this gets merged it would make sense to update the wiki to indicate that 3.2 and 4.0 are the only currently supported versions |
| 11:10:10 | <tech234a> | I don't think the wiki mentions 4.0 at all at this point |
| 11:25:46 | <@arkiver> | tech234a: can we write some dummy file somewhere to note 'update started', and remove it if 'update ended' |
| 11:26:12 | <@arkiver> | then if it's interrupted, we'll see the dummy file, and know the update never ended, and do the update as usual (and eventually remove the file then when 'update ended') |
| 11:26:43 | <tech234a> | yeah that could work though I guess the script would also need to detect if one of its subcommands failed |
| 11:28:41 | <@arkiver> | if a subcommand fails, the entire thing fails, the dummy file stays there, and we'll retry next time? |
| 11:29:18 | <tech234a> | that works |
| 12:49:04 | <tech234a> | Update interruption checking has been added |
| 14:43:39 | | qwertyasdfuiopghjkl quits [Client Quit] |
| 15:58:12 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 16:20:04 | | DogsRNice joins |
| 16:48:22 | <@chfoo> | i merged the pull request now |
| 17:25:59 | | bladem quits [Ping timeout: 272 seconds] |
| 17:27:00 | | bladem (bladem) joins |
| 18:30:57 | <fireonlive> | “ Someone theoretically could have a VM running untouched since 2017” neat |
| 19:51:38 | <tech234a> | chfoo: thanks |
| 20:51:45 | <tech234a> | Wiki is now updated to account for the EOL, add VM update instructions, and list version 4.0 alongside version 3.2 |
| 21:00:03 | | systwi quits [Ping timeout: 272 seconds] |
| 21:19:59 | | systwi (systwi) joins |
| 22:03:26 | <tech234a> | Ryz: if you reboot your 3.2 VM is it fixed now? |
| 22:23:13 | <tech234a> | interesting that GitHub has download stats on the API for various versions of the Warrior VM: 3.2: 4432 (+ 40 views on Internet Archive), 3.2-beta: 37, 3.1: 14, 3.0: 16 (+179 views on Internet Archive) https://api.github.com/repos/ArchiveTeam/Ubuntu-Warrior/releases. None of the 4.0 versions have more than 11 downloads on GitHub. Obviously this doesn't include the warriorhq.archiveteam.org or syping.de downloads though |