Mining Steem on OS X
Well I am somewhat bemused, I have gone through a strange concoction of install instructions that weaved through 3 different install instructions, starting on OS X gong into Ubuntu and finishing on Windows configuration of Config.ini. As well other sites to try and understand why it had failed to work. Finally a did a cmake from within a subfolder that was never explained or instructed to do, but that caused Steemd to finally install.
I loaded using "screen -r steemd" in terminal before changing config.ini info., and got:
STARTING STEEM NETWORK
initminer public key: STM8G****(etc)
chain id: 0000000000000000000000000000000000000000000000000000000000000000
2587419ms th_a main.cpp:124 main ] Writing new config file at /Users/****/steem/programs/steemd/witness_node_data_dir/config.ini
2587420ms th_a witness.cpp:98 plugin_initialize ] _witnesses: []
2587449ms th_a database.cpp:118 reindex ] !no last block
2587450ms th_a database.cpp:119 reindex ] last_block:
2587450ms th_a thread.cpp:95 thread ] name:ntp tid:4497543168
2587452ms th_a thread.cpp:95 thread ] name:p2p tid:4502814720
2587497ms th_a witness.cpp:186 plugin_startup ] No witnesses configured! Please add witness names and private keys to configuration.
2587497ms th_a witness.cpp:194 plugin_startup ] No miners configured! Please add miner names and private keys to configuration.
2595162ms ntp ntp.cpp:166 read_loop ] received stale ntp reply requested at 2016-07-29T21:43:08, send a new time request
Now after this I opened the config.ini file in Text Edit and then Unitron and modified the details as instructed as per the windows configuration instructions that are suppose to be the same for all platforms. I reloaded Terminal, and it loads up the same as before with all the above details supposedly only as history? And it then adds an extra line after a small period of time:
3360293ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -940771 us
And that's it! Now is this doing something or not? It appears to be doing nothing at all. Do I need to force it to refresh and read the updated config file or something? Or is there just something wrong with the setup?? Really it tells me nothing and the computer is pretty much idle, so no mining or anything is happening.
There's all these mixed instructions on installing but nothing I can find on what happens or should happen once installed.
Thanks
I'm having this exact problem on my raspberry pi. I reported the problem over in steemit.chat#mining. Hopefully, someone has some insight.
Interestingly, I've also done the installation on DigitalOceans, this problem doesn't occur.
Main problem I set-out above was caused by starting mining from the wrong directory, so system wasn't finding my modified config.ini file. Though still had constant issues with running on OS X, my solution is as follows: (not sure if this will help much on a Raspberry pi)
I found easiest solution was to run it on Ubuntu on a virtual machine using VMware Fusion. Only had one issue to diagnose, which I managed to workout myself. One minor downside that probably doesn't affect anyone with 16 cores/threads or less, is that I couldn't run a full 24 cores/threads on my machine. I followed these comprehensive instructions to do this:
https://steemit.com/steemit/@cloh76/comprehensive-guide-to-mining-steem-for-both-windows-and-linux-users#@timeet/re-cloh76-comprehensive-guide-to-mining-steem-for-both-windows-and-linux-users-20160807t220847671z
The one problem I experienced was solved by hashing(#) out the last seed-note from the "config.ini" file as show 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'm fairly certain the problem I'm having is due to the tiny RAM on the pi (
1GB). Even setting a huge swap of8GBdidn't help. I'm finding that2GBis the absolute minimum.You've probably seen this, and not sure how it would work with a pi: If memory is to low to compile run:
cmake -DENABLE_CONTENT_PATCHING=OFF -DLOW_MEMORY_NODE=ON CMakeLists.txt
I Took this from here: https://steemit.com/steemhelp/@proctologic/easy-install-steemd-in-ubuntu
No, it's doing nothing. Try downloading the blockchain from http://steemitup.eu/ , paste it to the right folder and try again.
Thanks, well I did that.. reloaded and something different has happened as now the cursor is now unresponsive within the Steemd terminal window. Previously I could type anything and the mouse movements would be logged as code/^[[A^[[B^ etc. I will leave it running for an hour or so, wondered if it is updating the Blockchain with any new Blocks since it was last uploaded to: http://steemitup.eu/
?
Terminal is still active, nothing appears to have crashed or hungup.
Hmm, never really seen that. Maybe you can get into steemit.chat and ask - might be some experienced miners there.
Nice @timeet
Shot you an Upvote :)
I got this working on Ubuntu under a virtual machine in the end, but I had to hash out the last seed-note as show below in order get passed similar errors:
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
So tried this on OS X, and managed to get it to mine, but it has since started acting up again and started chucking out error messages and terminating. The Virtual Machine running Ubuntu is almost good enough, but it is limited to 16 cores/threads for some reason, when I have 24 available on my machine.
last output is:
1464014ms th_a database.cpp:3497 apply_hardfork ] HARDFORK 9
1478307ms th_a database.cpp:3519 apply_hardfork ] HARDFORK 10
1491819ms th_a database.cpp:3525 apply_hardfork ] HARDFORK 11
93.403% 3300000 of 3533077
96.2334% 3400000 of 3533077
99.0638% 3500000 of 3533077
1646798ms th_a thread.cpp:95 thread ] name:ntp tid:4603686912
1646798ms th_a thread.cpp:95 thread ] name:p2p tid:4825554944
1648138ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to -974605 us
Main problem I set-out above was caused by starting mining from the wrong directory, so system wasn't finding my modified config.ini file. Though still had constant issues with running on OS X, I found easiest solution was to run it on Ubuntu on a virtual machine using VMware Fusion. Only had one issue to diagnose, which I managed to workout myself.
One downside that probably doesn't affect anyone with 16 cores/threads or less, is that I couldn't run a full 24 cores/threads on my machine. I followed these comprehensive instructions to do this:
https://steemit.com/steemit/@cloh76/comprehensive-guide-to-mining-steem-for-both-windows-and-linux-users#@timeet/re-cloh76-comprehensive-guide-to-mining-steem-for-both-windows-and-linux-users-20160807t220847671z
The one problem I experienced (as I stated on an earlier post) was solved by hashing(#) out the last seed-note from the "config.ini" file as show 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
Upvoted
Upvoted
Nice @timeet
Shot you an Upvote :)