HomeSearchPrevious dayNext day

00:40:07sralracer quits [Client Quit]
02:57:29cow_2001 quits [Quit: ✡]
02:58:37cow_2001 joins
03:01:56nulldata quits [Quit: Ping timeout (120 seconds)]
03:03:50nulldata (nulldata) joins
04:04:30razul27 quits [Ping timeout: 252 seconds]
04:09:27nulldata quits [Client Quit]
04:11:21nulldata (nulldata) joins
04:12:21razul27 joins
04:41:40Unholy2361924645377131 quits [Ping timeout: 260 seconds]
07:06:03Unholy2361924645377131 (Unholy2361) joins
07:10:57TheTechRobo quits [Ping timeout: 252 seconds]
07:11:09TheTechRobo (TheTechRobo) joins
07:12:45@rewby quits [Ping timeout: 260 seconds]
08:37:05rewby (rewby) joins
08:37:05@ChanServ sets mode: +o rewby
10:36:22sralracer joins
11:14:09nulldata0 (nulldata) joins
11:14:46nulldata quits [Ping timeout: 255 seconds]
11:14:47nulldata0 is now known as nulldata
12:00:02Bleo182600722719623 quits [Quit: The Lounge - https://thelounge.chat]
12:02:46Bleo182600722719623 joins
12:05:57thenes quits [Ping timeout: 240 seconds]
12:08:04thenes (thenes) joins
12:35:49<sralracer>https://justpaste.it/cn1fr
12:36:25<sralracer>this is what all of my warrior instances are seeing after the latest update arkiver
12:36:57<mls>Cheers sralracer, was just about to mention it.
12:51:21th3z0l4_ quits [Read error: Connection reset by peer]
12:52:17th3z0l4 joins
13:06:48th3z0l4 quits [Ping timeout: 252 seconds]
13:07:23th3z0l4 joins
14:12:15<sralracer>could it be that both the wget-at version and the project version being the same gives issues?
14:23:22<mls>It seems like atdr doesn't have a updated grab-base yet and no wget-at
14:23:48<mls>no updated wget-at*
14:31:48<mls>Nope, that doesn't seem to be the case either
14:50:22<mls>On a warrior running telegram I have two versions of wget (wget-at, wget-at-gnutls) and are version 1.21.3-at.20231215.01
15:26:40<TheTechRobo>The warrior installs its own Wget-AT and has to be updated. It doesn't use the standalone docker images because that would require nested Docker containers. Which is iffy.
15:56:26Raithmir joins
15:58:46<Raithmir>I've noticed today that most projects fail to install due to not finding a suitable wget. I'm using version 4 VM, guessing I should probably download and deploy the latest version again?
15:58:46<Raithmir>"Exception: No usable Wget+At found.
15:58:47<Raithmir>2024-11-19 15:51:27,668 - seesaw.warrior - WARNING - Project askfm did not install correctly and we're ignoring this problem."
15:59:11<sralracer>this was just fixed Raithmir
15:59:33<Raithmir>Oh cool, guess I'll give it a while then.
16:02:38<mls>TheTechRobo Yea I can see how that can become rather messy. Thanks for the info.
16:07:05pabs quits [Ping timeout: 260 seconds]
16:10:20pabs (pabs) joins
16:15:07Raithmir quits [Client Quit]
16:48:44<TheTechRobo>Raithmir: To fix the problem immediately, try rebooting the warrior.
17:19:24wessel1512 joins
17:19:30bladem quits [Read error: Connection reset by peer]
17:56:45pabs quits [Ping timeout: 260 seconds]
17:59:10sralracer quits [Client Quit]
18:00:11pabs (pabs) joins
21:07:14alexlehm quits [Remote host closed the connection]
21:07:34Sluggs quits [Quit: ZNC - http://znc.in]
21:07:38alexlehm (alexlehm) joins
21:08:36Barto quits [Quit: WeeChat 4.4.3]
21:09:15katia_ quits [Ping timeout: 260 seconds]
21:09:50@JAA quits [Ping timeout: 260 seconds]
21:11:09JAA (JAA) joins
21:11:09@ChanServ sets mode: +o JAA
21:16:29Sluggs joins
21:17:40katia_ (katia) joins
21:43:41Barto (Barto) joins
22:04:35@JAA quits [Remote host closed the connection]
22:05:11JAA (JAA) joins
22:05:11@ChanServ sets mode: +o JAA
22:29:45Unholy2361924645377131 quits [Ping timeout: 260 seconds]

HomeSearchPrevious dayNext day