00:14:10 <m-relay_> <j​0j0xmr:monero.social> Are there plans for a hard fork any time soon?
00:16:05 <m-relay_> <j​0j0xmr:monero.social> Or will the next one be FCMP?
00:43:42 <nioCat> FCMP
08:35:07 <Webitect> Hello, I'm trying to run a monero node on my raspberry pi 4. For the last 2 days I've been prunning the blockchain and got about 75% done, when I checked on it again I was getting an error that the daemon wasn't running so when trying to start it back up again I received this error
08:35:09 <Webitect> Fatal glibc error: malloc assertion failure in sysmalloc: (old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)
08:37:39 <m-relay_> <a​surar0:monero.social> Hello, is this the whole error message?
08:38:15 <Webitect> Yes
08:42:25 <m-relay_> <a​surar0:monero.social> I'm surprised to see a glibc static assertion failure, as this is an unusual occurrence. It's possible that memory corruption may be the cause. Would you consider attempting a full resynchronization of your node?
08:45:08 <m-relay_> <a​surar0:monero.social> edit: glibc assertion failure
08:54:03 <moneromooo> Restarting with valgrind might give a clue. If valgrind runs on that machine.
08:54:27 <moneromooo> If you built it yourself, biulding with -g might give better info.
08:54:43 <moneromooo> Building with ASAN should give even better info, but might hide the bug.
09:00:01 <m-relay_> <a​surar0:monero.social> According to users on Raspberry Pi forum, Valgrind is fully supported on Raspberri Pi hardware. Hopefully if the issue persist Webitect will be able to use it
09:46:36 <aperechnev> Hi everyone! I opened a very simple pull request to make Monero compilable on FreeBSD: https://github.com/monero-project/monero/pull/9475
23:17:48 <m-relay_> <s​arg22:matrix.org> Getting "Daemon is busy" error when running "start_mining", I'm experimenting with a private testnet with two nodes. I mined 100 blocks in "--offline" mode, that seems to work fine, but otherwise mining doesn't start. Both nodes are 100/100 block height synced yet for some reason it replies with "BUSY" when trying to mine like its stuck in syncing