-
Notifications
You must be signed in to change notification settings - Fork 3.8k
nodeos crash in ubuntu 16.04 after running several days as block producer #2403
Comments
It happen again today dmesg: tail -f stderr.txt |
After that starting nodeos gets following errors: 3028278ms thread-0 block_log.cpp:120 open ] Log is nonempty |
I keep getting the same errors: Any idea what exactly it is? |
I'm seeing a similar error when stopping and restating the node, happens when I get an exit code of 137 while stopping
|
I caught a core dump in a crash while syncing blocks. (lldb) bt all (lldb) * thread #1, name = 'nodeos', stop reason = signal SIGSEGV
|
This appears to be two different issues. Startup after a crash or ungraceful shutdown nearly always fails due to corruption of the boost shared memory cache of the in-memory database. For normal shutdown, never kill with
The core dump is a different problem. That looks like a corrupted network packet, specifically a |
Update: I fixed my issue with: I'm using Docker on Win10. The first time I ran Dawn 4.2, I ran: docker run --name nodeos -p 8888:8888 -p 9876:9876 -t eosio/eos nodeosd.sh arg1 arg2 After that worked, I did a docker system prune -a and tried version 1.0.1. It fails with: 2094856ms thread-0 net_plugin.cpp:2920 plugin_startup ] starting listener, max clients is 25 2094856ms thread-0 producer_plugin.cpp:577 plugin_startup ] producer plugin: plugin_startup() begin 2094856ms thread-0 producer_plugin.cpp:592 plugin_startup ] Launching block production for 1 producers at 2018-06-02T22:34:54.856. 2094856ms thread-0 producer_plugin.cpp:604 plugin_startup ] producer plugin: plugin_startup() end It doesn't show the blocks every half second now. I pruned and retried a few times and even reverted back to Dawn 4.2, but no luck yet. Do I need to reset something on my network or firewall in addition to docker system prune -a ? This is my first time trying Docker or nodeos. Also, assuming the mainnet arrives, how do I connect to it from my own Docker nodeos? |
Build : dawn-v3.0.0
Environment : Ubuntu 16.04.3 LTS
Linux kernal: Linux i-hmidbtjm 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Issue: nodeos crash after running several days as block producer.
More information:
[808583.358958] traps: nodeos[25675] general protection ip:7f9b0aedc478 sp:7ffe6b2f09e0 error:0 in libc-2.23.so[7f9b0ae5e000+1c0000]
[852538.838959] nodeos[8772]: segfault at 7fb4cd719010 ip 00000000006297f5 sp 00007ffcf6b4d860 error 6 in nodeos[400000+20b1000]
[912444.313550] ip_tables: (C) 2000-2006 Netfilter Core Team
[1352932.903115] nodeos[8301]: segfault at 0 ip 0000000000629fb5 sp 00007ffc08447960 error 6 in nodeos[400000+20b1000]
last stderr.txt before crash:
push block #1321906 from bat 2018-04-14T21:05:28.000 00142bb2d89c58997771c116a0f678891e2594193ff67c620dc285f2c4bdd076 lib: 1310190 success
push block #1321907 from bat 2018-04-14T21:05:28.500 00142bb348d94b0cf0c8775891398c3193fd30285227a3043c400f98b4ca01e0 lib: 1310190 success
350671ms thread-0 fork_database.cpp:78 _push_block ] Number of missed blocks: 12
350673ms thread-0 chain_controller.cpp:1406 validate_block_heade ] head_block_time 2018-04-14T21:05:28.500, next_block 2018-04-14T21:05:35.000, block_interval 500
350673ms thread-0 chain_controller.cpp:1408 validate_block_heade ] Did not produce block within block_interval 500ms, took 6500ms)
push block #1321908 from dragonfly 2018-04-14T21:05:35.000 00142bb449668c7fda66f6dda1f34754ac168ff6961f8db55addc3ea818956cc lib: 1310190 success
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350674ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350675ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350675ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350675ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350675ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
350675ms thread-0 net_plugin.cpp:1385 recv_notice ] sync_manager got catch up block notice
after crash, restarting the nodeos can turn the node back to normal.
The text was updated successfully, but these errors were encountered: