Description: Didn't know what happened, monerod crashed 1 hour later. Then a similar thing was printed again when I rebooted ~15 minutes ago (didn't check if they were completely identical, see gist revisions.)
Server RAM size: 512M - Extra swap: 1.5G (Shouldn't be a memory problem, there's plenty.)
Disk is about half full. (Shouldn't be a disk problem.)
Stacktrace: https://gist.github.com/UninterestinAcc/8ab0830791803e3fa3660d0f3399c1d5
Start options: "--limit-rate 160 --block-sync-size 1 --restricted-rpc --rpc-bind-ip <server ip address> --rpc-bind-port 18089 --confirm-external-bind" (yes an open node config from https://moneroworld.com/#nodes)
This doesn't seem to be the cause of the crash. Are you sure it is ?
Do you have a core file (or other similar way to get a stack trace on crash) ?
I dont think it caused the crash. Just saw it appear twice and thought about noting it here. And no I don't have a way to get a stacktrace on crash.
FWIW, --block-sync-size 1 is a silly setting, which will slow down sync by a fair amount. Why are you using this ?
That was a bad idea for progress tracking and saving my RAM. 🤷
I also receive this exception quite often (few times a day), mostly after BLOCK ADDED AS ALTERNATIVE ON HEIGHT.
2017-07-31 18:54:03.598 [P2P9] INFO global src/cryptonote_core/blockchain.cpp:1420 ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 1366460
id:
PoW:
difficulty: 16566208035
2017-07-31 19:01:10.751 [P2P9] INFO stacktrace src/common/stack_trace.cpp:119 Exception: boost::exception_detail::clone_impl
2017-07-31 19:01:10.751 [P2P9] INFO stacktrace src/common/stack_trace.cpp:120 Unwound call stack:
2017-07-31 19:01:10.788 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [1] monerod:__cxa_throw+0x84 [0x807a04]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [2] monerod:void boost::throw_exception
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [3] monerod:boost::asio::detail::do_throw_error(boost::system::error_code const&, char const)+0x1e [0x638b9e]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [4] monerod:epee::net_utils::boosted_tcp_server
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [5] monerod:nodetool::node_server
l::net_address const&, unsigned long)+0x397 [0x6f9937]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [6] monerod:nodetool::node_server
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [7] monerod:nodetool::node_server
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [8] monerod:epee::net_utils::boosted_tcp_server
base>)+0x1e [0x651a2e]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [9] monerod:boost::asio::detail::wait_handler
_base> > > > >::do_complete(boost::asio::detail::task_io_service, boost::asio::detail::task_io_service_operation, boost::system::error_code const&, unsigned long)+0xf7 [0x630787]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [10] monerod:boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock
etail::task_io_service_thread_info&, boost::system::error_code const&)+0x2fd [0x63372d]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [11] monerod:epee::net_utils::boosted_tcp_server
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [12] /usr/local/lib/libboost_thread.so.1.64.0+0x116d9 [0x7ffbe5b416d9]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [13] /lib64/libpthread.so.0+0x7dc5 [0x7ffbe61aadc5]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158 [14] /lib64/libc.so.6:clone+0x6d [0x7ffbe49ed76d]
2017-07-31 19:01:10.789 [P2P9] INFO stacktrace src/common/stack_trace.cpp:158
2017-07-31 20:12:59.085 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1099 SYNCHRONIZED OK
Server: CentOS 7.3 running in OpenVZ 3GB RAM
That should be fine, it's rying to connect to a new peer, and fails.
The crash might be fixed by https://github.com/monero-project/monero/pull/2492
I'll call it fixed, since the stack trace is not available anymore, I don't remember what it was, and my last comment says it might be fixed :)
Reopen if you still hit this and have more info.
+resolved