problem again with bitcoincore 10.1

[bobby88]

Hello everybody ,

I have problems when i try to run bitcoind - daemon from my computer(Os windows 7 64 bit , 6GB RAM ,Intel iCore3 ) the cmd cursor keeps flashing  and when i did  Ctrl+c  it say

C:\Program Files\Bitcoin\daemon>bitcoind -daemon
Assertion failed!

Program: C:\Program Files\Bitcoin\daemon\bitcoind.exe
File: allocators.h, Line 43

Expression: this->GetLockedPageCount() == 0

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

C:\Program Files\Bitcoin\daemon>bitcoind -daemon

What did I missed ? please help

Regards

[cr1776]

Are you trying to stop Bitcoin Core with a control-c?  You should use the quit command to stop the program.

Maybe I am not clear on exactly what you are asking.

[Borisz]

Yes, I am also not entirely clear on what you were trying to do.

Did you simply want to quit after running (successfully) for X hours or you think that it is hung and want to kill the process?

[bobby88]

I tried to run daemon from its folder with cmd , so i thought i will run daemon and make it running on server node as https://en.bitcoin.it/wiki/Bitcoind said , and then there s come the problem that i wrote before , the question is is it save  for me just run the bitcoin qt  after that problem , is there any corrupted or unstable running , or what should ido , sorry for the noob questions


regards

[achow101_alt]

The behavior you see is actually what should happen. If you open task manager after you run the command, you should see bitcoind.exe in it. You can then open another command prompt and give commands to that instance of bitcoind you ran in the other command prompt.

The output you see when you hit Ctrl+C is what should happen since Ctrl+C is an interrupt and will cause the program to terminate.

Also, I don't think that -daemon is a valid option for bitcoind.

[cr1776]

I tried to run daemon from its folder with cmd , so i thought i will run daemon and make it running on server node as https://en.bitcoin.it/wiki/Bitcoind said , and then there s come the problem that i wrote before , the question is is it save  for me just run the bitcoin qt  after that problem , is there any corrupted or unstable running , or what should ido , sorry for the noob questions


regards

Yes, but why hit control-c?  That should interrupt it like you saw. 

If you run it again, it should notify you if there is a problem.

[shorena]

I tried to run daemon from its folder with cmd , so i thought i will run daemon and make it running on server node as https://en.bitcoin.it/wiki/Bitcoind said , and then there s come the problem that i wrote before , the question is is it save  for me just run the bitcoin qt  after that problem , is there any corrupted or unstable running , or what should ido , sorry for the noob questions


regards

Yes, but why hit control-c?  That should interrupt it like you saw.  

If you run it again, it should notify you if there is a problem.

I think OP is looking for a way to start the daemon and return to the prompt while the daemon keeps running in the background.

@OP try the following if the above is true.

Code:

start /b bitcoind -daemon

[cr1776]

I tried to run daemon from its folder with cmd , so i thought i will run daemon and make it running on server node as https://en.bitcoin.it/wiki/Bitcoind said , and then there s come the problem that i wrote before , the question is is it save  for me just run the bitcoin qt  after that problem , is there any corrupted or unstable running , or what should ido , sorry for the noob questions


regards

Yes, but why hit control-c?  That should interrupt it like you saw.  

If you run it again, it should notify you if there is a problem.

I think OP is looking for a way to start the daemon and return to the prompt while the daemon keeps running in the background.

@OP try the following if the above is true.

Code:

start /b bitcoind -daemon

Ah.  If so, something as suggested above should work.  On Linux Or OS x one could use the screen command or something similar. 

And you should be able to run it after that error - it should warn you of it finds a problem.

[bobby88]

yeah , its not easy to run *nix stuff  to windows environment