Author

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

full member
Activity: 202
Merit: 104
You would have to setup your own pool.  It's not that difficult.  https://github.com/clintar/node-cryptonote-pool
Even better, https://github.com/clintar/cryptonote-xmr-pool
I got so many dumb pool repos..
legendary
Activity: 896
Merit: 1001
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.

Yup pool mining is broken right now. Neither Suprnova or Mbk work properly.

What daemon are you using? I've tried boolbd and when it finds a block it freaks out and breaks.

I'm using the open-cl from mbk https://github.com/mbkuperman/boolberry-opencl/releases

Like someone already stated though, you need to have plenty of RAM.  The blockchain is over three gigs and that gets loaded into memory so you're basically out of RAM.  I had the same problem on a box with only 4 gigs of RAM.  I doubled it to 8 gigs and everything works fine.  Same thing when running a pool. You need plenty of RAM or else the daemon will die.    

Yeah, I tried boolbd for a bit. Every time it found a block the miner would crash. It also used 100% of my CPU. It wouldn't load with 4GB as well and I had to install 8GB.

Is there anyway to setup one stratum locally and have miners connect to it?


may i suggest you to try http://bbr.poolto.be ?
pool is running since more 2 years.
payout working fine.

I'll give it a shot, but payouts from Suprnova were less then 50% of what I should've been making, even less on Mbk.

You would have to setup your own pool.  It's not that difficult.  https://github.com/clintar/node-cryptonote-pool
legendary
Activity: 1750
Merit: 1024
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.

Yup pool mining is broken right now. Neither Suprnova or Mbk work properly.

What daemon are you using? I've tried boolbd and when it finds a block it freaks out and breaks.

I'm using the open-cl from mbk https://github.com/mbkuperman/boolberry-opencl/releases

Like someone already stated though, you need to have plenty of RAM.  The blockchain is over three gigs and that gets loaded into memory so you're basically out of RAM.  I had the same problem on a box with only 4 gigs of RAM.  I doubled it to 8 gigs and everything works fine.  Same thing when running a pool. You need plenty of RAM or else the daemon will die.    

Yeah, I tried boolbd for a bit. Every time it found a block the miner would crash. It also used 100% of my CPU. It wouldn't load with 4GB as well and I had to install 8GB.

Is there anyway to setup one stratum locally and have miners connect to it?


may i suggest you to try http://bbr.poolto.be ?
pool is running since more 2 years.
payout working fine.

I'll give it a shot, but payouts from Suprnova were less then 50% of what I should've been making, even less on Mbk.
newbie
Activity: 43
Merit: 0
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.

Yup pool mining is broken right now. Neither Suprnova or Mbk work properly.

What daemon are you using? I've tried boolbd and when it finds a block it freaks out and breaks.

may i suggest you to try http://bbr.poolto.be ?
pool is running since more 2 years.
payout working fine.

+1 for this pool. Pool is working like a dream fast and reliable. Thanks Pcfill  Smiley

I agree, I really like this pool. It's small at the moment, but reliable. I'm on monero (xmr.poolto.be), and the fixed diff is a big plus for me. Got also some answers in their irc, since I'm a real beginner, so a big plus from me.
member
Activity: 87
Merit: 11
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.

Yup pool mining is broken right now. Neither Suprnova or Mbk work properly.

What daemon are you using? I've tried boolbd and when it finds a block it freaks out and breaks.

may i suggest you to try http://bbr.poolto.be ?
pool is running since more 2 years.
payout working fine.

+1 for this pool. Pool is working like a dream fast and reliable. Thanks Pcfill  Smiley
member
Activity: 86
Merit: 10
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.

Yup pool mining is broken right now. Neither Suprnova or Mbk work properly.

What daemon are you using? I've tried boolbd and when it finds a block it freaks out and breaks.

may i suggest you to try http://bbr.poolto.be ?
pool is running since more 2 years.
payout working fine.
legendary
Activity: 896
Merit: 1001
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.

Yup pool mining is broken right now. Neither Suprnova or Mbk work properly.

What daemon are you using? I've tried boolbd and when it finds a block it freaks out and breaks.

I'm using the open-cl from mbk https://github.com/mbkuperman/boolberry-opencl/releases

Like someone already stated though, you need to have plenty of RAM.  The blockchain is over three gigs and that gets loaded into memory so you're basically out of RAM.  I had the same problem on a box with only 4 gigs of RAM.  I doubled it to 8 gigs and everything works fine.  Same thing when running a pool. You need plenty of RAM or else the daemon will die.   
legendary
Activity: 1750
Merit: 1024
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.

Yup pool mining is broken right now. Neither Suprnova or Mbk work properly.

What daemon are you using? I've tried boolbd and when it finds a block it freaks out and breaks.
legendary
Activity: 896
Merit: 1001
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.


I don't bother with the pools.  Too many issues.  I use mbk's boolberry-opencl to solomine and am finding blocks consistently.  The hashrate is low enough that solo mining is still the best option for me.  I get much less coins mining on a pool.  I'm also not affected by any DDOS attacks.  I did have a private pool setup but I seem to get more blocks with the solo mining using the daemon rather than pointing my miners at a pool.
hero member
Activity: 591
Merit: 501
Scavenger of Crypto Sorrow
Looks like mbk's pool crapped again. No payouts for 10 hours. This is getting really annoying.
member
Activity: 86
Merit: 10
Pool back online ! After weeks of DDOS..

Dear miners, new setup is ready (new isp, new box) :

http://bbr.poolto.be

Thanks for your support !

is this also can be done with solo mining just wanted to try if my laptop can get some BBR using your pool thanks.

If you have 5Gb of RAM to spare, you can do solo mining. Otherwise don't bother. Pool mining works fine most of the time.


How do you solomine then? I attempted to use boolbd, but it seems to crash every time a block is found. It also uses the entirety of the CPU.

You need boolbd running to solomine.
Running it is quite.. "touchy" latelly, it crash often yes.
how many hashes (MH/s) do you expect ? cause to solomine you need quite a lot !
regards,
legendary
Activity: 1750
Merit: 1024
Pool back online ! After weeks of DDOS..

Dear miners, new setup is ready (new isp, new box) :

http://bbr.poolto.be

Thanks for your support !

is this also can be done with solo mining just wanted to try if my laptop can get some BBR using your pool thanks.

If you have 5Gb of RAM to spare, you can do solo mining. Otherwise don't bother. Pool mining works fine most of the time.


How do you solomine then? I attempted to use boolbd, but it seems to crash every time a block is found. It also uses the entirety of the CPU.
legendary
Activity: 1108
Merit: 1005
Quote
Those line numbers don't look like they line up with this. Please use this repo:
https://github.com/clintar/cryptonote-universal-pool

I had it working for two days without problems, was finding blocks.
But now, strange thing happened to me, I start to get this error message

2016-09-23 17:16:44 [api] Broadcasting to 0 visitors and 0 address lookups
2016-09-23 17:16:46 [master] Pool fork 2 died, spawning replacement worker...
2016-09-23 17:16:46 [pool] (Thread 3) Miner connected 1DFmFSA2151eScguvHf93pU7xJvEwvzhAcC8cDKfANk63D8nPqNWE18NXmBNkjpCtnRYXXW9dQkyu8q [email protected]
2016-09-23 17:16:47 [api] Stat collection finished: 1 ms redis, 4 ms daemon
2016-09-23 17:16:47 [api] Broadcasting to 0 visitors and 0 address lookups
2016-09-23 17:16:49 [pool] (Thread 2) Started server listening on port 5555
2016-09-23 17:16:49 [pool] (Thread 2) Started server listening on port 7777
2016-09-23 17:16:49 [master] Pool fork 3 died, spawning replacement worker...
2016-09-23 17:16:49 [pool] (Thread 4) Miner connected 1DFmFSA2151eScguvHf93pU7xJvEwvzhAcC8cDKfANk63D8nPqNWE18NXmBNkjpCtnRYXXW9dQkyu8q [email protected]


I've tried changing ports, restart redis, but it's still in there.
Also I tried to make clean install on second machine, and I'm getting same error in there as well.
And now I'm stuck, and can't move on.
And, this what miner's  showing

[2016-09-23 17:33:59] GPU #0: GeForce GTX 750 Ti: 16140433 hashes, 730.07 kh/s
[2016-09-23 17:34:08] GPU #1: GeForce GTX 750 Ti: 11496820 hashes, 799.20 kh/s
[2016-09-23 17:34:14] GPU #2: GeForce GTX 750 Ti: 35281080 hashes, 798.74 kh/s
[2016-09-23 17:34:49] stratum_recv_line failed
[2016-09-23 17:34:49] Stratum connection interrupted
[2016-09-23 17:34:49] GPU #1: GeForce GTX 750 Ti: 33142201 hashes, 797.58 kh/s
[2016-09-23 17:34:49] GPU #0: GeForce GTX 750 Ti: 36831601 hashes, 731.96 kh/


Can you help me with this too?
cheers
Yuck, what version of node is that running on? I think there sounds there be more errors about it crashing and in what line.

I have v0.10.25 on both machines. You think it's a problem? Because It was working fine, with this version.
And I'm sorry, but I'm not sure, what you mean, with your second question.
hero member
Activity: 591
Merit: 501
Scavenger of Crypto Sorrow
Pool back online ! After weeks of DDOS..

Dear miners, new setup is ready (new isp, new box) :

http://bbr.poolto.be

Thanks for your support !

is this also can be done with solo mining just wanted to try if my laptop can get some BBR using your pool thanks.

If you have 5Gb of RAM to spare, you can do solo mining. Otherwise don't bother. Pool mining works fine most of the time.
member
Activity: 86
Merit: 10
Pool back online ! After weeks of DDOS..

Dear miners, new setup is ready (new isp, new box) :

http://bbr.poolto.be

Thanks for your support !

is this also can be done with solo mining just wanted to try if my laptop can get some BBR using your pool thanks.

hm, solo mining is not compatible with pool mining.
Either you mine solo, either you mine on a pool.
Which OS is using your laptop? ou can cpu or gpu mine.
But using a laptop, gpu mine is clearly not recommended
hero member
Activity: 2128
Merit: 520
Pool back online ! After weeks of DDOS..

Dear miners, new setup is ready (new isp, new box) :

http://bbr.poolto.be

Thanks for your support !

is this also can be done with solo mining just wanted to try if my laptop can get some BBR using your pool thanks.
member
Activity: 86
Merit: 10
Pool back online ! After weeks of DDOS..

Dear miners, new setup is ready (new isp, new box) :

http://bbr.poolto.be

Thanks for your support !
full member
Activity: 202
Merit: 104
Quote
Those line numbers don't look like they line up with this. Please use this repo:
https://github.com/clintar/cryptonote-universal-pool

I had it working for two days without problems, was finding blocks.
But now, strange thing happened to me, I start to get this error message

2016-09-23 17:16:44 [api] Broadcasting to 0 visitors and 0 address lookups
2016-09-23 17:16:46 [master] Pool fork 2 died, spawning replacement worker...
2016-09-23 17:16:46 [pool] (Thread 3) Miner connected 1DFmFSA2151eScguvHf93pU7xJvEwvzhAcC8cDKfANk63D8nPqNWE18NXmBNkjpCtnRYXXW9dQkyu8q [email protected]
2016-09-23 17:16:47 [api] Stat collection finished: 1 ms redis, 4 ms daemon
2016-09-23 17:16:47 [api] Broadcasting to 0 visitors and 0 address lookups
2016-09-23 17:16:49 [pool] (Thread 2) Started server listening on port 5555
2016-09-23 17:16:49 [pool] (Thread 2) Started server listening on port 7777
2016-09-23 17:16:49 [master] Pool fork 3 died, spawning replacement worker...
2016-09-23 17:16:49 [pool] (Thread 4) Miner connected 1DFmFSA2151eScguvHf93pU7xJvEwvzhAcC8cDKfANk63D8nPqNWE18NXmBNkjpCtnRYXXW9dQkyu8q [email protected]


I've tried changing ports, restart redis, but it's still in there.
Also I tried to make clean install on second machine, and I'm getting same error in there as well.
And now I'm stuck, and can't move on.
And, this what miner's  showing

[2016-09-23 17:33:59] GPU #0: GeForce GTX 750 Ti: 16140433 hashes, 730.07 kh/s
[2016-09-23 17:34:08] GPU #1: GeForce GTX 750 Ti: 11496820 hashes, 799.20 kh/s
[2016-09-23 17:34:14] GPU #2: GeForce GTX 750 Ti: 35281080 hashes, 798.74 kh/s
[2016-09-23 17:34:49] stratum_recv_line failed
[2016-09-23 17:34:49] Stratum connection interrupted
[2016-09-23 17:34:49] GPU #1: GeForce GTX 750 Ti: 33142201 hashes, 797.58 kh/s
[2016-09-23 17:34:49] GPU #0: GeForce GTX 750 Ti: 36831601 hashes, 731.96 kh/


Can you help me with this too?
cheers
Yuck, what version of node is that running on? I think there sounds there be more errors about it crashing and in what line.
legendary
Activity: 1108
Merit: 1005
Quote
Those line numbers don't look like they line up with this. Please use this repo:
https://github.com/clintar/cryptonote-universal-pool

I had it working for two days without problems, was finding blocks.
But now, strange thing happened to me, I start to get this error message

2016-09-23 17:16:44 [api] Broadcasting to 0 visitors and 0 address lookups
2016-09-23 17:16:46 [master] Pool fork 2 died, spawning replacement worker...
2016-09-23 17:16:46 [pool] (Thread 3) Miner connected 1DFmFSA2151eScguvHf93pU7xJvEwvzhAcC8cDKfANk63D8nPqNWE18NXmBNkjpCtnRYXXW9dQkyu8q [email protected]
2016-09-23 17:16:47 [api] Stat collection finished: 1 ms redis, 4 ms daemon
2016-09-23 17:16:47 [api] Broadcasting to 0 visitors and 0 address lookups
2016-09-23 17:16:49 [pool] (Thread 2) Started server listening on port 5555
2016-09-23 17:16:49 [pool] (Thread 2) Started server listening on port 7777
2016-09-23 17:16:49 [master] Pool fork 3 died, spawning replacement worker...
2016-09-23 17:16:49 [pool] (Thread 4) Miner connected 1DFmFSA2151eScguvHf93pU7xJvEwvzhAcC8cDKfANk63D8nPqNWE18NXmBNkjpCtnRYXXW9dQkyu8q [email protected]


I've tried changing ports, restart redis, but it's still in there.
Also I tried to make clean install on second machine, and I'm getting same error in there as well.
And now I'm stuck, and can't move on.
And, this what miner's  showing

[2016-09-23 17:33:59] GPU #0: GeForce GTX 750 Ti: 16140433 hashes, 730.07 kh/s
[2016-09-23 17:34:08] GPU #1: GeForce GTX 750 Ti: 11496820 hashes, 799.20 kh/s
[2016-09-23 17:34:14] GPU #2: GeForce GTX 750 Ti: 35281080 hashes, 798.74 kh/s
[2016-09-23 17:34:49] stratum_recv_line failed
[2016-09-23 17:34:49] Stratum connection interrupted
[2016-09-23 17:34:49] GPU #1: GeForce GTX 750 Ti: 33142201 hashes, 797.58 kh/s
[2016-09-23 17:34:49] GPU #0: GeForce GTX 750 Ti: 36831601 hashes, 731.96 kh/


Can you help me with this too?
cheers
member
Activity: 86
Merit: 10
Is there are slack with boolberry?
Jump to: