Skip to content
This repository was archived by the owner on Aug 2, 2022. It is now read-only.

nodeos crash at websocketpp::exception: invalid state #6971

Closed
taokayan opened this issue Mar 20, 2019 · 2 comments
Closed

nodeos crash at websocketpp::exception: invalid state #6971

taokayan opened this issue Mar 20, 2019 · 2 comments

Comments

@taokayan
Copy link
Contributor

taokayan commented Mar 20, 2019

in branch 6429-protocol-upgrade-activation-mechanism (commit 568476a), related to #6736

I can reproduce similar crash using the init script attached, by running the script for a 2nd time:

console output:

libc++abi.dylib: terminating with uncaught exception of type websocketpp::exception: invalid state
./clean_start.sh: line 6:  2464 Abort trap: 6           (core dumped) ./programs/nodeos/nodeos --data-dir=/Users/jiaendu/workspaces/eos/build/data-dir --config-dir=/Users/jiaendu/workspaces/eos/build/data-dir --http-validate-host=false --delete-all-blocks --verbose-http-errors --filter-on=* --filter-out=eosio:onblock:eosio --p2p-max-nodes-per-host=100 $*

lldb backtrace:

* thread #1, stop reason = signal SIGSTOP
  * frame #0: 0x00007fff7c8f0bea libsystem_kernel.dylib`kevent + 10
    frame #1: 0x0000000102986132 nodeos`boost::asio::detail::kqueue_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) + 290
    frame #2: 0x0000000102985b14 nodeos`boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) + 340
    frame #3: 0x000000010279cee5 nodeos`boost::asio::detail::scheduler::run_one(boost::system::error_code&) + 181
    frame #4: 0x000000010279ac39 nodeos`appbase::application::exec() + 121
    frame #5: 0x000000010278c515 nodeos`main + 3397
    frame #6: 0x00007fff7c79f015 libdyld.dylib`start + 1
@taokayan
Copy link
Contributor Author

attached init script file.
init_sh.txt

@taokayan
Copy link
Contributor Author

close this as already fixed in #6974 & #6975

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant