00:02:53 wow that's a lot of merges 14:00:40 hi anyone worked on monero private-testnet? 14:00:40 when I start to mine in private-testnet, the daemon stops 14:06:11 paste website logs and configs 14:06:25 use a paste website* for 14:06:44 https://github.com/monero-project/monero/issues/8369 14:06:57 issue has been raised in github, any solution please? 14:08:44 Completely different issue 14:08:45 https://github.com/monero-project/monero/issues/8821 14:09:00 sorry this is the one 14:10:01 Post the stack trace (gdb on the core, bt). You might have to build some files with -g -O0. 17:08:50 When the seed command is invoked on a multisig wallet, what's the string of hex chars shown? Is that just the private spend key? 17:09:06 s//CLI wallet `/, s//`/ 17:25:33 State needed to recreate. 17:26:48 * StaceyWarren[m] uploaded an image: (31KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/FJuvWvSTJopCpfJFrekvWJyz/image.png > 17:27:11 moneromooo: this is what I got 17:41:04 I assume you posted a stack trace as an attachment or something. If so, it does not show up through the relay. Paste on paste.debian.net. 17:41:18 Or if an image, ibb.co lets tor through. 17:43:42 the image doesn't show a backtrace 17:44:30 [Inferior 1 (process 352) exited with code 05] 17:47:18 StaceyWarren[m]: it doesn't crash, monerod exits 17:47:24 this is not like the issue you linked 17:49:04 how much free RAM do you have? 17:50:44 dmesg will log OOM kills. 18:17:22 it says "couldn't allocate RandomX dataset using large pages" and then exits 18:25:00 That's not an error, it will go on allocating normal pages. 18:25:27 If the exit isn't a normal exit/return, you can try running in gdb/ 18:25:36 Before running, add "catch throw". 18:25:58 Type "cont" if it breaks on early exceptions such as the one above. 18:37:31 that's the photo they shared https://usercontent.irccloud-cdn.com/file/WWIoNqUP/image.png 18:40:54 Ah, then gdb needs to stop earlier. An exception is a fair bet. 18:41:19 But OOM is indeed a fairer one. 18:41:36 I think we'd get a message with a top level catch. 18:42:25 look, I run "man -k oom" and of course it's full of systemd stuf... 18:42:43 I guess I should run systemman nowadays...