| 00:52:20 | <ctag> | I'm seeing a lot of wget-at stack traces on the docker container. Can anyone advise if this is known, or where to report? |
| 00:52:21 | | M--mlv|m joins |
| 01:50:03 | <TheTechRobo> | ctag: What specifically are you seeing, and on what project? |
| 02:02:16 | | DogsRNice quits [Read error: Connection reset by peer] |
| 02:21:24 | | colepaws joins |
| 03:15:04 | <ctag> | TheTechRobo warrior auto. Do you have a preferred pastebin? |
| 03:16:42 | <TheTechRobo> | ctag: transfer.archivete.am is our official one. |
| 03:27:35 | <ctag> | Thanks |
| 03:27:37 | <ctag> | https://transfer.archivete.am/5ZD7u/wget-at.txt |
| 03:27:37 | <eggdrop> | inline (for browser viewing): https://transfer.archivete.am/inline/5ZD7u/wget-at.txt |
| 03:43:14 | <TheTechRobo> | Uhh |
| 03:43:22 | <TheTechRobo> | That looks bad |
| 03:44:09 | <TheTechRobo> | Cc JAA; weird wget crashes |
| 03:44:33 | <TheTechRobo> | ctag: Are you running Wget-AT on x86_64? |
| 03:44:45 | <TheTechRobo> | er, sorry, s/Wget-AT/the Warrior/ |
| 03:45:09 | | datechnoman quits [Quit: The Lounge - https://thelounge.chat] |
| 03:45:10 | <TheTechRobo> | Also, are any items succeeding? |
| 03:46:58 | | datechnoman (datechnoman) joins |
| 04:22:18 | <colepaws> | Just spun up my warrior session for the first time, it seems to be receiving a bit of error messages. |
| 04:22:18 | <colepaws> | "Bad response on first URL. Aborting item. Could not find CDNs". |
| 04:25:08 | <colepaws> | Seems to only be on the Telegram one |
| 05:51:09 | | thenes quits [Ping timeout: 240 seconds] |
| 05:54:48 | | thenes (thenes) joins |
| 06:41:01 | <Xanthon> | [colepaws] that's normal. it's just telegram's servers acting up. |
| 07:09:50 | | Unholy236192464537713 quits [Ping timeout: 260 seconds] |
| 07:10:03 | | abirkill quits [Quit: Let us prepare to grapple with the ineffable itself, and see if we may not eff it after all.] |
| 07:10:30 | | abirkill (abirkill) joins |
| 07:32:55 | | evanim quits [Ping timeout: 255 seconds] |
| 07:33:04 | | evanim (evanim) joins |
| 07:46:46 | | angenieux quits [Quit: Ping timeout (120 seconds)] |
| 08:45:35 | | qwertyasdfuiopghjkl quits [Client Quit] |
| 09:02:54 | | colepaws quits [Quit: The Lounge - https://thelounge.chat] |
| 09:03:43 | | colepaws joins |
| 09:03:44 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 09:26:53 | | angenieux (angenieux) joins |
| 09:37:55 | <@JAA> | ctag: What's the host system CPU architecture? |
| 09:38:35 | <@JAA> | And how are you running it? VM or container? |
| 09:38:42 | <@JAA> | Er, you said container, nevermind. |
| 09:40:06 | <@JAA> | I'd guess you're on ARM, which is not supported. You can use Docker's x86_64 emulation via QEMU. |
| 10:25:18 | | sralracer joins |
| 10:25:53 | | sralracer is now authenticated as sralracer |
| 11:30:34 | | JaffaCakes118_2 (JaffaCakes118) joins |
| 11:34:13 | | JaffaCakes118 quits [Ping timeout: 258 seconds] |
| 12:33:35 | | BearFortress quits [Read error: Connection reset by peer] |
| 13:02:47 | <ctag> | TheTechRobo JAA Running docker compose in a LXC on x86_64 |
| 13:02:50 | <ctag> | > model name : Intel(R) Xeon(R) CPU E5645 @ 2.40GHz |
| 13:03:20 | <ctag> | Have the container stopped for now. Will check if items succeed when I get a chance. |
| 13:07:44 | | Aoede quits [Quit: ZNC - https://znc.in] |
| 13:10:26 | <@JAA> | Cc arkiver |
| 13:12:38 | | BearFortress joins |
| 13:56:55 | | cow_2001 quits [Quit: ✡] |
| 14:04:28 | | pocketwax17 (pocketwax17) joins |
| 14:33:01 | | MrMcNuggets (MrMcNuggets) joins |
| 14:45:11 | | MrMcNuggets quits [Client Quit] |
| 15:10:53 | | fuzzy80211 quits [Read error: Connection reset by peer] |
| 15:12:05 | | fuzzy80211 (fuzzy80211) joins |
| 15:45:27 | | qwertyasdfuiopghjkl quits [Client Quit] |
| 15:55:48 | | ctag quits [Quit: The Lounge - https://thelounge.chat] |
| 15:56:48 | | bladem quits [Read error: Connection reset by peer] |
| 15:58:22 | | PredatorIWD2 quits [Read error: Connection reset by peer] |
| 16:02:00 | | bladem (bladem) joins |
| 16:32:41 | | ctag (ctag) joins |
| 17:02:16 | | DogsRNice joins |
| 18:10:45 | | razul27 quits [Ping timeout: 260 seconds] |
| 18:11:07 | | razul27 joins |
| 18:11:51 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 18:15:21 | | razul271 joins |
| 18:17:45 | | razul27 quits [Ping timeout: 260 seconds] |
| 18:17:45 | | razul271 is now known as razul27 |
| 19:11:19 | | Cysioland quits [Remote host closed the connection] |
| 19:26:51 | | nulldata quits [Quit: Ping timeout (120 seconds)] |
| 19:29:49 | | nulldata (nulldata) joins |
| 19:43:36 | | Cysioland (Cysioland) joins |
| 19:54:23 | | Aoede (Aoede) joins |
| 20:50:35 | | Aoede quits [Ping timeout: 260 seconds] |
| 20:53:30 | | Chris5010 quits [Ping timeout: 260 seconds] |
| 20:53:48 | | Chris5010 (Chris5010) joins |
| 21:04:26 | | Aoede (Aoede) joins |
| 21:06:19 | <colepaws> | Xanthon Thanks for clarifying |
| 22:09:55 | | sralracer quits [Client Quit] |
| 22:26:08 | | andrew9 (andrew) joins |
| 22:27:31 | | andrew quits [Ping timeout: 255 seconds] |
| 22:27:32 | | andrew9 is now known as andrew |
| 23:37:22 | <ctag> | I see both failures and what I think are successes in the warrior webpage. |
| 23:38:01 | <ctag> | > server returned bad response |
| 23:39:00 | <ctag> | And others: > tracker confirmed item |