Author

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

full member
Activity: 224
Merit: 100

http://pastebin.com/q0Cd1uE8

anyone know how to solve the libboost linking problem I seem to be having?

You should use the latest version of libboost : 1.55
that is with using the latest version of libboost, for some reason it is referencing icu48 instead of 52 like it should

what say commands
Code:
ls -l /lib64/libboost_locale.so
ldd /lib64/libboost_locale.so

(change lib64 if it's elsewhere)
Why do you care it wasn't linked against icu52? Install icu48 or recompile boost.

I care because I can't run simpleminer, it keeps calling for icu48 and icu48 isnt' installed.  libboost 1.55 has been re-installed as well as icu52
sr. member
Activity: 336
Merit: 250

http://pastebin.com/q0Cd1uE8

anyone know how to solve the libboost linking problem I seem to be having?

You should use the latest version of libboost : 1.55
that is with using the latest version of libboost, for some reason it is referencing icu48 instead of 52 like it should

what say commands
Code:
ls -l /lib64/libboost_locale.so
ldd /lib64/libboost_locale.so

(change lib64 if it's elsewhere)
Why do you care it wasn't linked against icu52? Install icu48 or recompile boost.
full member
Activity: 224
Merit: 100

http://pastebin.com/q0Cd1uE8

anyone know how to solve the libboost linking problem I seem to be having?

You should use the latest version of libboost : 1.55
that is with using the latest version of libboost, for some reason it is referencing icu48 instead of 52 like it should
hero member
Activity: 556
Merit: 501
sr. member
Activity: 248
Merit: 251

http://pastebin.com/q0Cd1uE8

anyone know how to solve the libboost linking problem I seem to be having?

You should use the latest version of libboost : 1.55
hero member
Activity: 976
Merit: 646
I'm seeing the "low difficulty share" issue here now.  Took about 24h of testing for it to show up.

I saw this begin happening after a disconnect from extremepool at 11:30 EDT.  Did this happen to others at the same time?

I have added a more complete restart mechanism to mask this even more, but would like to identify the underlying source of the failures.

Miner updated, patch here:

  https://github.com/dave-andersen/boolberry/commit/06998dc0ed2f63683dadf5ea293c8217575c9b46

Will keep testing.  C_Z, if you have any insights to how the scratchpad copy might get permanently desynchronized with the server, I think that's where the error lies.  Hopefully this more complete restart will mask it, but re-downloading the scratchpad will increase bandwidth use, so it'd still be good to fix.

  -Dave

This fix appears effective.

Code:
2014-Jun-15 14:08:52.666932 Failed to submit share!  Updating job.
2014-Jun-15 14:08:52.666939 Too many submission failures.  Something is very wrong.
2014-Jun-15 14:08:52.666944 Excessive failures.  Sleeping 10 seconds and restarting...
2014-Jun-15 14:09:02.679750 Mining with 8 threads

I'll keep digging, however, because of the potential bandwidth use of having to re-download the scratchpad twice a day or so, as the blockchain gets larger.
Megred.
dga
hero member
Activity: 737
Merit: 511
I'm seeing the "low difficulty share" issue here now.  Took about 24h of testing for it to show up.

I saw this begin happening after a disconnect from extremepool at 11:30 EDT.  Did this happen to others at the same time?

I have added a more complete restart mechanism to mask this even more, but would like to identify the underlying source of the failures.

Miner updated, patch here:

  https://github.com/dave-andersen/boolberry/commit/06998dc0ed2f63683dadf5ea293c8217575c9b46

Will keep testing.  C_Z, if you have any insights to how the scratchpad copy might get permanently desynchronized with the server, I think that's where the error lies.  Hopefully this more complete restart will mask it, but re-downloading the scratchpad will increase bandwidth use, so it'd still be good to fix.

  -Dave

This fix appears effective.

Code:
2014-Jun-15 14:08:52.666932 Failed to submit share!  Updating job.
2014-Jun-15 14:08:52.666939 Too many submission failures.  Something is very wrong.
2014-Jun-15 14:08:52.666944 Excessive failures.  Sleeping 10 seconds and restarting...
2014-Jun-15 14:09:02.679750 Mining with 8 threads

I'll keep digging, however, because of the potential bandwidth use of having to re-download the scratchpad twice a day or so, as the blockchain gets larger.
dga
hero member
Activity: 737
Merit: 511
I'm seeing the "low difficulty share" issue here now.  Took about 24h of testing for it to show up.

I saw this begin happening after a disconnect from extremepool at 11:30 EDT.  Did this happen to others at the same time?

I have added a more complete restart mechanism to mask this even more, but would like to identify the underlying source of the failures.

Miner updated, patch here:

  https://github.com/dave-andersen/boolberry/commit/06998dc0ed2f63683dadf5ea293c8217575c9b46

Will keep testing.  C_Z, if you have any insights to how the scratchpad copy might get permanently desynchronized with the server, I think that's where the error lies.  Hopefully this more complete restart will mask it, but re-downloading the scratchpad will increase bandwidth use, so it'd still be good to fix.

  -Dave
member
Activity: 97
Merit: 10
Hi, can me someone help, how can I transfer my BBRs from bittrex to poloniex ?

i need some transfer_id from bittrex , how can i achieve this id on bittrex ?

I recommend transferring the BBR to your personal wallet address first as it would not need a payment ID. Then you would need to deposit into your Poloniex account by following this format:

Code:
transfer 0   
member
Activity: 84
Merit: 10
Hi, can me someone help, how can I transfer my BBRs from bittrex to poloniex ?

i need some transfer_id from bittrex , how can i achieve this id on bittrex ?
hero member
Activity: 588
Merit: 504
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png


Not very useful.  Run from gdb and get backtrace when it dies.  Make sure binary has debug info.
dmesg might also give some clue about the cause of death.
already did
http://i.imgur.com/RcfLvhi.png

my guess is the system is running out of ram.

I've been running in VM with 1gb allocated, easily 24hours. never seen such problems
hero member
Activity: 976
Merit: 646
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png


Not very useful.  Run from gdb and get backtrace when it dies.  Make sure binary has debug info.
dmesg might also give some clue about the cause of death.
already did
http://i.imgur.com/RcfLvhi.png

my guess is the system is running out of ram.

Sounds like it.  Is it possible something *else* is using memory periodically and you're running really close to the limit?

(that ps output would be helpful).  Mine has been locked at 658mb virtual / 18mb resident since I started it running yesterday, but that doesn't mean there's not a memory leak in some other setting.
Have dmesg showed some memory problems ?
dga
hero member
Activity: 737
Merit: 511
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png


Not very useful.  Run from gdb and get backtrace when it dies.  Make sure binary has debug info.
dmesg might also give some clue about the cause of death.
already did
http://i.imgur.com/RcfLvhi.png

my guess is the system is running out of ram.

Sounds like it.  Is it possible something *else* is using memory periodically and you're running really close to the limit?

(that ps output would be helpful).  Mine has been locked at 658mb virtual / 18mb resident since I started it running yesterday, but that doesn't mean there's not a memory leak in some other setting.
full member
Activity: 224
Merit: 100
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png


Not very useful.  Run from gdb and get backtrace when it dies.  Make sure binary has debug info.
dmesg might also give some clue about the cause of death.
already did
http://i.imgur.com/RcfLvhi.png

my guess is the system is running out of ram.
sr. member
Activity: 336
Merit: 250
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png


Not very useful.  Run from gdb and get backtrace when it dies.  Make sure binary has debug info.
dmesg might also give some clue about the cause of death.
dga
hero member
Activity: 737
Merit: 511
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png

Damn.
I'll take a look.
not on all but most of them.  just dies, I could set a cronjob to auto restart it but it would be much easier for miners if they didn't have to take that step.

Can you give more details?
- os / version / cpu
- pool info (which one, or what settings?)
- version of boost installed

I haven't been able to make mine die yet. 

In the interim - don't use cron, just wrap it in a shell script... would it be useful to put an auto-restarter in the simpleminer directory?

Also - check ps or top:  howmuch memory is it using, and is that amount of memory increasing as it runs longer?
full member
Activity: 224
Merit: 100
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png

Damn.
I'll take a look.
not on all but most of them.  just dies, I could set a cronjob to auto restart it but it would be much easier for miners if they didn't have to take that step.

Can you give more details?
- os / version / cpu
- pool info (which one, or what settings?)
- version of boost installed

I haven't been able to make mine die yet.  

In the interim - don't use cron, just wrap it in a shell script... would it be useful to put an auto-restarter in the simpleminer directory?

xubuntu 14.04  dual xeon 5650, hyperthreading disabled 12 total cores.
my pool.. http://bbr.extremepool.org
boost is 1.55
I do have it in a shell scrypt right now. 

fyi I am dayas on irc we talked this morning
full member
Activity: 224
Merit: 100
Good news is that the pool is starting to hit block on a regular basis Smiley

http://bbr.extremepool.org
dga
hero member
Activity: 737
Merit: 511
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png

Damn.
I'll take a look.
not on all but most of them.  just dies, I could set a cronjob to auto restart it but it would be much easier for miners if they didn't have to take that step.

Can you give more details?
- os / version / cpu
- pool info (which one, or what settings?)
- version of boost installed

I haven't been able to make mine die yet. 

In the interim - don't use cron, just wrap it in a shell script... would it be useful to put an auto-restarter in the simpleminer directory?
full member
Activity: 224
Merit: 100
dga, still getting this on most of my own miners
http://i.imgur.com/nDxoP8r.png

Damn.
I'll take a look.
not on all but most of them.  just dies, I could set a cronjob to auto restart it but it would be much easier for miners if they didn't have to take that step.
Jump to: