[BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 426.

tc61

hero member

Activity: 494

Merit: 500

hi all, newb to berry, mining on a pool. how long does it take to find a block, been on a while blocks found never..am I doing something wrong?

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: dga on June 10, 2014, 11:49:34 AM

Quote from: btc-mike on June 10, 2014, 11:01:11 AM

I am testing to see if this resolves the error.

If you have an easy way to reproduce it, I can test too. I don't have my own pool set up, so I was just testing on extremehash. I didn't see the bug before or after the fix, but...

I changed some parameters in config. Maybe it matters for errors .

Code:

 "varDiff": {
            "minDiff": 50000,
            "maxDiff": 10000000,
            "targetTime": 50,  # from 100
            "retargetTime": 30,
            "variancePercent": 30,
            "maxJump": 150000 
        },

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: btc-mike on June 10, 2014, 12:36:31 PM

Quote from: cubydu on June 10, 2014, 12:33:40 PM

Quote from: btc-mike on June 10, 2014, 12:24:29 PM

After about 45 minutes, I get continuous authentication errors and low-diff errors. But the jobs are still coming. Restart simpleminer resolves.

these are old errors

Were these already resolved? How to fix?

I wrote dga only about a time to get new job.

And open ticket about low-diff https://github.com/LucasJones/node-boolberry-pool/issues/1

btc-mike

hero member

Activity: 938

Merit: 1001

Quote from: cubydu on June 10, 2014, 12:33:40 PM

Quote from: btc-mike on June 10, 2014, 12:24:29 PM

After about 45 minutes, I get continuous authentication errors and low-diff errors. But the jobs are still coming. Restart simpleminer resolves.

these are old errors

Were these already resolved? How to fix?

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: btc-mike on June 10, 2014, 12:24:29 PM

After about 45 minutes, I get continuous authentication errors and low-diff errors. But the jobs are still coming. Restart simpleminer resolves.

these are old errors

btc-mike

hero member

Activity: 938

Merit: 1001

After about 45 minutes, I get continuous authentication errors and low-diff errors. But the jobs are still coming. Restart simpleminer resolves.

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: dga on June 10, 2014, 11:49:34 AM

Quote from: btc-mike on June 10, 2014, 11:01:11 AM

I am testing to see if this resolves the error.

If you have an easy way to reproduce it, I can test too. I don't have my own pool set up, so I was just testing on extremehash. I didn't see the bug before or after the fix, but...

You can test with my pool http://79.135.200.108/ . I got errors with this pool.
And I can give you shell access to pool if you need.

dga

hero member

Activity: 737

Merit: 511

Quote from: btc-mike on June 10, 2014, 11:01:11 AM

I am testing to see if this resolves the error.

If you have an easy way to reproduce it, I can test too. I don't have my own pool set up, so I was just testing on extremehash. I didn't see the bug before or after the fix, but...

btc-mike

hero member

Activity: 938

Merit: 1001

Quote from: dga on June 10, 2014, 09:10:39 AM

Quote from: cubydu on June 10, 2014, 07:32:57 AM

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted. I'm not entirely sure if it's the same thing, I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

I am testing to see if this resolves the error.

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: dga on June 10, 2014, 09:10:39 AM

Quote from: cubydu on June 10, 2014, 07:32:57 AM

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted. I'm not entirely sure if it's the same thing, I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

Thanks!
Yes, it is seems.
I'm testing simpleminer 15 minutes.

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: dga on June 10, 2014, 09:10:39 AM

Quote from: cubydu on June 10, 2014, 07:32:57 AM

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted. I'm not entirely sure if it's the same thing, I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

Merged, thank you.

dga

hero member

Activity: 737

Merit: 511

Quote from: cubydu on June 10, 2014, 07:32:57 AM

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Thank you - this might be a bug I hadn't spotted. I'm not entirely sure if it's the same thing, I've submitted a pull request for a fix, but if you want to rebuild for yourself, this is the patch:

Code:

--- a/src/miner/simpleminer.cpp
+++ b/src/miner/simpleminer.cpp
@@ -235,6 +235,9 @@ namespace mining
          threads.push_back(boost::thread(&simpleminer::worker_thread, this, start_nonce, nonce_offset, &results[i]
          nonce_offset += attempts_per_loop;
        }
+       (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+       
+
        BOOST_FOREACH(boost::thread& th, threads)
        {
          th.join();
@@ -281,6 +284,8 @@ namespace mining
              }
              LOG_PRINT_GREEN("Share submitted successfully!", LOG_LEVEL_0);
              new_job_needed = true;
+             (*reinterpret_cast(&m_job.blob[1])) = (start_nonce + nonce_offset);
+
              break;
            }
          }

cubydu

sr. member

Activity: 308

Merit: 250

With last updated simpleminer I get strange picture.
Sometimes simpleminer can't get new job for a long time. Until the network found new block
Pool runs on server with 24 threads and has enough resources.

Code:

2014-Jun-10 15:23:18.289738 Job didn't change
2014-Jun-10 15:23:26.201698 Share found: nonce=10771210 for job=351806463976390, diff: 3350000
, PoW:, height:16546, submitting...
2014-Jun-10 15:23:26.243949 Share submitted successfully!
2014-Jun-10 15:23:26.243991 Getting next job...
2014-Jun-10 15:23:26.282002 Job didn't change
2014-Jun-10 15:23:31.322204 Share found: nonce=13224449 for job=351806463976390, diff: 3350000
, PoW:, height:16546, submitting...
2014-Jun-10 15:23:31.363280 Share submitted successfully!
2014-Jun-10 15:23:31.363339 Getting next job...
2014-Jun-10 15:23:31.402001 Job didn't change
2014-Jun-10 15:23:51.431627 Getting next job...
2014-Jun-10 15:23:51.470557 Job didn't change
2014-Jun-10 15:24:11.581892 Getting next job...
2014-Jun-10 15:24:11.619042 Job didn't change
2014-Jun-10 15:24:31.723488 Getting next job...
2014-Jun-10 15:24:31.763493 Job didn't change
2014-Jun-10 15:24:51.967757 Getting next job...
2014-Jun-10 15:24:52.007851 Job didn't change
2014-Jun-10 15:25:12.029291 Getting next job...
2014-Jun-10 15:25:12.068339 Job didn't change
2014-Jun-10 15:25:32.271406 Getting next job...
2014-Jun-10 15:25:32.308764 Job didn't change
2014-Jun-10 15:25:52.462629 Getting next job...
2014-Jun-10 15:25:52.501255 Job didn't change
2014-Jun-10 15:26:12.638873 Getting next job...
2014-Jun-10 15:26:12.677568 Job didn't change
2014-Jun-10 15:26:12.638873 Getting next job...
2014-Jun-10 15:26:12.677568 Job didn't change
2014-Jun-10 15:26:32.714673 Getting next job...
2014-Jun-10 15:26:32.756398 Job didn't change
2014-Jun-10 15:26:52.765889 Getting next job...
2014-Jun-10 15:26:52.806491 Job didn't change
2014-Jun-10 15:27:12.889515 Getting next job...
2014-Jun-10 15:27:12.926968 Job didn't change
2014-Jun-10 15:27:33.138448 Getting next job...
2014-Jun-10 15:27:41.544436 Numbers of blocks added to scratchpad: 1
2014-Jun-10 15:27:46.205116 Share found: nonce=2259201 for job=926625466300174, diff: 3350000
, PoW:, height:16546, submitting...
2014-Jun-10 15:27:46.207270 Share submitted successfully!
2014-Jun-10 15:27:46.207330 Getting next job...
2014-Jun-10 15:27:46.247430 Job didn't change

dga

hero member

Activity: 737

Merit: 511

Quote from: crypto_zoidberg on June 10, 2014, 04:52:14 AM

Quote from: BoscoMurray on June 10, 2014, 02:26:27 AM

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work:
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

Can you send full log file, or at least about last 100 screens. I'll try to figure out what happend.
btw: at the moment when blocks stopped to appear you can also see connections count decreased.
http://boolberry.com/munin/localdomain/localhost.localdomain/incoming_connections_count.html

A bit more logging info from my computer, which also had one last night:

2014-Jun-10 00:58:03.741695 [P2P1][sock 66] ip denied 117.131.169.12, shutdowning connection
2014-Jun-10 01:31:34.736434 [P2P3][85.25.196.210:10101 OUT] SYNCHRONIZED OK
2014-Jun-10 01:39:53.998850 [P2P6]ERROR /home/dga/coin/bool/shared/boolberry/trunk/contrib/epee/include/net/lev
in_protocol_handler_async.h:429[bool epee::levin::async_protocol_handler::handle_recv(con
st void*, size_t) [with t_connection_context = nodetool::p2p_connection_context_t_context>; size_t = long unsigned int]][222.223.122.5:52394 INC]Signature mismatch, connection will be closed
2014-Jun-10 01:43:06.791363 [P2P4]ERROR /home/dga/coin/bool/shared/boolberry/trunk/src/currency_core/tx_pool.cp
p:70[bool currency::tx_memory_pool::add_tx(const currency::transaction&, const crypto::hash&, size_t, currency:
:tx_verification_context&, bool)]Transaction with id= bedb3104> used already spent key images
2014-Jun-10 01:43:06.791416 [P2P4]Transaction verification failed:
2014-Jun-10 01:43:06.791442 [P2P4][221.0.76.119:53601 INC]Tx verification failed, dropping connection
2014-Jun-10 01:58:05.595791 [P2P7][sock 59] ip denied 117.131.169.12, shutdowning connection
2014-Jun-10 02:58:32.387880 [P2P5][sock 49] ip denied 117.131.169.12, shutdowning connection
2014-Jun-10 03:03:07.173040 [P2P9]Connecting to 117.218.46.97:10101(white=0, last_seen: d0.h18.m45.s50)...
2014-Jun-10 03:03:08.217350 [P2P3][117.218.46.97:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-10 03:08:48.386494 [miner 0]Found block for difficulty: 79798370751
2014-Jun-10 03:08:48.386729 [miner 0]Block with id:
have not enough proof of work:
nexpected difficulty: 79798370751
2014-Jun-10 03:08:48.400420 [miner 0]ERROR /home/dga/coin/bool/shared/boolberry/trunk/src/currency_core/currency_core.cpp:394[virtual bool currency::core::handle_block_found(currency::block&)]mined block failed verification

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: dga on June 10, 2014, 03:17:08 AM

Quote from: BoscoMurray on June 10, 2014, 02:26:27 AM

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work:
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

I think there's a bug - I've been seeing this during some of the big "no block for an hour" things as well. My hypothesis is that it's related to the block timestamp getting thrown off by a miner with a bad clock, but I'll try to investigate more in the morning if nobody else figures it out before then.

I guess timestamp is not related, since expected difficulty is seems right.
Probably miner have a bug in reorganize when alternative chain is loaded. I'll do hot fix today that reloads scratchpad from blockchain in case of such errors with mined blocks.

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: BoscoMurray on June 10, 2014, 02:26:27 AM

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work:
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

Can you send full log file, or at least about last 100 screens. I'll try to figure out what happend.
btw: at the moment when blocks stopped to appear you can also see connections count decreased.
http://boolberry.com/munin/localdomain/localhost.localdomain/incoming_connections_count.html

dga

hero member

Activity: 737

Merit: 511

Quote from: BoscoMurray on June 10, 2014, 02:26:27 AM

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work:
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

I think there's a bug - I've been seeing this during some of the big "no block for an hour" things as well. My hypothesis is that it's related to the block timestamp getting thrown off by a miner with a bad clock, but I'll try to investigate more in the morning if nobody else figures it out before then.

BoscoMurray

sr. member

Activity: 450

Merit: 250

I have a few of these:

2014-Jun-10 07:18:20.634615 [P2P6]Blockchain stored OK.
2014-Jun-10 08:11:32.679787 [miner 7]Found block for difficulty: 79798370751
2014-Jun-10 08:11:32.683788 [miner 7]Block with id: <9e634e9cc3677301977e7fc114f2353bb1b9f341d72b214612b031b16cf40d48>
have not enough proof of work:
nexpected difficulty: 79798370751
2014-Jun-10 08:11:32.698789 [miner 7]ERROR ..\..\src\currency_core\currency_core.cpp:384[currency::core::handle_block_found]mined block failed verification

Not enough proof? Anything I can do to prevent this in the future?

aloney

full member

Activity: 122

Merit: 100

what happend?? over more than an hour, not even one block was found on the network??

eddywise

sr. member

Activity: 253

Merit: 250

Let's Boolberry

Great,we have the GUI now
next,I think should be the GPU miner Grin

Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 426. (Read 1210779 times)