-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPi3B+ monerod errors #4507
Comments
You seem to be out of memory. Or something is trying to allocate a whole lot. Use more memory, add swap, etc. Do you have a stack trace for the crash ? |
That should be enough, and sync size should not really matter a whole lot here. But the db is probably corrupt indeed if you get a SIGSEGV there. You can type "bt" to get the stack trace at the crash point (you have just the tip here). |
Cool, I was close :P #0 0x0093ed64 in mdb_midl_xmerge () |
#19 0x007a833e in void boost::asio::detail::strand_service::dispatch<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_context::strand, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_tcryptonote::cryptonote_connection_context > >, boost::system::error_code const&, unsigned int>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_tcryptonote::cryptonote_connection_context > > > >, boost::arg<1> ()(), boost::arg<2> ()()> >, boost::asio::detail::is_continuation_if_running>, boost::system::error_code, unsigned int>, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::as---Type to continue, or q to quit--- |
rm data.mdb and start again with 2048MB RAM instead of 1000MB? |
I now think the memory's ok, the DB being shot probably causes it to request silly amounts based on bad data. Maybe hyc can help more here. |
Hi guys, FYI, I cross posted this issue to the r/pinode subreddit to ask for help there w.r.t. what could also be Pi setup related errors |
Hi guys I failed again: 2018-10-07 19:50:20.452 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1171 [185.152.64.176:18080 OUT] Synced 96116/1677909 |
update when I resumed monerod it went past the block. |
failed again 2018-10-07 20:09:01.940 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1171 [148.251.89.12:18080 OUT] Synced 96816/1677923 |
2018-10-07 20:17:07.080 76f12210 INFO global src/cryptonote_core/cryptonote_core.cpp:427 Loading blockchain from folder /home/pi/.bitmonero/lmdb ... |
gdb ./bin/monero-v0.12.3.0/monerod Thread 1 "monerod" received signal SIGBUS, Bus error. |
stuff it. restarting from zero for the 4th and last time... |
(gdb) bt |
running for the 4th time from block 0 with: ./bin/monero-v0.12.3.0/monerod --rpc-bind-ip=192.168.1.10 --rpc-bind-port=4008 --confirm-external-bind --max-concurrency 1 --block-sync-size 20 |
If you see the problem again, you should try the |
Next error 2018-10-08 00:15:24.542 [P2P8] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1171 [107.10.255.62:18080 OUT] Synced 92332/1678034 |
pi@xmrpi:~ $ dmesg |
Maybe the RPi is too weak to power the 2TB ext hdd? |
I have an output of 5V 3A Power supply |
Should I consider getting a SSD HD instead? They are probably more power efficient |
Ok, so I ordered a powered USB hub after checking out some Raspberry Pi forums. Lets see if some more external power solves the reliability issue of the HDD. |
So I think we cracked this one on reddit.. Still syncing stable now.. |
Very good find :) |
Kudos to reddit user u/shermand100 for amazing perseverance and patience with an unusual symptoms and to @glv2 for the dmesg suggestion. |
Can you give a command that adds that setting to the boot file (ie, echo "max_usb_current=1" >> /etc/someconfig") which I can add to the README ? |
I never even knew that was possible. Can't imagine it's good for the longevity of the Pi. Simple low-tech solution is just to get a USB Y-cable, and plug an external USB power supply in to give the drive enough juice. |
@moneromooo-monero
and then I added the setting to the config file:
@hyc we discussed the Y splitter cable and powered usb hub alternatives as well on r/pinode The pi is now running stable for a day already at temp=68.8'C which is below the max threshold of 80'C even without an extra cooling fan which I think is badass :P |
Thanks, it's now in #4553 |
Relying on the Pi to supply enough power by itself is a mistake. If there's extra CPU or network activity, it won't have enough juice for your HDD. |
Since my last post I received the powered usb hub. I will plug that into the Pi for at least the period of catching up the initial sync. It can only help carry the load indeed. |
Hi guys
After having deleted and re-started downloading the blockchain a week ago I started seeing errors again:
I have been following this guide for the setup.
I have used this refined command to launch monerod with more manageable block-sync-size:
It was running very stable up to this point. I have a 2Tb external hdd connected to the pi. Is the mapping correc?
produces:
Is the database corrupted again?
The text was updated successfully, but these errors were encountered: