Upon the initial sync, I found the following error messages in the log: … 2026-04-07 18:38:35.491 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1618 Synced 3647399/3647400 (99%, 1 left) 2026-04-07 18:38:35.992 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1618 Synced 3647400/3647400 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2409 Synced 11449 blocks in 5.5 hours (0.58 blocks per second) 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 ********************************************************************** 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 You are now synchronized with the network. You may now start monero-wallet-cli. 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 Use the "help" command to see the list of available commands. 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 ********************************************************************** 2026-04-07 18:38:39.493 [P2P9] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem The level is ERROR, so probably at least a decrease in privacy is to worry about. Here is my ~/.config/systemd/user/monerod.service: [Unit] Description=Monero Node After=network.target [Service] Type=simple ExecStart=/usr/bin/monerod --data-dir /path_to_my_Monero_folder --prune-blockchain --log-file /path_to_my_Monero_folder/bitmonero.log --non-interactive Restart=always RestartSec=30 Environment=MONERO_RANDOMX_UMASK=1 Nice=19 IOSchedulingClass=idle [Install] WantedBy=default.target I'd be grateful for a fix. Albert
This could fix the error. Can you please test this?
Dear Bastian, Thank you for the patch! For an unknown reason, I didn't get an e-mail corresponding to your message #10. I checked bugs.debian.org/1132940 out of curiosity manually today and saw your message only now. Today, I upgraded the package to 0.18.5.0+~0+20260428-1, and the error did not occur today yet. The last four such errors happened before the upgrade and quite rarely: 2026-04-26 08:59:10.073 [P2P0] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-04-28 05:12:02.797 [P2P8] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-15 11:44:15.028 [P2P6] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-19 10:02:41.344 [P2P3] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem I checked out the code and applied your patch locally, but now I start running into all kinds of issues during build. For example, though I have cmake 3.31.6, `make` outputs pages of warnings, the earliest of which is this: CMake Deprecation Warning at external/randomx/CMakeLists.txt:29 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument value. Or, use the ... syntax to tell CMake that the project requires at least but has been updated to work with policies introduced by or earlier. My machine does not have a development environment suitable for proper code development, and I don't have any insight into the warnings. So even if the compilation ever succeeds (it takes long), and even if I succeed to start the compiled monerod, I'm unsure how useful my feedback would be; my apologies. Probably unrelated, but still better to mention this. Upon issuing `systemctl --user restart monerod` or `systemctl --user stop monerod` (with monerod from the Debian package 0.18.5.0+~0+20260428-1), I get this into the log: 2026-06-20 22:17:56.483 [SRV_MAIN] INFO global src/daemon/p2p.h:81 p2p net loop stopped 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:134 Exception: std::system_error 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:135 Unwound call stack: 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [1] 0xab) [0x555dede82aa6]:__cxa_throw+0xab) [0x555dede82aa6] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [2] /usr/bin/monerod(+0xbd701) [0x555dede7d701] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [3] /usr/bin/monerod(+0x73bfa9) [0x555dee4fbfa9] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [4] 0xbc97) [0x7f54092ebc97]:_64-linux-gnu/libboost_thread.so.1.90.0(+0xbc97) [0x7f54092ebc97] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [5] 0x92b7b) [0x7f540869eb7b]:_64-linux-gnu/libc.so.6(+0x92b7b) [0x7f540869eb7b] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [6] 0x1107f8) [0x7f540871c7f8]:_64-linux-gnu/libc.so.6(+0x1107f8) [0x7f540871c7f8] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 A stacktrace is probably not something we should expect during normal operation, should we? As a rule of thumb, an exit should be graceful; upon exit, a program should free its resources itself properly. Gratefully, Albert
Dear Bastian, Thank you for the patch! For an unknown reason, I didn't get an e-mail corresponding to your message #10. I checked bugs.debian.org/1132940 out of curiosity manually today and saw your message only now. Today, I upgraded the package to 0.18.5.0+~0+20260428-1, and the error did not occur today yet. The last four such errors happened before the upgrade and quite rarely: 2026-04-26 08:59:10.073 [P2P0] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-04-28 05:12:02.797 [P2P8] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-15 11:44:15.028 [P2P6] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-19 10:02:41.344 [P2P3] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem I checked out the code and applied your patch locally, but now I start running into all kinds of issues during build. For example, though I have cmake 3.31.6, `make` outputs pages of warnings, the earliest of which is this: CMake Deprecation Warning at external/randomx/CMakeLists.txt:29 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. My machine does not have a development environment suitable for proper code development, and I don't have any insight into the warnings. So even if the compilation ever succeeds (it takes long), and even if I succeed to start the compiled monerod, I'm unsure how useful my feedback would be; my apologies. Probably unrelated, but still better to mention this. Upon issuing `systemctl --user restart monerod` or `systemctl --user stop monerod` (with monerod from the Debian package 0.18.5.0+~0+20260428-1), I get this into the log: 2026-06-20 22:17:56.483 [SRV_MAIN] INFO global src/daemon/p2p.h:81 p2p net loop stopped 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:134 Exception: std::system_error 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:135 Unwound call stack: 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [1] 0xab) [0x555dede82aa6]:__cxa_throw+0xab) [0x555dede82aa6] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [2] /usr/bin/monerod(+0xbd701) [0x555dede7d701] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [3] /usr/bin/monerod(+0x73bfa9) [0x555dee4fbfa9] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [4] 0xbc97) [0x7f54092ebc97]:_64-linux-gnu/libboost_thread.so.1.90.0(+0xbc97) [0x7f54092ebc97] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [5] 0x92b7b) [0x7f540869eb7b]:_64-linux-gnu/libc.so.6(+0x92b7b) [0x7f540869eb7b] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [6] 0x1107f8) [0x7f540871c7f8]:_64-linux-gnu/libc.so.6(+0x1107f8) [0x7f540871c7f8] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 A stacktrace is probably not something we should expect during normal operation, should we? As a rule of thumb, an exit should be graceful; upon exit, a program should free its resources itself properly. Gratefully, Albert
Several hours later, after tons of warnings, the build finished successfully. I started the just compiled monerod, and, so far, no error message of the type “ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem” has occurred.
Oh. The version I checked out using the public https://github.com/monero-project/monero.git (obtained from https://github.com/monero-project/monero , click on the green “Code“ ) turned to be 0.18.1 (according to /tmp/monero/bin/monerod --version), which is behind Debian's 0.18.5 (according to monerod --version). Why is the upstream version lower than the downstream one?! Anyway, forget my tests yesterday and today, as I apparently wasted lots of time for nothing.
And the new attempt with a new checkout (`git clone --recursive https://github.com/monero-project/monero https://github.com/monero-project/monero ` followed by `cd monero`, `git checkout release-v0.18`, and `make`) yielded a couple of warnings followed by an error CMake Error at /usr/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:233 (message): Could NOT find Boost (missing: locale) (found suitable version "1.83.0", minimum required is "1.62") Call Stack (most recent call first): /usr/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.31/Modules/FindBoost.cmake:2423 (find_package_handle_standard_args) CMakeLists.txt:1108 (find_package) I ran out of free AI-chatbot queries to ask how to proceed from here, so this is clearly above my level. I kindly ask for understanding that I won't be able to perform more development-level tests.
Please install the experimental version 0.18.5.0+~0+20260428-2~exp which includes the patch.
We believe that the bug you reported is fixed in the latest version of monero, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1132940@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann <bage@debian.org> (supplier of updated monero package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Mon, 22 Jun 2026 01:02:34 +0200 Source: monero Architecture: source Version: 0.18.5.0+~0+20260428-2~exp Distribution: experimental Urgency: medium Maintainer: Debian Cryptocoin Team <team+cryptocoin@tracker.debian.org> Changed-By: Bastian Germann <bage@debian.org> Closes: 1132940 Changes: monero (0.18.5.0+~0+20260428-2~exp) experimental; urgency=medium . * Fall back to unfiltered outgoing peers (Closes: #1132940) Checksums-Sha1: 02615acbc12e9172f7793ee438a1042b2a0481eb 2793 monero_0.18.5.0+~0+20260428-2~exp.dsc abec0e79e9d8b640258fb9569fa58dbf6d47c3d9 19824 monero_0.18.5.0+~0+20260428-2~exp.debian.tar.xz dca34843e72dae86f6084b299947dda84b70bfd8 10493 monero_0.18.5.0+~0+20260428-2~exp_source.buildinfo Checksums-Sha256: 1ddf65aa2dadab72c07c87ba63f203708be612918509087eb47feb9649135eec 2793 monero_0.18.5.0+~0+20260428-2~exp.dsc 9d3b0652123245b83b7e4e635eb1e767557fb2b37852619d8e81e01dbbc8edd3 19824 monero_0.18.5.0+~0+20260428-2~exp.debian.tar.xz 7c3aa7be3aba29f7e2772feb681fc8375b6c266708f21fe421709106392d460e 10493 monero_0.18.5.0+~0+20260428-2~exp_source.buildinfo Files: 19b8e348bfbd20528065a11122f9a38a 2793 utils optional monero_0.18.5.0+~0+20260428-2~exp.dsc a58c0db17ad4100b33fc4848093064fd 19824 utils optional monero_0.18.5.0+~0+20260428-2~exp.debian.tar.xz 04194674f4fffe2d9c6d4e5213d6e0e4 10493 utils optional monero_0.18.5.0+~0+20260428-2~exp_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmo4bb4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFKuODADErfgb1fJ7YuKoUE9n7qGPWGHUasaRs70a CSkia/b6JuCz5+4AYHhigGreFcYaKrL9iuhnioZ4OQXn5BH0GkVLMV0M0snWBs3q ExPVl3bsDOgxMI+eOcmkVFkBKlLDLZNlejNenlIFLbFmyg9mjVGynBfMQVTDpsCs 7iBR2pgHGMQwJoLQIisf0yISQI8j6AqiDYX/B8yGJXBTmJ2S1zOcEH7aeLRqz3+N wgWzNaBP5iivXMacI2KdtzNKHo5q56oVmpdPONhivq8MXELsQSlYmn8U+u5ajwPG hlDZ54Xax/+y34AOtlUzvHeAaegt1rizpVOl/5sI7mqFa6QHBaw27ZCfSMsWtVty 8hwJvSipZ6Udi3vWBE0lfzt7IPLnkFaSD6obOvNJHBJ9pEBcHYShWsvw4PJ8YWnX SoAzp+NbfJ16vhS8KjjgjZrcYk4KMBo+PKUYNzWzwrh24Def6JgJAljT5HjmGuyn rNoTCvt44utN3G0Ca5GcGMU5PWOjT/M= =+vnO -----END PGP SIGNATURE-----
Please check whether the patch works for you. I am not going to carry it to the next upload if I have not received an answer within one week.
Hi Bastian, The outgoing filter (against spam) on my e-mail server is too strong. I'm now looking for ways to provide the technical information to you; cf. the attachment. Best, Albert
By the way, with a higher log level we don't get much more information right before the crash: $ monerod --data-dir /path_to_my_Monero_dir --non-interactive --log-level 4 2026-10-01 20:23:59.937 I Monero 'Fluorine Fermi' (v0.18.5.0-unknown) 2026-10-01 20:23:59.937 I Moving from main() into the daemonize now. 2026-10-01 20:23:59.937 I Initializing cryptonote protocol... 2026-10-01 20:23:59.937 I Cryptonote protocol initialized OK 2026-10-01 20:23:59.939 T Blockchain::Blockchain 2026-10-01 20:23:59.939 I Initializing core... 2026-10-01 20:23:59.939 T BlockchainLMDB::BlockchainLMDB 2026-10-01 20:23:59.939 T BlockchainLMDB::get_db_name 2026-10-01 20:23:59.939 I Loading blockchain from folder /path_to_my_Monero_dir/lmdb ... 2026-10-01 20:23:59.940 D option: fast 2026-10-01 20:23:59.940 D option: async 2026-10-01 20:23:59.940 D option: 250000000bytes 2026-10-01 20:23:59.940 T BlockchainLMDB::open 2026-10-01 20:23:59.940 T BlockchainLMDB::need_resize 2026-10-01 20:23:59.940 D DB map size: 121995063296 2026-10-01 20:23:59.940 D Space used: 109599993856 2026-10-01 20:23:59.940 D Space remaining: 12395069440 2026-10-01 20:23:59.940 D Size threshold: 0 2026-10-01 20:23:59.940 D Percent used: 89.8397 Percent threshold: 90.0000 zsh: bus error monerod --data-dir /path_to_my_Monero_dir --non-interactive --log-level 4
The crash that you reported is an unrelated one. Which filesystem type are your monero database files located on? Which kernel version are you running? The crash is in LMDB. The last thing printed (DB map size / Space used / Percent used: 89.8397) comes from BlockchainLMDB::need_resize() in src/blockchain_db/lmdb/db_lmdb.cpp:640, called once from open() at line 1467. Because 89.8397 is below the 90.0000 threshold, no resize happens — so the crash is in mdb_txn_begin() (line 1480) or the lmdb_db_open() calls immediately after, i.e. LMDB opening the named sub-databases for the first time. The default --db-sync-mode fast:async:250000000bytes resolves to MDB_NOSYNC only (db_lmdb.cpp:1442). MDB_WRITEMAP is only set for fastest mode or on OpenBSD, so per mdb.c:4452-4460 your data.mdb is mapped PROT_READ/MAP_SHARED with no ftruncate. That rules out a write fault: SIGBUS here means the kernel couldn't back a page on read - either the offset is past EOF, or the underlying storage returned an error. Please also try with --db-sync-mode safe.
Please find my answer in the attachment (my apologies again; the outgoing e-mail server refuses to accept the technical data as main text).
We believe that the bug you reported is fixed in the latest version of monero, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1132940@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann <bage@debian.org> (supplier of updated monero package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Sun, 04 Oct 2026 17:26:32 +0200 Source: monero Architecture: source Version: 0.18.5.3+~0+20260428-1 Distribution: unstable Urgency: medium Maintainer: Debian Cryptocoin Team <team+cryptocoin@tracker.debian.org> Changed-By: Bastian Germann <bage@debian.org> Closes: 1132852 1132940 Changes: monero (0.18.5.3+~0+20260428-1) unstable; urgency=medium . * Team upload * Add note on suported file systems (Closes: #1132852, #1132940) * New upstream version 0.18.5.3+~0+20260428 Checksums-Sha1: 84ea76347dd333c465935d026f451c1f47a216e3 2777 monero_0.18.5.3+~0+20260428-1.dsc cb403be3f0656ecfdfb426a68f50ab5f975b6cf4 337695 monero_0.18.5.3+~0+20260428.orig-Xsupercop.tar.gz bcb2d5165f9d8f4188c031a1df09b77d8b3a774d 14196919 monero_0.18.5.3+~0+20260428.orig.tar.gz ac2e9f8f6f3296e3b31aee0d0c0d78b344546aa8 19332 monero_0.18.5.3+~0+20260428-1.debian.tar.xz fab33f54643166faa287c68509d681505b3d63a5 9176 monero_0.18.5.3+~0+20260428-1_source.buildinfo Checksums-Sha256: f4b7783c27ef98d8f6531a00edbebb269e1017af40ac93687b2cffb9e08b0067 2777 monero_0.18.5.3+~0+20260428-1.dsc 28b09708cd979124a9d5fe81d097d68b69085d57fc5a6663187dd342ef0c3486 337695 monero_0.18.5.3+~0+20260428.orig-Xsupercop.tar.gz 4e5ddc6a04b22c93088f53b9f443710f55739d907f712ff8739b7bbf75118b80 14196919 monero_0.18.5.3+~0+20260428.orig.tar.gz 39bb611db2bde522276cf8c11124cc2818eac900c026b47c1509a51424950168 19332 monero_0.18.5.3+~0+20260428-1.debian.tar.xz eddf9e74bd14213fd292f87b6a5223576ea9be1237ad573a8b9943fa6c28e587 9176 monero_0.18.5.3+~0+20260428-1_source.buildinfo Files: 0e0926b4443cc6ff21147affbc7abedc 2777 utils optional monero_0.18.5.3+~0+20260428-1.dsc 7c9de8c469829e610162d0886905da5b 337695 utils optional monero_0.18.5.3+~0+20260428.orig-Xsupercop.tar.gz aa998b8b9bd428710ba42567ffec6bad 14196919 utils optional monero_0.18.5.3+~0+20260428.orig.tar.gz cd57f0bfbc972266a3d6c6ccb2aabb53 19332 utils optional monero_0.18.5.3+~0+20260428-1.debian.tar.xz 2be67d52d22bb46b4c370b4e47ef74d7 9176 utils optional monero_0.18.5.3+~0+20260428-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmrCcNUQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFHRzDADExgPzmil+oTZUxgGmgxx1R0wQ5G1FUcg8 czRIDQm+AY7dtAXfgILbbSMWXE/v+85y1DKX9cpUjRV9r+D+ymyJm7zudsV6k6aJ VkooHZjKK6eS2pKh8eAMMwhC+uR/Qv/2lJvsw2O8vWbxR3dNYK6oF53GRTW5XVrg nf1UM9/0wgJ5U8AmJl75jK2YqY8huwjSj8S8pZGSHwgTgpUja7oD5rzKEibMDLPm 7RHAaVfZMYGgRNyteIxQd5NKCvZUy1V4w1kGwSo1qZP6W2zqyu8hYmS3xDFDH29A KbhFvbssJyI50i8dvy2Jn5hQRh69XRy6dDkewiiCzz/8/otKrV2EEGvRPtBV/dU5 C3gQEq1ny2LUP3KlY5f+PaYt5zrjP7/ZKQNds7nwe8asN+kz8irxsUbxHWap0kAz DtQb+Qvj1RO1Z2UPYE6MIq6AW7WeOemLtd6XdTv+LlRhlqKN9k8PhxkXT0r5qY05 JD3pWVZWJ4nYZERdueT0Y/ZHtmIbHzk= =gw2a -----END PGP SIGNATURE-----
I saw you mentioned canceling support for NTFS in another bug report; bad luck. FWIW, now I tried out your new version 0.18.5.3+~0+20260428-1. The crash remained: $ monerod --data-dir /my_Monero_dir/Monero --db-sync-mode safe --non-interactive --log-level 4 2026-10-08 01:06:55.789 I Monero 'Fluorine Fermi' (v0.18.5.3-unknown) 2026-10-08 01:06:55.789 I Moving from main() into the daemonize now. 2026-10-08 01:06:55.789 I Initializing cryptonote protocol... 2026-10-08 01:06:55.789 I Cryptonote protocol initialized OK 2026-10-08 01:06:55.791 T Blockchain::Blockchain 2026-10-08 01:06:55.791 I Initializing core... 2026-10-08 01:06:55.791 T BlockchainLMDB::BlockchainLMDB 2026-10-08 01:06:55.791 T BlockchainLMDB::get_db_name 2026-10-08 01:06:55.791 I Loading blockchain from folder /my_Monero_dir/lmdb ... 2026-10-08 01:06:55.791 D option: safe 2026-10-08 01:06:55.792 T BlockchainLMDB::open 2026-10-08 01:06:55.792 T BlockchainLMDB::need_resize 2026-10-08 01:06:55.792 D DB map size: 121995063296 2026-10-08 01:06:55.792 D Space used: 109599993856 2026-10-08 01:06:55.792 D Space remaining: 12395069440 2026-10-08 01:06:55.792 D Size threshold: 0 2026-10-08 01:06:55.792 D Percent used: 89.8397 Percent threshold: 90.0000 zsh: bus error monerod --data-dir /my_Monero_dir/Monero --db-sync-mode safe --non-interactive In the meantime, my e-mail provider said they adjusted the outgoing spam filter. I hope this technical e-mail gets through.
Typo correction in the report (due to anonymizing): $ monerod --data-dir /full_path_of_my_Monero_dir --db-sync-mode safe --non-interactive --log-level 4 2026-10-08 01:06:55.789 I Monero 'Fluorine Fermi' (v0.18.5.3-unknown) 2026-10-08 01:06:55.789 I Moving from main() into the daemonize now. 2026-10-08 01:06:55.789 I Initializing cryptonote protocol... 2026-10-08 01:06:55.789 I Cryptonote protocol initialized OK 2026-10-08 01:06:55.791 T Blockchain::Blockchain 2026-10-08 01:06:55.791 I Initializing core... 2026-10-08 01:06:55.791 T BlockchainLMDB::BlockchainLMDB 2026-10-08 01:06:55.791 T BlockchainLMDB::get_db_name 2026-10-08 01:06:55.791 I Loading blockchain from folder /full_path_of_my_Monero_dir/lmdb ... 2026-10-08 01:06:55.791 D option: safe 2026-10-08 01:06:55.792 T BlockchainLMDB::open 2026-10-08 01:06:55.792 T BlockchainLMDB::need_resize 2026-10-08 01:06:55.792 D DB map size: 121995063296 2026-10-08 01:06:55.792 D Space used: 109599993856 2026-10-08 01:06:55.792 D Space remaining: 12395069440 2026-10-08 01:06:55.792 D Size threshold: 0 2026-10-08 01:06:55.792 D Percent used: 89.8397 Percent threshold: 90.0000 zsh: bus error monerod --data-dir /full_path_of_my_Monero_dir --db-sync-mode safe --non-interactive