Skip to content
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

CLI 'nano_node --wallet_create' or 'nano_node --wallet_list' commands don't work #2824

Closed
aglkm opened this issue Jun 19, 2020 · 4 comments
Closed
Assignees
Labels
Milestone

Comments

@aglkm
Copy link

aglkm commented Jun 19, 2020

Run ./nano_node --wallet_create command and you will get the following:
Assertion (!flags.read_only) failed
nano::node::node(boost::asio::io_context&, const boost::filesystem::path&, nano::alarm&, const nano::node_config&, nano::work_pool&, nano::node_flags, unsigned int)
/workspace/nano/node/node.cpp:368

0# 0x00000000008BC363 in ./nano_node
1# 0x00000000008BD604 in ./nano_node
2# 0x000000000063531A in ./nano_node
3# 0x00000000006372E8 in ./nano_node
4# 0x000000000051F5AF in ./nano_node
5# 0x0000000000523B3F in ./nano_node
6# 0x0000000000480BB1 in ./nano_node
7# __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
8# 0x00000000004C5339 in ./nano_node

Aborted

@wezrule
Copy link
Contributor

wezrule commented Jun 19, 2020

It seems this is an issue if the node hasn't been started yet (not properly initialised data.ldb file). Could you run with the --daemon flag first, wait for the command line output (with network etc) and try the command again please.

@aglkm
Copy link
Author

aglkm commented Jun 19, 2020

OK, I've tested a bit.
If data.ldb file is located inside default home(~/Nano) directory there is no such issue.
However, in my scenario, I have started nano_node with custom directory(--data_path option), so in this case nano_node --wallet_create doesn't work.
I see that 'nano_node --wallet_create --data_path=...' works.
It would be nice to have a message saying something like "node requires data.ldb file for the operation but can't find it" in such case.

@wezrule
Copy link
Contributor

wezrule commented Jun 19, 2020

Yeh this is a bug, shouldn't crash for sure. Thanks for the report and testing.

@wezrule
Copy link
Contributor

wezrule commented Jul 28, 2020

#2862 will make it no longer crash and output appropriate message.

@zhyatt zhyatt closed this as completed Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants