HomeSearchPrevious dayNext day

00:05:54APOLLO03 joins
00:16:34Megame quits [Ping timeout: 250 seconds]
00:28:57etnguyen03 (etnguyen03) joins
00:44:33etnguyen03 quits [Client Quit]
00:48:11lennier2 joins
00:51:03lennier2_ quits [Ping timeout: 260 seconds]
00:59:09SkilledAlpaca418962 quits [Quit: SkilledAlpaca418962]
01:05:42Wohlstand (Wohlstand) joins
01:08:49SkilledAlpaca418962 joins
01:19:38scurvy_duck quits [Ping timeout: 260 seconds]
01:28:23etnguyen03 (etnguyen03) joins
01:30:40rohvani joins
01:44:44Island joins
02:28:49biscuitenjoyer12 joins
02:32:59<biscuitenjoyer12>howdy, are there any performance differences between the archiveteam-warrior versus one of the project specific containers?(the usgov-grab to be specific)
02:36:58lexikiq quits [Ping timeout: 250 seconds]
02:37:20lexikiq joins
02:49:17biscuitenjoyer12 quits [Client Quit]
02:59:30DopefishJustin quits [Ping timeout: 250 seconds]
03:02:56<TheTechRobo>!tell biscuitenjoyer12 The project-specific containers don't have a web UI so they will likely use RAM, although in practice the effect is likely minor. The real useful thing is that they put logs on stdout, which allows you to use log centralization tools if you have a lot of containers
03:02:56<eggdrop>[tell] ok, I'll tell biscuitenjoyer12 when they join next
03:10:30lunax quits [Remote host closed the connection]
03:18:44<nicolas17>use less* RAM?
03:30:54etnguyen03 quits [Remote host closed the connection]
03:46:28gust quits [Read error: Connection reset by peer]
04:05:22scurvy_duck joins
04:11:00<TheTechRobo>er, yeah
04:12:18lexikiq quits [Ping timeout: 260 seconds]
04:12:18seab5 joins
04:12:40lexikiq joins
04:12:52seab5 quits [Client Quit]
04:40:41Wohlstand quits [Remote host closed the connection]
04:45:28caylin quits [Read error: Connection reset by peer]
04:45:41caylin (caylin) joins
04:51:14BlueMaxima quits [Quit: Leaving]
04:51:18scurvy_duck quits [Ping timeout: 250 seconds]
05:00:29dendory quits [Quit: The Lounge - https://thelounge.chat]
05:00:49dendory (dendory) joins
06:15:44SootBector quits [Remote host closed the connection]
06:16:04SootBector (SootBector) joins
06:27:17BornOn420 quits [Remote host closed the connection]
06:27:44BornOn420 (BornOn420) joins
06:33:20DopefishJustin joins
06:40:37Justin[home] joins
06:44:33DopefishJustin quits [Ping timeout: 260 seconds]
06:44:45Justin[home] is now known as DopefishJustin
06:59:17lennier2 quits [Read error: Connection reset by peer]
06:59:33lennier2 joins
07:00:05beardicus quits [Quit: Ping timeout (120 seconds)]
07:02:36beardicus (beardicus) joins
08:20:52ahm2587 quits [Quit: The Lounge - https://thelounge.chat]
08:21:08ahm2587 joins
08:33:38nulldata quits [Ping timeout: 260 seconds]
09:22:03corentin5 quits [Ping timeout: 260 seconds]
09:46:06sparky14921 (sparky1492) joins
09:49:26sparky1492 quits [Ping timeout: 250 seconds]
09:49:27sparky14921 is now known as sparky1492
10:00:25Island quits [Read error: Connection reset by peer]
10:36:29sparky14926 (sparky1492) joins
10:40:13sparky1492 quits [Ping timeout: 260 seconds]
10:40:14sparky14926 is now known as sparky1492
10:46:29loug83181422 joins
10:48:30sec^nd quits [Remote host closed the connection]
10:48:56sec^nd (second) joins
10:57:12<@arkiver>some projects have been running a bit slow lately
10:57:19<@arkiver>it's due to the large amount of content being archived.
10:57:53<@arkiver>there's long term projects with backlog, short term projects and backlog still being uploaded
10:58:15<@arkiver>for example blogger and livestream will soon have their items finished, which is going to save enormously already
11:18:06<myself>Ooo that's exciting. All that stuff has been sitting out on staging disks this whole time?
11:23:08<@arkiver>yeah there's both crawling backlog and an upload backlog, but they're clearing out
11:23:15<@arkiver>it may take more weeks though
12:00:02Bleo18260072271962345 quits [Quit: The Lounge - https://thelounge.chat]
12:02:46Bleo18260072271962345 joins
12:22:45Wohlstand (Wohlstand) joins
12:34:19SkilledAlpaca418962 quits [Quit: SkilledAlpaca418962]
12:34:50SkilledAlpaca418962 joins
13:26:06notarobot1 quits [Ping timeout: 250 seconds]
14:14:18@rewby quits [Ping timeout: 260 seconds]
14:28:41NeonGlitch (NeonGlitch) joins
14:37:41rewby (rewby) joins
14:37:41@ChanServ sets mode: +o rewby
15:14:38Megame (Megame) joins
15:31:55Wohlstand quits [Quit: Wohlstand]
15:41:40sparky14924 (sparky1492) joins
15:45:18sparky1492 quits [Ping timeout: 260 seconds]
15:45:19sparky14924 is now known as sparky1492
15:55:29BornOn420_ (BornOn420) joins
15:58:58BornOn420 quits [Ping timeout: 276 seconds]
16:04:15scurvy_duck joins
16:09:22BornOn420_ quits [Ping timeout: 276 seconds]
16:22:54scurvy_duck quits [Ping timeout: 250 seconds]
16:23:10BornOn420 (BornOn420) joins
16:52:28<sparky1492> Good Day all, I started having an issue with one of my docker containers last week and have been slowing troubleshooting it and now i'm stuck on what else to try. It's unable to see the warrior projects, on the "Avaliable Projects" page when the docker warrior is running only shows "ArchiveTeam's Choice" and below that show an error message of
16:52:28<sparky1492>"Phooey… No warrior projects are available for participation yet!" This docker was running fine for a week or so, then I think it was after it restarted last week sometime. I've removed the image re-downloaded, changed the compose.yaml configurations to mostly vanilla. I have other docker images and VMs on other machines running just fine on
16:52:28<sparky1492>the same network. I've not been able to find anything online that has/shows anything about that error message.
16:54:36<sparky1492>Also to add to this, the graph for downloads and uploads is constantly active showing downloads and uploads. Also checked the data folder on the docker container and only shows the warrior logs and wget items. The logs only show this:
16:54:37<sparky1492>2025-03-03 16:43:01,952 - seesaw.warrior - DEBUG - Update warrior hq.
16:54:37<sparky1492>2025-03-03 16:43:01,952 - seesaw.warrior - DEBUG - Warrior ID ''.
16:54:37<sparky1492>2025-03-03 16:53:01,953 - seesaw.warrior - DEBUG - Update warrior hq.
16:54:37<sparky1492>2025-03-03 16:53:01,953 - seesaw.warrior - DEBUG - Warrior ID ''.
17:18:08<sparky1492>also my apologizes if this needs to be in another channel please let me know
17:19:21<Blueacid>arkiver: Is the backlog due to the limited ingest speed / slot count of the IA's infrastructure? Roughly how much is staged & in the queue for transferring?
17:19:40<Blueacid>(It's incredible just how much stuff there is - kudos to all of you for wranglin' all this infrastructure!)
17:27:33NeonGlitch quits [Client Quit]
17:42:17Megame quits [Client Quit]
17:42:37NeonGlitch (NeonGlitch) joins
18:13:02kansei quits [Quit: ZNC 1.9.1 - https://znc.in]
18:16:20kansei (kansei) joins
18:28:13kansei quits [Client Quit]
18:28:45Barto (Barto) joins
18:30:03nicolas17 quits [Quit: Konversation terminated!]
18:30:25kansei (kansei) joins
18:33:31Barto quits [Client Quit]
18:38:03Barto (Barto) joins
18:48:13gust joins
18:58:33gust quits [Remote host closed the connection]
18:58:52gust joins
19:00:08nicolas17 joins
19:24:02wyatt8740 quits [Ping timeout: 250 seconds]
19:27:53wyatt8740 joins

HomeSearchPrevious dayNext day