You are viewing a single comment's thread from:

RE: Comprehensive and Updated Guide to Mining Steem (For Both Windows and Linux Users) - One-stop-shop for all your information needs!

in #steemit8 years ago

I got this working relatively problem free, though I had to hash out the last seed note from the Config.ini file, as shown below:

seed-node = 212.47.249.84:40696
seed-node = 52.4.250.181:39705
seed-node = 81.89.101.133:2001
seed-node = 192.99.4.226:2001
seed-node = 46.252.27.1:1337
#seed-node = seed.steemd.com:34191

I was getting multiple errors stacking up until it exited starting with this:

3110051ms th_a application.cpp:102 reset_p2p_node ] Adding seed node 46.252.27.1:1337
3110111ms th_a application.cpp:102 reset_p2p_node ] Adding seed node 162.213.199.171:34191
3110112ms th_a application.cpp:102 reset_p2p_node ] Adding seed node 162.213.199.171:34191
3110123ms th_a application.cpp:352 startup ] 90003 already_connected_to_requested_peer: already connected to requested peer
already connected to requested endpoint 162.213.199.171:34191
{"endpoint":"162.213.199.171:34191"}
p2p node.cpp:4565 connect_to_endpoint


Any ideas as to why this was the case? Also hashing that out is liable to cause any problems?
I also started out with a decent hash rate of about 35000/hps running off 16 cores, for some reason Ubuntu VM wouldn't allow me to configure all 24 in settings! Why?

But anyway, after around 20/30minues my hash rate gradually started dropping off, it is now only running at about 40/hps and drops with every new set of transactions on each new block. My cpu is also now doing almost nothing, it was running upto 70%, now it is idling at around 4% use.. What is the reason for such behaviour?

Thanks

Sort:  

The loss of hash power could possibly have been due to lack of space on the VM, though it did appear to have enough space, a low space warning was given when exiting. I increased the VM size to 30GB, up from 20GB. Have re-run mining of Steemit, and has maintained a consistent 35000ish/hps for over 2 hours.

Though is there a way to stop the mining and then restart it without just closing the Terminal window? As this always causes a replaying of the Blockchain when I restart it, which is a pretty slow process.

you can press ctrl-c to stop the miner. you can then just run ./steemd again to restart it. As for the space, i noticed 30GB is better for a VM arrangement. At 20GB I also run out of space

did you mean "./steemd"? ... "./steemit" isn't recognised, and to my knowledge there isn't anything named steemit.

./steemd doesn't work any better, as it just loads up and then replays the blockchain, percent by percent and lists the hard-forks, which takes 20mins+, and that was after using the Ctrl-C to shutdown mining cleanly

corrected it. Yup. It can take a little bit of time to replay the blockchain, but should start back up