So there i was, all pleased with myself for updating well ahead of time for 0.5.0... I log into my miners this morning and... all broken. So i restart them and it just sits at this. Any ideas people? 2474353ms th_a witness.cpp:419 on_applied_block ] hash rate: 1 hps target: 27 queue: 95 estimated time to produce: 2236962 minutes
author | b0y2k |
---|---|
permlink | steem-0 |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:02:24 |
last_update | 2016-06-01 09:02:24 |
depth | 0 |
children | 26 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 6.884 HBD |
curator_payout_value | 6.884 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 359 |
author_reputation | 576,806,030,298,882 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,359 |
net_rshares | 11,280,879,196,574 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
justin | 0 | 753,733,241,555 | 100% | ||
silver | 0 | 2,427,987,189,253 | 100% | ||
silversteem | 0 | 2,315,229,098,979 | 100% | ||
turtle | 0 | 5,814,192,819 | 100% | ||
nextgencrypto | 0 | 3,855,384,127,911 | 100% | ||
rossco99 | 0 | 1,860,208,578,569 | 100% | ||
steemservices | 0 | 36,104,066,168 | 100% | ||
aizensou | 0 | 5,299,570,000 | 100% | ||
b0y2k | 0 | 5,281,488,600 | 100% | ||
jackie | 0 | 113,643,300 | 100% | ||
markopaasila | 0 | 8,986,630,724 | 100% | ||
timifey2015 | 0 | 653,350,749 | 100% | ||
jerome-colley | 0 | 280,819,477 | 100% | ||
jonde | 0 | 430,874,199 | 100% | ||
xav | 0 | 4,239,508,583 | 100% | ||
viet-ngo | 0 | 272,931,890 | 100% | ||
dmitry | 0 | 352,314,613 | 100% | ||
sulastri-wahid | 0 | 380,519,602 | 100% | ||
ladeblah | 0 | 127,049,583 | 100% | ||
capocapital | 0 | 0 | 100% |
It probably means your miner has mined out a "ticket", then waiting for producing a block to claim the reward. To save your hashing power, setup multiple miners in one process. By the way, I'm curious why this post got a lot of up-votes. Bots?
author | abit |
---|---|
permlink | re-b0y2k-steem-0-20160601t091415771z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:14:15 |
last_update | 2016-06-01 09:14:15 |
depth | 1 |
children | 6 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.238 HBD |
curator_payout_value | 0.238 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 244 |
author_reputation | 141,171,499,037,785 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,366 |
net_rshares | 1,158,892,905,804 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
bhuz | 0 | 851,588,660,577 | 100% | ||
ash | 0 | 8,360,794,697 | 100% | ||
noaommerrr | 0 | 298,401,708,384 | 100% | ||
ladeblah | 0 | 127,049,583 | 100% | ||
denverliu | 0 | 414,692,563 | 100% |
something similar has happend every update so far.. It was mining very nicely before the fork even after updating to 0.5. Yet after the fork it just stopped producing at all. I am rebuilding a fresh install now and just replaying the blockchain. Just strange this always happens every update, each time the only fix was a complete fresh install.
author | b0y2k |
---|---|
permlink | re-abit-re-b0y2k-steem-0-20160601t092030646z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:21:30 |
last_update | 2016-06-01 09:21:30 |
depth | 2 |
children | 5 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 347 |
author_reputation | 576,806,030,298,882 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,371 |
net_rshares | 127,049,583 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
ladeblah | 0 | 127,049,583 | 100% |
You have checked the queue? If yes, or you already have multiple miners setup, it would be strange. Both of my testing miners are running fine. ``` 1536117ms th_a witness.cpp:419 on_applied_block ] hash rate: 5636 hps target: 28 queue: 96 estimated time to produce: 793 minutes ``` ``` 1599491ms th_a witness.cpp:419 on_applied_block ] hash rate: 6001 hps target: 27 queue: 95 estimated time to produce: 372 minutes ```
author | abit |
---|---|
permlink | re-b0y2k-re-abit-re-b0y2k-steem-0-20160601t093009119z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:30:09 |
last_update | 2016-06-01 09:30:09 |
depth | 3 |
children | 4 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 470 |
author_reputation | 141,171,499,037,785 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,375 |
net_rshares | 0 |
My miner also got stuck with "1 hps" logs several times. And it definitely wasn't because my witnesses were all in the queue. Didn't happen again since the hardfork date.
author | cyrano.witness |
---|---|
permlink | re-b0y2k-steem-0-20160602t184557181z |
category | steem |
json_metadata | {"tags":["steem"]} |
created | 2016-06-02 18:45:57 |
last_update | 2016-06-02 18:45:57 |
depth | 1 |
children | 0 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 170 |
author_reputation | 4,484,166,969,124 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 21,888 |
net_rshares | 0 |
How did you compile steem? I just get stuck at 67% every time.
author | markopaasila |
---|---|
permlink | re-b0y2k-steem-0-20160601t092336977z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:23:36 |
last_update | 2016-06-01 09:23:36 |
depth | 1 |
children | 12 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 62 |
author_reputation | 32,771,884,740,822 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,372 |
net_rshares | 0 |
Can you post the error messages here? Probably you need to do this before compiling: ``` git submodule update --init --recursive ```
author | abit |
---|---|
permlink | re-markopaasila-re-b0y2k-steem-0-20160601t093146120z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:31:45 |
last_update | 2016-06-01 09:31:45 |
depth | 2 |
children | 6 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 132 |
author_reputation | 141,171,499,037,785 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,376 |
net_rshares | 9,404,613,548 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
markopaasila | 0 | 9,404,613,548 | 100% |
I did that. I'm using boost 1.60.0, which is default on Arch. Here's the output: ``` [ 67%] Building CXX object libraries/chain/CMakeFiles/steemit_chain.dir/database.cpp.o /home/marko/steem/steem/libraries/chain/database.cpp: In member function ‘steemit::chain::signed_block steemit::chain::database::_generate_block(fc::time_point_sec, const string&, const fc::ecc::private_key&)’: /home/marko/steem/steem/libraries/chain/database.cpp:719:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if( new_total_size >= maximum_block_size ) ^ /home/marko/steem/steem/libraries/chain/database.cpp: In member function ‘void steemit::chain::database::set_hardfork(uint32_t, bool)’: /home/marko/steem/steem/libraries/chain/database.cpp:2991:48: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] for( int i = hardforks.last_hardfork + 1; i <= hardfork && i <= STEEMIT_NUM_HARDFORKS; i++ ) ^ In file included from /home/marko/steem/steem/libraries/db/include/graphene/db/object_id.hpp:25:0, from /home/marko/steem/steem/libraries/chain/include/steemit/chain/protocol/types.hpp:4, from /home/marko/steem/steem/libraries/chain/include/steemit/chain/protocol/base.hpp:3, from /home/marko/steem/steem/libraries/chain/include/steemit/chain/protocol/steem_operations.hpp:2, from /home/marko/steem/steem/libraries/chain/database.cpp:2: /home/marko/steem/steem/libraries/chain/database.cpp: In lambda function: /home/marko/steem/steem/libraries/chain/database.cpp:3058:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] FC_ASSERT( hardfork == hfp.last_hardfork + 1, "Hardfork being applied out of order", ("hardfork",hardfork)("hfp.last_hardfork",hfp.last_hardfork) ); ^ /home/marko/steem/steem/libraries/fc/include/fc/exception/exception.hpp:325:30: note: in definition of macro ‘FC_EXPAND_MACRO’ #define FC_EXPAND_MACRO( x ) x ^ /home/marko/steem/steem/libraries/fc/include/fc/exception/exception.hpp:332:11: note: in expansion of macro ‘UNLIKELY’ if( UNLIKELY(!(TEST)) ) \ ^ /home/marko/steem/steem/libraries/chain/database.cpp:3058:7: note: in expansion of macro ‘FC_ASSERT’ FC_ASSERT( hardfork == hfp.last_hardfork + 1, "Hardfork being applied out of order", ("hardfork",hardfork)("hfp.last_hardfork",hfp.last_hardfork) ); ^ c++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions. libraries/chain/CMakeFiles/steemit_chain.dir/build.make:62: recipe for target 'libraries/chain/CMakeFiles/steemit_chain.dir/database.cpp.o' failed make[2]: *** [libraries/chain/CMakeFiles/steemit_chain.dir/database.cpp.o] Error 4 CMakeFiles/Makefile2:985: recipe for target 'libraries/chain/CMakeFiles/steemit_chain.dir/all' failed make[1]: *** [libraries/chain/CMakeFiles/steemit_chain.dir/all] Error 2 Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 ```
author | markopaasila |
---|---|
permlink | re-abit-re-markopaasila-re-b0y2k-steem-0-20160601t094103993z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:41:03 |
last_update | 2016-06-01 09:45:27 |
depth | 3 |
children | 5 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 3,239 |
author_reputation | 32,771,884,740,822 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,386 |
net_rshares | 0 |
mv steem steemBAK git clone https://github.com/steemit/steem.git git submodule update --init --recursive cmake -DENABLE_CONTENT_PATCHING=OFF .
author | b0y2k |
---|---|
permlink | re-markopaasila-re-b0y2k-steem-0-20160601t092432761z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:25:33 |
last_update | 2016-06-01 09:25:33 |
depth | 2 |
children | 4 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 142 |
author_reputation | 576,806,030,298,882 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,374 |
net_rshares | 9,404,613,548 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
markopaasila | 0 | 9,404,613,548 | 100% |
What version of Boost is installed on your system? What version of gcc (output of gcc - v)? It seems unlikely, but maybe there is an issue with your version of Boost that is somehow only triggered now in v0.5.0? Manually compiling Boost 1.57 or 1.58 and pointing to it in the cmake step might be worth a shot. Also, ENABLE_CONTENT_PATCHING is no longer necessary with v0.5.0. If you want a low memory node do `-DLOW_MEMORY_NODE=ON`. And finally, go on the Slack [#help](https://steem.slack.com/messages/help/) channel if you want more direct interactive help.
author | arhag |
---|---|
permlink | re-b0y2k-re-markopaasila-re-b0y2k-steem-0-20160601t111111696z |
category | steem |
json_metadata | {"links":["https://steem.slack.com/messages/help/"]} |
created | 2016-06-01 11:11:12 |
last_update | 2016-06-01 11:11:12 |
depth | 3 |
children | 1 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 563 |
author_reputation | 52,490,827,205,383 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,464 |
net_rshares | 9,475,472,498 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
markopaasila | 0 | 8,777,639,312 | 100% | ||
hcf27 | 0 | 697,833,186 | 100% |
That's what I'm doing, but doesn't work on Ubuntu or Arch. Which distro are you using?
author | markopaasila |
---|---|
permlink | re-b0y2k-re-markopaasila-re-b0y2k-steem-0-20160601t093433660z |
category | steem |
json_metadata | {} |
created | 2016-06-01 09:34:33 |
last_update | 2016-06-01 09:34:33 |
depth | 3 |
children | 1 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 86 |
author_reputation | 32,771,884,740,822 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,382 |
net_rshares | 0 |
Mine was stuck like that at 1 hps for quite a while, probably around 30 mins, I kept it running like that and it later started working. I think all you need to do is wait. Btw, My cli_wallet.exe doesn't work, It shows the transport error. Has anyone fixed it? I changed rpc-endpoint = 127.0.0.1:8090 at configuration but it still doesn't work.
author | tshering-tamang |
---|---|
permlink | re-b0y2k-steem-0-20160601t122841206z |
category | steem |
json_metadata | {} |
created | 2016-06-01 12:28:42 |
last_update | 2016-06-01 12:28:42 |
depth | 1 |
children | 4 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 344 |
author_reputation | 11,388,588,016,470 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,514 |
net_rshares | 0 |
been chugging away for a few hours now... still 1hps :(
author | b0y2k |
---|---|
permlink | re-tshering-tamang-re-b0y2k-steem-0-20160601t135801456z |
category | steem |
json_metadata | {} |
created | 2016-06-01 13:59:00 |
last_update | 2016-06-01 13:59:00 |
depth | 2 |
children | 3 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 55 |
author_reputation | 576,806,030,298,882 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,609 |
net_rshares | 0 |
hmmm Network problems can cause this as well. Have you checked your connections?
author | tshering-tamang |
---|---|
permlink | re-b0y2k-re-tshering-tamang-re-b0y2k-steem-0-20160601t143049687z |
category | steem |
json_metadata | {} |
created | 2016-06-01 14:30:54 |
last_update | 2016-06-01 14:30:54 |
depth | 3 |
children | 2 |
last_payout | 2016-08-19 14:59:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 80 |
author_reputation | 11,388,588,016,470 |
root_title | "Steem 0.5.0 Release Candidate has broken my miners.." |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 20,628 |
net_rshares | 5,281,488,600 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
b0y2k | 0 | 5,281,488,600 | 100% |