| 01:39:01 | | Makusu8 (Makusu) joins |
| 01:41:09 | | Makusu quits [Ping timeout: 260 seconds] |
| 01:41:09 | | Makusu8 is now known as Makusu |
| 03:45:03 | | DogsRNice quits [Read error: Connection reset by peer] |
| 04:12:22 | | nathang21 quits [Remote host closed the connection] |
| 04:58:37 | | thenes quits [Remote host closed the connection] |
| 04:59:00 | | thenes (thenes) joins |
| 05:11:00 | | thenes quits [Remote host closed the connection] |
| 05:11:15 | | thenes (thenes) joins |
| 05:13:22 | | nathang21 joins |
| 05:18:03 | | nathang21 quits [Client Quit] |
| 05:19:11 | | nathang21 joins |
| 06:37:53 | | zhongfu quits [Quit: cya losers] |
| 08:26:55 | | playzn joins |
| 08:28:15 | <playzn> | does warrior use grab-site? |
| 08:28:38 | <playzn> | or does it use any other proprietary archival tool? |
| 08:35:10 | | Exorcism|irc quits [Quit: Ping timeout (120 seconds)] |
| 08:35:13 | | DigitalDragons quits [Quit: Ping timeout (120 seconds)] |
| 08:35:50 | | Exorcism|irc (exorcism) joins |
| 08:36:54 | | zhongfu (zhongfu) joins |
| 08:37:54 | | DigitalDragons (DigitalDragons) joins |
| 08:42:14 | <anonymoususer852> | "does warrior use grab-site?" pretty sure it does use grab-site. |
| 09:39:34 | | playzn quits [Client Quit] |
| 11:00:03 | | Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat] |
| 11:02:49 | | Bleo182600722719623455222 joins |
| 11:44:14 | | BornOn420 quits [Remote host closed the connection] |
| 11:44:14 | | thenes quits [Remote host closed the connection] |
| 12:32:11 | <TheTechRobo> | It uses Wget-AT: https://github.com/ArchiveTeam/wget-lua |
| 12:32:48 | <TheTechRobo> | A few projects used wpull, which grab-site uses internally. I don't think any project has directly used grab-site, since it's more meant for manual crawling. |
| 12:51:38 | <anonymoususer852> | !tell playzn See https://irclogs.archivete.am/warrior/2025-08-22#l9c9adef0 for correct answer to warrior using grab-site. |
| 12:51:39 | <eggdrop> | [tell] ok, I'll tell playzn when they join next |
| 13:54:06 | | FiTheArchiver joins |
| 13:59:04 | | FiTheArchiver quits [Ping timeout: 260 seconds] |
| 15:37:19 | | phillipsjk joins |
| 15:40:15 | <phillipsjk> | So I had both may watchtower and warrior die on me (during last few days of AT choice). Assuming OOM: as I only have 3.6GiB of available memory. |
| 15:40:26 | <phillipsjk> | (using docker) |
| 15:46:29 | <anonymoususer852> | You can try checking system logs to see if it is really OOM. |
| 15:50:34 | <phillipsjk> | "sudo cat /var/log/dmesg | grep OOM" gave no results. |
| 15:55:03 | <phillipsjk> | Ooops that is only boot messages. |
| 15:55:36 | | BornOn420_ (BornOn420) joins |
| 15:59:20 | <anonymoususer852> | Could try "journalctl --grep=OOM" if your machine is using systemd. |
| 16:00:36 | <phillipsjk> | Looks like a network change may have been the culprit:2025-08-21T11:12:18.757340-06:00 fran kernel: [611352.577011] veth6ae234d: renamed from eth0 |
| 16:00:36 | <phillipsjk> | 2025-08-21T11:12:18.829464-06:00 fran kernel: [611352.649132] docker0: port 2(veth05d47f1) entered disabled state |
| 16:00:36 | <phillipsjk> | 2025-08-21T11:12:18.833456-06:00 fran kernel: [611352.651912] device veth05d47f1 left promiscuous mode |
| 16:00:45 | | thenes (thenes) joins |
| 16:00:59 | <phillipsjk> | Not using systemd. |
| 16:01:29 | <phillipsjk> | That is from kern.log |
| 16:03:30 | <phillipsjk> | That could be just a symptom of docker going down too I suppose. |
| 16:03:41 | <anonymoususer852> | I doubt that would cause the two docker instance to die. Network interface renaming typically happens once, and that's at the start I believe. |
| 16:03:52 | <anonymoususer852> | Try "docker ps -a" or something. |
| 16:04:32 | <anonymoususer852> | s/instance/&s/ |
| 16:05:15 | <phillipsjk> | oh there is a docker log. |
| 16:07:46 | <phillipsjk> | time="2025-08-21T11:12:18.609125255-06:00" level=info msg="shim disconnected" id=a0cbdd56ebe720b235fb34c4cca41123381e39dbbca0b9462bf1a68dfdbb5bab |
| 16:07:47 | <phillipsjk> | time="2025-08-21T11:12:18.609406755-06:00" level=warning msg="cleaning up after shim disconnected" id=a0cbdd56ebe720b235fb34c4cca41123381e39dbbca0b9462bf1a68dfdbb5bab namespace=moby |
| 16:07:47 | <phillipsjk> | time="2025-08-21T11:12:18.609453688-06:00" level=info msg="cleaning up dead shim" |
| 16:07:47 | <phillipsjk> | time="2025-08-21T11:12:18.610179029-06:00" level=info msg="ignoring event" container=a0cbdd56ebe720b235fb34c4cca41123381e39dbbca0b9462bf1a68dfdbb5bab module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete" |
| 16:07:49 | <phillipsjk> | time="2025-08-21T11:12:18.647340947-06:00" level=warning msg="cleanup warnings time=\"2025-08-21T11:12:18-06:00\" level=info msg=\"starting signal loop\" namespace=moby pid=11713 runtime=io.containerd.runc.v2\ntime=\"2025-08-21T11:12:18-06:00\" level=warning msg=\"failed to remove runc container\" error=\"runc did not terminate successfully: exit status 255: \" runtime=io.containerd.runc.v2\n" |
| 16:08:26 | <anonymoususer852> | I'd just do something like "grep -Ri "OOM" /var/log/*" to get a list of files that contains such word (case-insensitive). Then view the returned matches more closely to see if the results are as intended. |
| 16:11:15 | <anonymoususer852> | That paste isn't an output of OOM. Something like this https://tunnelix.com/wp-content/uploads/2017/07/Screen-Shot-2017-07-03-at-10.47.06-PM.png should be what OOM is. |
| 16:12:51 | <phillipsjk> | The paste was just what happened when the docker net dropped yesterday. May not be OOM. |
| 16:13:48 | <anonymoususer852> | Here's what OOM should roughly look like, "Aug 19 22:00:02 linux kernel: Out of memory: Killed process 1210928 (mkfs.erofs) total-vm:7854680kB, anon-rss:2174192kB, file-rss:1676kB, shmem-rss:0kB, UID:1000 pgtables:15316kB oom_score_adj:200" |
| 16:14:26 | <phillipsjk> | The suggested command has a bunch of false positives like: "/var/log/installer/cdebconf/templates.dat:Description-et.UTF-8: Köitegrupi loomisel ilmnes viga" -- nothing memory related. |
| 16:15:49 | <anonymoususer852> | 'grep -R "Out of memory" *'? Try that |
| 16:16:42 | <anonymoususer852> | 'grep -R "Out of memory" /var/log/*' Even. |
| 16:18:21 | <phillipsjk> | Only memory mention is boot messages and Xorg mention my video memory is only 3MB (explaining the 1024x768 resolution limit) |
| 16:20:19 | <anonymoususer852> | Pretty sure you didn't reap OOM killer in that case. Something else is causing those processes to die, and I just don't think renamed network interfaces would cause that. |
| 16:23:35 | <phillipsjk> | I lied slightly: I apparently could scroll up more. Docker memory monitoring messages were from March though. (I deleted an reinstalled the appliances after updates broke them.) |
| 16:24:34 | <anonymoususer852> | Also your machine should be reacting very poorly before/during OOM killer is reaped, especially if you also use HDD this behavior is easily distinguishable. |
| 16:25:15 | <phillipsjk> | Actually have an SSD, no swap. |
| 16:26:47 | <anonymoususer852> | I'd question why no swap even if you're using SSD. I have a spare machine that has like a bit under 3GB of available memory, and I use zram (as swap) with that. Then again, that might not be related. |
| 16:28:24 | <anonymoususer852> | I suppose the next time you notice your warrior instances are killed, check system logs then and there, especially the latest entries towards the bottom. |
| 16:29:43 | <phillipsjk> | I think I did not want the performance penalty on encrypted swap. Low power cpu and when I set up the machine I was using it to move cryptocurrency on a "clean" machine. |
| 16:31:48 | <phillipsjk> | Machine does not have ECC either. I use zram on my machine with ECC RAM that I use for day to day things. |
| 16:34:53 | <anonymoususer852> | I use zram on machines without ECC RAM. Encrypted swap is a bit fancy for my liking. |
| 16:53:58 | | PredatorIWD25 quits [Read error: Connection reset by peer] |
| 16:57:09 | | PredatorIWD25 joins |
| 17:00:45 | <phillipsjk> | Did not want to risk a bit flip making $24,000 CAD go *poof* due to a bit flip. Though checksums on the Bitcoin network should have protected me (would have to check if the encoded address on the wire is checksummed).. |
| 17:04:24 | <anonymoususer852> | I understand that there's money riding on your use of ECC RAM, but that's not a requirement with Warrior client, otherwise that would be a bit of a tall requirement. It's just that swap device should always be available as triggering OOM killer is never fun. |
| 17:04:45 | | thenes quits [Remote host closed the connection] |
| 17:05:13 | | thenes (thenes) joins |
| 17:10:08 | <anonymoususer852> | I have had OOM killer reaping more often than not in the past, where I avoided having any swap, because of performance penalties especially with HDD. Learned that the hard way, and that zswap or better yet, zram as swap alleviated most of that concern. |
| 17:19:09 | | lemuria (lemuria) joins |
| 17:19:58 | <phillipsjk> | I checked the syslog from the times above: nothing logged before the net disconnection. |
| 17:20:28 | <anonymoususer852> | As in physically disconnected from net? |
| 17:20:49 | <phillipsjk> | Not as far as I know. |
| 17:21:15 | <phillipsjk> | I suppose I *could* have bumped it. |
| 17:22:55 | <anonymoususer852> | Those should be visible in system logs. I have had at times where I was briefly offline, but I don't recall the loss of Warrior instances during that offline period. Then again my setup is likely different from yours. |
| 17:24:16 | <anonymoususer852> | briefly offline == ISP kicked me offline without informing me beforehand. Not like they're obliged to either. |
| 17:24:24 | <phillipsjk> | A few other services restarted shortly after too: so maybe OOM is not being logged for some reason. |
| 17:25:24 | <anonymoususer852> | I still find it a bit hard to believe it would OOM killer to be honest. Without logs to indicate either way, it's really hard to know exactly what caused the mysterious death of your docker instances. |
| 17:25:46 | <anonymoususer852> | s/would/&\ be/ |
| 17:26:44 | <phillipsjk> | I think I will look into enabling swap just in case. The catch is I want to make sure it is encrypted in case I use the machine to send money again. |
| 17:28:10 | <anonymoususer852> | The lack of swap device could exacerbate OOM killer being reaped when system is totally out of "free-able" memory. The same could also be said even if you have swap device(s) and you still exhaust all of your available memory. |
| 17:30:05 | <anonymoususer852> | IoW, swap device(s) won't completely free you from witnessing OOM killer, it just delays the potentially deadly massacre. |
| 17:31:17 | <phillipsjk> | This is a "thin client" replacing my Pentium II-350Mhz machine with 384MB of RAM. It drew 40W: and I concluded I could save a lot on a UPS if I got a power efficient machine first. |
| 17:33:15 | <phillipsjk> | UPS battery died before I got around to reconfiguring VOIP :P |
| 17:35:03 | <anonymoususer852> | That poor machine could really use some memory upgrades. I have had in the past a Pentium II 400MHz with like 768MB of RAM. If theoretically running just Warrior alone (cross-compiled to x86-only), it wouldn't give the instance much headroom to play with. |
| 17:36:05 | <phillipsjk> | AFAIK 384MB was the max supported (3 128MB DIMMS) Hard drive was also getting noisy. |
| 17:37:03 | <phillipsjk> | Think client replacement has 8GB (some stolen for video/etc) |
| 17:37:09 | <anonymoususer852> | I ran Warrior in VM-only initially, with the standard 512MB RAM, it was a little quick to reap OOM killer back then. Alas, I have no logs of that ever since I began messing with the VM config. |
| 17:39:27 | <anonymoususer852> | The machine I have with a bit under 3GB of RAM is Core 2 Duo 1.6GHz under turbo mode, which hardly ever gets there. Even with my Warrior VM instances, I still use a bit under 3GB RAM as the model to base it on. |
| 17:41:04 | <phillipsjk> | firefox is the big memory hog: need to limit my tabs. |
| 17:41:42 | <anonymoususer852> | There's firefox extensions for that, something like discard tab is what I use. |
| 17:41:54 | <anonymoususer852> | s/discard/auto\ &/ |
| 17:42:31 | <phillipsjk> | only 400MB at the moment. |
| 17:43:59 | <anonymoususer852> | Modern GUI web browsers are generally memory heavy, no matter if it is firefox or chrome. :p I just keep having my eyes peeled on resource monitors, and the 'about:processes' as a dedicated tab in firefox. |
| 17:46:43 | <anonymoususer852> | Bonus points if you're using systemd, as you could also use cgroupsv2 to hard limit a processes' memory consumption, which it will then choose to hammer your disk I/O lol. |
| 18:05:56 | | thenes quits [Remote host closed the connection] |
| 18:06:13 | | thenes (thenes) joins |
| 18:21:29 | | BornOn420__ (BornOn420) joins |
| 18:24:30 | | BornOn420_ quits [Ping timeout: 255 seconds] |
| 21:12:14 | <phillipsjk> | ooh new UPS battery arrived! (went with LiPO4 drop-in replacement; need to de-rate UPS from like 900VA to 120VA (10A @ 12V) |
| 21:42:49 | | archiveDrill quits [Quit: The Lounge - https://thelounge.chat] |
| 21:52:56 | | archiveDrill joins |
| 22:37:58 | | DogsRNice joins |