-
Notifications
You must be signed in to change notification settings - Fork 92
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
Daemon wont completely shutdown #569
Comments
Can this behavior be replicated via the gitian built binary? |
not sure, i can try |
After some digging I found 2 PRs on bitcoin upstream that I think if we ported into navcoin would do some good: Basically those PRs refactor the net.cpp and net.h code to be more efficient and from I've read, they also eliminate the thread issue you reported in this PR But the amount of code changes require is alot. Not sure if it's worth it for this release. Basically the PRs I mention also come with some performance benefits, aparently they speed up the network sync by a large amount, refer to this PR from dash about more details on the performance impacts: dashpay/dash#1586 |
Basically this issue seems to have been caused by a peer that was not yet properly handled by |
Since I could not replicate this on my nodes (I could shut them down gracefully) this must only happen under certain conditions, IE only when a peer is trying to connect and shutdown is called on the node via |
Closing for now as I think this may have been an isolated issue on the test system |
Version: Running commit 2b13cc9 of the 4.7.0 RC (#545) built locally using the depends folder.
OS: Mac OSX 10.14.5
Steps;
./src/navcoind &
./src/navcoin-cli stop
Result;
error: couldn't connect to server
../src/navcoind &
results inError: Cannot obtain a lock on data directory /Users/xxx/Library/Application Support/NavCoin4. NavCoin Core is probably already running.
The only way to stop the daemon entirely is to force kill the process id or reboot your machine.
Expected result;
navcoind would fully shut down and exit when using the cli
stop
command.The text was updated successfully, but these errors were encountered: