RE: -EZSTEEM SUITE 1.0- : The EZ way to setup your STEEM Miner/Node in a Linux VM [Windows Compatible]
Thanks for this! It's very easy to configure your mining accounts since the code does it for you.
I'm trying to sync up the blockchain and it was going well until this:
g Blockchain --- Got block: #3430000 time: 2016-07-22T23:46:27
173992ms th_a application.cpp:419 handle_block ] Syncing Blockchain --- Got block: #3440000 time: 2016-07-23T08:10:48
188611ms th_a application.cpp:419 handle_block ] Syncing Blockchain --- Got block: #3450000 time: 2016-07-23T16:35:48
213065ms th_a application.cpp:419 handle_block ] Syncing Blockchain --- Got block: #3460000 time: 2016-07-24T01:05:09
461285ms p2p tcp_socket.cpp:162 bind ] Exception binding outgoing connection to desired local endpoint: bind: Bad file descriptor
Any idea what that is all about? Thanks for looking!
EDIT:
I shut down and then restarted my VM. Chose 6, it checked the blockchain, then It BEGAN TO MINE! Yayyyy! Thanks! Only about 5400 hash per second, so we'll see if I ever get anything from this, but at least it is Working!
EDIT 2:
I set up ezsteem on a Ubantu VM on Microsoft Azure and got it to mine, thanks!
Question -- I have some credits on Azure, that's one reason I set this up there instead of my own machine. I don't want my own machine running 24/7. But when I closed putty on my machine, which is the ssh way I was talking to the Azure VM, I noticed on my Azure dashboard that the CPU usage went to 0 for the VM that is doing the mining. SO, is there a way to have the VM keep mining without me having to have my machine running putty 24/7?
Maybe the nohup command? "Nohup enables a program to continue running after the user that started it logs out." If @omotherhen could add another choice to the menu that allowed the user to log out, that would really help! I also see there are ways to orphan or disown a job, and that might be the way to go too.
Nohup mentioned here: http://www.minecraftforum.net/forums/support/server-support/server-administration/1897017-logging-out-of-putty-shuts-down-server
Orphan or disown a job mentioned here: http://stackoverflow.com/questions/6012557/does-quitting-putty-close-the-running-command
@kenny-crane
If you used the default installation path of /var/EZSTEEM, try this command:
screen -dmSL myTest /var/EZSTEEM/steem/programs/steemd/steemd
the -dmSL means : detach with a new screen, allow a session name (myTest in this case, you can use whatever) and log stderr and stdout at ~/screenlog.0
You should now be able to exit your PuTTY session leaving it running in the background.
When you log back in again, use this command to bring it to the foreground.
screen -x myTest
You can also check the log using your favorite text editor or just watch it with tail
tail -f ~screenlog.0