shojayxt
Legendary
Offline
Activity: 896
Merit: 1001
|
|
February 04, 2016, 04:03:48 PM |
|
poloniexBBR markets frozen while we investigate issues with the network. Posted by MobyDick
Now's the time to fire up a bbr daemon, run a miner, and support the network.
|
|
|
|
muchoman
|
|
February 04, 2016, 04:08:06 PM |
|
poloniexBBR markets frozen while we investigate issues with the network. Posted by MobyDick
Now's the time to fire up a bbr daemon, run a miner, and support the network. Daemon will not sync, no solo mining.
|
|
|
|
smic
|
|
February 04, 2016, 04:13:45 PM |
|
poloniexBBR markets frozen while we investigate issues with the network. Posted by MobyDick
Now's the time to fire up a bbr daemon, run a miner, and support the network. Daemon will not sync, no solo mining. i don't understand beacause the nethashrate is up? Hash Rate: 140.80 MH/sec from cncoin.farm
|
|
|
|
LucyLovesCrypto
|
|
February 04, 2016, 04:36:01 PM |
|
poloniexBBR markets frozen while we investigate issues with the network. Posted by MobyDick
Now's the time to fire up a bbr daemon, run a miner, and support the network. Daemon will not sync, no solo mining. Did you try these priority nodes? Start the daemon with the --add-priority-node argument and use these peers:
print_cn 2016-Jan-31 18:08:21.914303 Connections: Remote Host Peer id Recv/Sent (idle,sec) State Livetime(seconds) [OUT]5.9.38.137:10101 a9046e7dadd740ea 296177(26)/110759(27) state_normal 2217 [OUT]66.228.33.249:10101 7b310d1ae9aae498 222316(27)/63471(27) state_normal 2314 [OUT]81.39.24.26:10101 1ed0c1e83bd84bfb 713628(24)/123872(24) state_normal 2341 [OUT]106.185.46.152:10101 1056f3d057a82878 291907(26)/111263(27) state_normal 2222 [OUT]128.204.214.119:10101 914c40381b15b1c1 2115695(26)/135045(27) state_normal 2335 [OUT]59.120.166.36:10101 ccd2aae0f31fa810 302456(26)/114974(27) state_normal 2309 [OUT]91.155.235.8:10101 af038b424f669694 305199(15)/116435(15) state_normal 2303
boolbd --add-priority-node xxx.xxx.xxx.xxx:10101 --add-priority-node xxx.xxx.xxx.xxx:10101 etc...
--add-peer arg Manually add peer to local peerlist --add-priority-node arg Specify list of peers to connect to and attempt to keep the connection open
|
|
|
|
muchoman
|
|
February 04, 2016, 04:41:54 PM |
|
poloniexBBR markets frozen while we investigate issues with the network. Posted by MobyDick
Now's the time to fire up a bbr daemon, run a miner, and support the network. Daemon will not sync, no solo mining. Did you try these priority nodes? Start the daemon with the --add-priority-node argument and use these peers:
print_cn 2016-Jan-31 18:08:21.914303 Connections: Remote Host Peer id Recv/Sent (idle,sec) State Livetime(seconds) [OUT]5.9.38.137:10101 a9046e7dadd740ea 296177(26)/110759(27) state_normal 2217 [OUT]66.228.33.249:10101 7b310d1ae9aae498 222316(27)/63471(27) state_normal 2314 [OUT]81.39.24.26:10101 1ed0c1e83bd84bfb 713628(24)/123872(24) state_normal 2341 [OUT]106.185.46.152:10101 1056f3d057a82878 291907(26)/111263(27) state_normal 2222 [OUT]128.204.214.119:10101 914c40381b15b1c1 2115695(26)/135045(27) state_normal 2335 [OUT]59.120.166.36:10101 ccd2aae0f31fa810 302456(26)/114974(27) state_normal 2309 [OUT]91.155.235.8:10101 af038b424f669694 305199(15)/116435(15) state_normal 2303
boolbd --add-priority-node xxx.xxx.xxx.xxx:10101 --add-priority-node xxx.xxx.xxx.xxx:10101 etc...
--add-peer arg Manually add peer to local peerlist --add-priority-node arg Specify list of peers to connect to and attempt to keep the connection open
Yes, I did.
|
|
|
|
ol92
|
|
February 04, 2016, 04:44:17 PM |
|
poloniexBBR markets frozen while we investigate issues with the network. Posted by MobyDick
Now's the time to fire up a bbr daemon, run a miner, and support the network. Daemon will not sync, no solo mining. i don't understand beacause the nethashrate is up? Hash Rate: 140.80 MH/sec from cncoin.farm Probably: the main pool is down and the network hashrate isn't enough to find quickly the next block at current difficulty. Main pool is down and difficulty is high : hence the problem to find the next block. Hashrate corespond to previously found block and will be updated with next block found. Present hashrate is probably very low. PS : the main pool may host some key nodes for network sync, hence the difficulty to synchronize.
|
|
|
|
clintar2
|
|
February 04, 2016, 04:52:27 PM |
|
i think this is my fault by mistake i flooded the network with many small tx (to send to other wallet, so i can send to exchange) and since then boold daemon of pools crash ? whoops *i was CPU mining and have a lot of Dust I did see a lot of little transactions in the previous block. Doubt it was your fault, though.
|
|
|
|
jwinterm
Legendary
Offline
Activity: 3136
Merit: 1116
|
|
February 04, 2016, 04:55:40 PM |
|
I was able to sync daemon this morning, and tried to solo mine, but every share I found was getting rejected.
|
|
|
|
shojayxt
Legendary
Offline
Activity: 896
Merit: 1001
|
|
February 04, 2016, 04:57:16 PM |
|
|
|
|
|
jwinterm
Legendary
Offline
Activity: 3136
Merit: 1116
|
|
February 04, 2016, 04:59:56 PM |
|
Hmm, has the miner changed since summer (last time I was mining)?
|
|
|
|
|
smic
|
|
February 04, 2016, 05:17:41 PM |
|
by the way... someone to kindness can put the link for Windows 10 64bit amd 7950-7970 - r280 - r290? that works with radeon crimson? thx
|
|
|
|
damashup
|
|
February 04, 2016, 05:22:48 PM Last edit: February 04, 2016, 06:29:01 PM by damashup |
|
Tried start the daemon on a Linux box and got the following error: 2016-Feb-04 13:25:13.934656 [P2P8][66.228.33.249:10101 OUT]Sync data returned unknown top block: 216575 -> 448452 [231877 blocks (322 days) behind] SYNCHRONIZATION started 2016-Feb-04 13:25:13.934942 [P2P8][66.228.33.249:10101 OUT] COMMAND_HANDSHAKE INVOKED OK 2016-Feb-04 13:25:13.935476 [P2P0]Connecting to 81.39.24.26:10101(white=1, last_seen: never)... 2016-Feb-04 13:25:14.009604 [P2P7]Ip 66.228.33.249is unblocked. 2016-Feb-04 13:25:14.026837 [P2P5]ERROR /root/boolberry/src/currency_core/blockchain_storage.cpp:921[bool currency::blockchain_storage::complete_timestamps_vector(uint64_t, std::vector<long unsigned int>&)]internal error: passed start_height = 216575 not less then m_blocks.size()=216575 Segmentation fault (core dumped) Steps taken: - sudo add-apt-repository ppa:boost-latest/ppa - sudo apt-get update - sudo apt-get -y install gcc-4.8 g++-4.8 libboost1.55-all-dev git cmake - git clone https://github.com/cryptozoidberg/boolberry.git- cd boolberry; make - cd build/release/src - make ./boolbd --add-priority-node 5.9.38.137:10101 --add-priority-node 66.228.33.249:10101 --add-priority-node 81.39.24.26:10101 --add-priority-node 106.185.46.152:10101 --add-priority-node 128.204.214.119:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 1.155.235.8:10101 (been awhile since I tried to solo mine, are my steps out-of-date?)
|
|
|
|
coinrus9
Newbie
Offline
Activity: 29
Merit: 0
|
|
February 04, 2016, 05:36:01 PM |
|
hey i don't get prize for destroying BBR's net ?
|
|
|
|
|
jwinterm
Legendary
Offline
Activity: 3136
Merit: 1116
|
|
February 04, 2016, 06:07:49 PM |
|
hey i don't get prize for destroying BBR's net ?
|
|
|
|
coinrus9
Newbie
Offline
Activity: 29
Merit: 0
|
|
February 04, 2016, 06:08:35 PM |
|
good i can see new blocks now what caused this network downtime ? bug with daemons ?
|
|
|
|
shojayxt
Legendary
Offline
Activity: 896
Merit: 1001
|
|
February 04, 2016, 06:14:50 PM |
|
hey i don't get prize for destroying BBR's net ? Why would anyone want to destroy BBR?
|
|
|
|
coinrus9
Newbie
Offline
Activity: 29
Merit: 0
|
|
February 04, 2016, 06:18:53 PM |
|
hey i don't get prize for destroying BBR's net ? Why would anyone want to destroy BBR? it was by mistake maybe the amount and kind of TX cause the bug great discoveries happen by mistakes..
|
|
|
|
shojayxt
Legendary
Offline
Activity: 896
Merit: 1001
|
|
February 04, 2016, 06:22:16 PM |
|
hey i don't get prize for destroying BBR's net ? Why would anyone want to destroy BBR? it was by mistake maybe the amount and kind of TX cause the bug great discoveries happen by mistakes.. The hashrate ramped up significantly with the increase in market capitalization. It's all worked out now. Just a minor burp.
|
|
|
|
|