-
Notifications
You must be signed in to change notification settings - Fork 28
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
Segmentation fault #6
Comments
Update: nodeos --version - 1.5.x // Segmentation fault |
1.5.1 and the current
|
Found the problem: when you specify the plugin in command line, it overrides the standard plugin initialization sequence. As ZMQ plugin depends on chain plugin, the chain plugin has to be loaded first. This works:
|
Thank you. Can reproduce it. Additional note: the chain_plugin must be defined BEFORE the zmq_plugin on the command line. |
Hi,
I wanted to use the zmq plugin for some analytics but got a segmentation fault.
Environment:
GDB Output:
_gdb --args ./nodeos --disable-replay-opts --hard-replay-blockchain --data-dir /mnt/hdd1/crypto/eos.mainnet/data --plugin eosio::zmq_plugin
..
..
(gdb) r
Starting program: /home/jj/projects/lcc/analytics/eos/modules/nodeos/bin/nodeos --disable-replay-opts --replay-blockchain --hard-replay-blockchain --data-dir /mnt/hdd1/crypto/eos.mainnet/data --plugin eosio::zmq_plugin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff50bd700 (LWP 3168)]
[New Thread 0x7ffff48bc700 (LWP 3169)]
info 2018-12-15T17:25:34.235 thread-0 zmq_plugin.cpp:648 plugin_initialize ] Binding to ZMQ PUSH socket tcp://127.0.0.1:5556
Thread 1 "nodeos" received signal SIGSEGV, Segmentation fault.
0x0000000000fd4f66 in eosio::zmq_plugin::plugin_initialize(boost::program_options::variables_map const&) ()_
Best Regards,
Jiri / EOS Germany
nodeos_strace.log
The text was updated successfully, but these errors were encountered: