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

emontmon

member

Activity: 196

Merit: 10

i get the same error. i just updated to .13 and i get blue message tp update.....

cbuchner1

hero member

Activity: 756

Merit: 502

also interesting

Code:

2014-Jun-11 01:12:07.465459 [P2P4]Fresh maintainers info recieved(timestamp: 1402445429)
2014-Jun-11 01:12:07.465552 [P2P4]Newer version avaliable: 0.1.1.13, current version: 0.1.1.12(7dfb3d3-dirty)

the code thinks it is still 0.1.1.12(7dfb3d3-dirty) despite being a fresh checkout of github master (0.1.1.13)

baigreen

full member

Activity: 625

Merit: 100

Mine is Boolberry v0.1.1.13(58fd3dd)
Also print This software is is up to date, please update.

Quote

2014-Jun-11 06:44:30.519804 Starting...
2014-Jun-11 06:44:30.543727 Boolberry v0.1.1.13(58fd3dd)
2014-Jun-11 06:44:30.544092 Module folder: ./boolbd
2014-Jun-11 06:44:30.544931 Initializing p2p server...
2014-Jun-11 06:44:30.547592 Binding on 0.0.0.0:10101
2014-Jun-11 06:44:30.547968 Net service binded on 0.0.0.0:10101
2014-Jun-11 06:44:30.548194 P2p server initialized OK on port: 10101
2014-Jun-11 06:44:30.548374 Starting UPnP
2014-Jun-11 06:44:30.548580 Initializing currency protocol...
2014-Jun-11 06:44:30.548761 Currency protocol initialized OK
2014-Jun-11 06:44:30.548946 Initializing core rpc server...
2014-Jun-11 06:44:30.549118 Binding on 127.0.0.1:10102
2014-Jun-11 06:44:30.549365 Core rpc server initialized OK on port: 10102
2014-Jun-11 06:44:30.549548 Initializing core...
2014-Jun-11 06:44:30.549842 Loading blockchain...
2014-Jun-11 06:44:31.365472 Blockchain initialized. last block: 16857, d0.h0.m6.s6 time ago, current difficulty: 64687570143
2014-Jun-11 06:44:31.365859 Core initialized OK
2014-Jun-11 06:44:31.366092 Starting core rpc server...
2014-Jun-11 06:44:31.366240 Run net_service loop( 2 threads)...
2014-Jun-11 06:44:31.366456 [SRV_MAIN]Core rpc server started ok
2014-Jun-11 06:44:31.366580 [SRV_MAIN]Starting p2p net loop...
2014-Jun-11 06:44:31.366715 [SRV_MAIN]Run net_service loop( 10 threads)...
2014-Jun-11 06:44:32.366965 [P2P0]Connecting to 173.236.43.58:10101(white=1, last_seen: d0.h0.m1.s2)...
2014-Jun-11 06:44:32.367295 [P2P9]
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.

You can set the level of process detailization by using command "set_log ", where is either 0 (no details), 1 (current block height synchronized), or 2 (all details).

Use "help" command to see the list of available commands.

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2014-Jun-11 06:44:33.833279 [P2P8]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************
2014-Jun-11 06:44:33.834417 [P2P8][173.236.43.58:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:33.834699 [P2P0]Connecting to 203.195.129.161:10101(white=1, last_seen: d0.h0.m1.s4)...
2014-Jun-11 06:44:34.016409 [P2P7][203.195.129.161:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:34.016721 [P2P0]Connecting to 107.170.128.107:10101(white=1, last_seen: d0.h0.m1.s4)...
2014-Jun-11 06:44:34.926226 [P2P8][107.170.128.107:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:34.926676 [P2P0]Connecting to 115.29.100.223:10101(white=1, last_seen: d0.h0.m1.s5)...
2014-Jun-11 06:44:34.931491 [P2P6][115.29.100.223:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:34.933444 [P2P0]Connecting to 107.170.116.52:10101(white=1, last_seen: d1.h5.m23.s36)...
2014-Jun-11 06:44:35.684915 [P2P8][107.170.116.52:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:35.702754 [P2P0]Connecting to 82.80.32.35:10101(white=0, last_seen: d0.h0.m0.s12)...
2014-Jun-11 06:44:36.881494 [P2P6][82.80.32.35:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:36.882073 [P2P0]Connecting to 107.140.65.3:10101(white=0, last_seen: d0.h0.m2.s51)...
2014-Jun-11 06:44:37.870217 [P2P1][107.140.65.3:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:37.870914 [P2P0]Connecting to 128.199.196.65:10101(white=0, last_seen: d0.h0.m0.s10)...
2014-Jun-11 06:44:38.195461 [P2P7][128.199.196.65:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Jun-11 06:44:41.196293 [P2P1][URGENT]:This software is is up to date, please update.
2014-Jun-11 06:44:52.197399 [P2P6][URGENT]:This software is is up to date, please update.

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: crypto_zoidberg on June 10, 2014, 06:53:51 PM

Quote from: cubydu on June 10, 2014, 06:40:17 PM

Daemon output

Code:

2014-Jun-11 01:37:06.828478 [P2P2][URGENT]:This software is is up to date, please update.
2014-Jun-11 01:37:17.829092 [P2P8][URGENT]:This software is is up to date, please update.

On what version you are ? (don't care about wrong text)

v0.1.1.11(90ec703)

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: cubydu on June 10, 2014, 06:40:17 PM

Daemon output

Code:

2014-Jun-11 01:37:06.828478 [P2P2][URGENT]:This software is is up to date, please update.
2014-Jun-11 01:37:17.829092 [P2P8][URGENT]:This software is is up to date, please update.

On what version you are ? (don't care about wrong text)

cubydu

sr. member

Activity: 308

Merit: 250

Daemon output

Code:

2014-Jun-11 01:37:06.828478 [P2P2][URGENT]:This software is is up to date, please update.
2014-Jun-11 01:37:17.829092 [P2P8][URGENT]:This software is is up to date, please update.

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Please update daemon to version v0.1.1.15(5e193f8)

1. daemon miner hot fix!!! (solo miners)
2. pool rpc hot fix!!! (pools)

.

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: cubydu on June 10, 2014, 04:44:28 PM

Is this update only for pool/solo daemons ?

Solo. Pools is not affected.
But for pools i have another fix that's comming soon.

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: ?? on ??

Please update daemon to version v0.1.1.12(90ec703) (miner hot fix)!!!

Is this update only for pool/solo daemons ?

surfer43

sr. member

Activity: 560

Merit: 250

"Trading Platform of The Future!"

PoolBerry.org updated.

cubydu

sr. member

Activity: 308

Merit: 250

http://79.135.200.108/ updated.

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: dga on June 10, 2014, 03:46:33 PM

Quote from: crypto_zoidberg on June 10, 2014, 03:22:28 PM

Please all pool owners and solo miners, check your daemon logs now, we stuck again.
It seems that some bug in miner.

Might be coincidence -

I restarted my mining daemon to be able to print_block and see what was going on, and found the next block very shortly thereafter.

I'm *sure* that the latter part was luck - it's a very fast machine but not *that* fast - but I wonder if there was something about the restart that triggered some updates.

I agree with you. I guess in some situations on_block_chain_update() is not called for miner and scratchpad becomes invalid, that's why we have seen wrong PoW hashes. It's just guess, it's hard to reproduce it.
I've pushed hotfix with regular scratchpad update, once 30 sec, for first time it's ok, but it will become expensive when scratchpad will be more than 10-20 MB, hope we gonna find bug by then.

Quote from: dga on June 10, 2014, 03:46:33 PM

The only things I notice about the blocks:

The "extra" field in 16755 is larger than any of the previous several blocks;
16756 included two tx hashes, which none of the previous blocks did.

Code:

16756   "timestamp": 1402428976,
16755   "timestamp": 1402425579,   <- last block found before the gap
16754   "timestamp": 1402425570,
...

And extra fields:

Code:

16756    "timestamp": 1402428976,

  "tx_hashes": [ "9d0367bd319b128856c4b5c0039d81d77da14594753f849a4b2cff25642e43b2", "5f52cc1f3922edaaccac6a226b0c1db4981952c2ead97550c80ba27d8a4bf031"

    "extra": [ 1, 12, 170, 236, 106, 246, 128, 1, 64, 237, 160, 188, 139, 26, 60, 183, 2, 138, 33, 11, 78, 91, 223, 3, 160, 14, 147, 223, 31, 190, 15, 162, 14, 2, 22, 48, 46, 49, 46, 49, 46, 57, 40, 48, 46, 49, 45, 103, 101, 54, 50, 50, 99, 97, 48, 41, 124

16755   "timestamp": 1402425579,
    "extra": [ 1, 254, 90, 32, 214, 169, 66, 142, 107, 82, 112, 69, 141, 195, 9, 6, 153, 36, 236, 134, 174, 29, 214, 163, 233, 119, 179, 189, 81, 22, 225, 246, 0, 2, 32, 48, 46, 49, 46, 49, 46, 49, 49, 40, 51, 48, 49, 55, 52, 102, 50, 45, 100, 105, 114, 116, 121, 41, 0, 0, 0, 0, 7, 89, 162, 98, 0

16754   "timestamp": 1402425570,
    "extra": [ 1, 28, 48, 231, 241, 73, 242, 252, 185, 15, 227, 86, 12, 140, 79, 7, 171, 166, 109, 180, 100, 186, 97, 81, 74, 6, 20, 191, 82, 131, 53, 136, 111, 2, 22, 48, 46, 49, 46, 49, 46, 57, 40, 48, 46, 49, 45, 103, 101, 54, 50, 50, 99, 97, 48, 41, 124

The second of those two tx hashes was a pretty large transaction.

I thought about some combinations of transaction that broke create_block_template(), but since there are no errors in log about this i guess transactions is not related. Not sure about this.

dga

hero member

Activity: 737

Merit: 511

Quote from: crypto_zoidberg on June 10, 2014, 03:22:28 PM

Please all pool owners and solo miners, check your daemon logs now, we stuck again.
It seems that some bug in miner.

Might be coincidence -

I restarted my mining daemon to be able to print_block and see what was going on, and found the next block very shortly thereafter.

I'm *sure* that the latter part was luck - it's a very fast machine but not *that* fast - but I wonder if there was something about the restart that triggered some updates.

The only things I notice about the blocks:

The "extra" field in 16755 is larger than any of the previous several blocks;
16756 included two tx hashes, which none of the previous blocks did.

Code:

16756   "timestamp": 1402428976,
16755   "timestamp": 1402425579,   <- last block found before the gap
16754   "timestamp": 1402425570,
...

And extra fields:

Code:

16756    "timestamp": 1402428976,

  "tx_hashes": [ "9d0367bd319b128856c4b5c0039d81d77da14594753f849a4b2cff25642e43b2", "5f52cc1f3922edaaccac6a226b0c1db4981952c2ead97550c80ba27d8a4bf031"

    "extra": [ 1, 12, 170, 236, 106, 246, 128, 1, 64, 237, 160, 188, 139, 26, 60, 183, 2, 138, 33, 11, 78, 91, 223, 3, 160, 14, 147, 223, 31, 190, 15, 162, 14, 2, 22, 48, 46, 49, 46, 49, 46, 57, 40, 48, 46, 49, 45, 103, 101, 54, 50, 50, 99, 97, 48, 41, 124

16755   "timestamp": 1402425579,
    "extra": [ 1, 254, 90, 32, 214, 169, 66, 142, 107, 82, 112, 69, 141, 195, 9, 6, 153, 36, 236, 134, 174, 29, 214, 163, 233, 119, 179, 189, 81, 22, 225, 246, 0, 2, 32, 48, 46, 49, 46, 49, 46, 49, 49, 40, 51, 48, 49, 55, 52, 102, 50, 45, 100, 105, 114, 116, 121, 41, 0, 0, 0, 0, 7, 89, 162, 98, 0

16754   "timestamp": 1402425570,
    "extra": [ 1, 28, 48, 231, 241, 73, 242, 252, 185, 15, 227, 86, 12, 140, 79, 7, 171, 166, 109, 180, 100, 186, 97, 81, 74, 6, 20, 191, 82, 131, 53, 136, 111, 2, 22, 48, 46, 49, 46, 49, 46, 57, 40, 48, 46, 49, 45, 103, 101, 54, 50, 50, 99, 97, 48, 41, 124

The second of those two tx hashes was a pretty large transaction.

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Please all pool owners and solo miners, check your daemon logs now, we stuck again.
It seems that some bug in miner.

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: pt7 on June 10, 2014, 02:52:02 PM

Quote from: cubydu on June 10, 2014, 02:48:51 PM

Quote from: c18machine on June 10, 2014, 02:47:34 PM

Quote from: tc61 on June 10, 2014, 02:45:12 PM

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?

dont pool mine for now.

Why ?

Pools are not yet ready for prime time. Unfortunately they are bodly listed at the top of the OP page. I think they should be be moved to near the bottom, and with a disclaimer.

http://bbr.extremepool.org/ found 8 blocks

http://79.135.200.108/ found 4 blocks (1 I deleted)

Solo mining profitable only if you have cpu farm.

pt7

member

Activity: 98

Merit: 10

Quote from: cubydu on June 10, 2014, 02:48:51 PM

Quote from: c18machine on June 10, 2014, 02:47:34 PM

Quote from: tc61 on June 10, 2014, 02:45:12 PM

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?

dont pool mine for now.

Why ?

Pools are not yet ready for prime time. Unfortunately they are bodly listed at the top of the OP page. I think they should be be moved to near the bottom, and with a disclaimer.

tc61

hero member

Activity: 494

Merit: 500

Any newb tutorial on how to solo mine

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: tc61 on June 10, 2014, 02:45:12 PM

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?

(Pool hash rate * 86400) / current diff = blocks per day

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: c18machine on June 10, 2014, 02:47:34 PM

Quote from: tc61 on June 10, 2014, 02:45:12 PM

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?

dont pool mine for now.

Why ?

c18machine

newbie

Activity: 59

Merit: 0

Quote from: tc61 on June 10, 2014, 02:45:12 PM

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?

dont pool mine for now.

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