I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)
...
But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.
...
Or still something not quite right with my new node?
Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now. Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend. But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ... By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me. No, here is fine. |
|
|
|
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)
It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.
But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.
What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?
Or still something not quite right with my new node?
Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now. |
|
|
|
Ok, just an update on the explorer http://explorer.mining.blue/en. I got most things working now. I removed things we don't keep track of for this coin. Again, let me know of anything that looks to be wrong., but It should be pretty useful now. Have a great day! |
|
|
|
I have my block explorer up and running at http://explorer.mining.blue/en. It's still in development so don't trust it to be giving accurate info, but I figure it's something at least for now. Please help by letting me know of anything that seems off so I can fix it. It's based on code written for Karbowanec and I've attempted to make equivalent rpc calls in boolberry to get it working here, but unsure about how I've translated some of that. |
|
|
|
If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratchyou can get the branch with git clone -b lmdb_scratch https://github.com/clintar/boolberry.git then mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon should compile it, at least in linux. Let me know if it compiles or not at least!  I tested it out on OSX, this is what I got cmake -DDATABASE=lmdb ../..
-- Building for a 64-bit system
-- Could not find DATABASE in env (not required unless you want to change database type from default: lmdb)
CMake Warning at CMakeLists.txt:56 (find_package):
By not providing "FindBerkeleyDB.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"BerkeleyDB", but CMake did not find one.
Could not find a package configuration file provided by "BerkeleyDB" with
any of the following names:
BerkeleyDBConfig.cmake
berkeleydb-config.cmake
Add the installation prefix of "BerkeleyDB" to CMAKE_PREFIX_PATH or set
"BerkeleyDB_DIR" to a directory containing one of the above files. If
"BerkeleyDB" provides a separate development package or SDK, be sure it has
been installed.
-- BerkeleyDB not found and has been disabled.
-- Boost version: 1.59.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- atomic
-- program_options
-- Found Git: /usr/local/bin/git
CMake Error at contrib/db_drivers/CMakeLists.txt:32 (add_subdirectory):
add_subdirectory given source "liblmdb" which is not an existing directory.
-- Configuring incomplete, errors occurred! this was from the "cmake -DDATABASE=lmdb ../.." line and for the following make command, there is no 'daemon' target to build I'll check a linux node Maybe follow this: http://macappstore.org/berkeley-db/I did have an issue before that should be fixed. It would have a floating point exception in case you ran into that already. |
|
|
|
If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratchyou can get the branch with git clone -b lmdb_scratch https://github.com/clintar/boolberry.git then mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon should compile it, at least in linux. Let me know if it compiles or not at least! I tested it out on OSX, this is what I got cmake -DDATABASE=lmdb ../..
-- Building for a 64-bit system
-- Could not find DATABASE in env (not required unless you want to change database type from default: lmdb)
CMake Warning at CMakeLists.txt:56 (find_package):
By not providing "FindBerkeleyDB.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"BerkeleyDB", but CMake did not find one.
Could not find a package configuration file provided by "BerkeleyDB" with
any of the following names:
BerkeleyDBConfig.cmake
berkeleydb-config.cmake
Add the installation prefix of "BerkeleyDB" to CMAKE_PREFIX_PATH or set
"BerkeleyDB_DIR" to a directory containing one of the above files. If
"BerkeleyDB" provides a separate development package or SDK, be sure it has
been installed.
-- BerkeleyDB not found and has been disabled.
-- Boost version: 1.59.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- atomic
-- program_options
-- Found Git: /usr/local/bin/git
CMake Error at contrib/db_drivers/CMakeLists.txt:32 (add_subdirectory):
add_subdirectory given source "liblmdb" which is not an existing directory.
-- Configuring incomplete, errors occurred! this was from the "cmake -DDATABASE=lmdb ../.." line and for the following make command, there is no 'daemon' target to build I'll check a linux node Oh yeah, you'll need to install libdb-dev on ubuntu, or whatever equivalent for your OS. The code doesn't use it, though, really. |
|
|
|
If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratchyou can get the branch with git clone -b lmdb_scratch https://github.com/clintar/boolberry.git then mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon should compile it, at least in linux. Let me know if it compiles or not at least! |
|
|
|
why the hell is BBR STILL in "maintenance" on cryptopia???
Yeah, they just be counting all the bits in the blockchain to figure out if there was a fork. Really, it reminds of right before polo delisted. |
|
|
|
Just pushed to github security fix.
Issue was discovered by Monero Lab and they kindly noticed me about this case.
Strong advice to everyone who running BBR daemons to update it ASAP.
Zoidberg
What's the official site? boolberry.com or boolberry.org? On both the release to download is yet 0.3.0.41. I need it for Ubuntu Linux. I have a static built version of boolbd daemon with this fix it includes the donations rpc fix, too. Built under Ubuntu 16.04. https://www.dropbox.com/s/l2szdco5365yzow/bbr-linux-v0.3.0.41%285ef2dd5%29-no-gui.tar.bz2?dl=0 |
|
|
|
FYI, everyone, theneonirvana on Slack helped find a bug in bbr daemon rpc command when getting block info that caused it to report full donation amount for "donation" blocks that are the 1% dev fee. It happens every 720 blocks and is 1% of the entire mining reward, so a pool would mine one of those blocks and think it earned that donation amount, for example it would be like 72 coins reported when really the block only earned 8.3. Because of this bug, it is like the pools have been paying back the 1% dev fee to miners, so you're welcome This is a bad bug that I have failed to find and knew something was wrong for a long long time. PCFiL from bbr.poolto.be has been asking me for a fix for a long time, and I could never find a problem with the pool code to explain the random loss of funds, but it was because it is in the daemon. Here's the commit that fixes it https://github.com/clintar/boolberry/commit/f601f8373d2b09ee6c07388ba5633110b241dc17Every pool owner really should apply this. |
|
|
|
|
So can we close this thread up, then? Doesn't seem to be a point for it anymore. Just echoing the original thread.
|
|
|
|
Boolberry Network Address April 13th 2017
POLONIEX DEPOSITS AND WITHDRAWALS ARE RE-ENABLED
Clintar2 has a working LMBD version of Boolberry, no release date yet, stay tuned and positioned accordingly.
@BoolberryTeam on Twitter and it has 69 followers, crypjunkie has been managing that via our Hootsuite account.
Working is a little strong. I got the blockchain syncing, but tests are failing and I've still got to add support for aliases (which i'm doing now) I just am really short on time. |
|
|
|
https://github.com/BlockchainDevelopmentCompany/boolberrysystem ubuntu14.04 64 2017-Mar-30 00:08:27.595838 [P2P8][5.9.44.190:10101 OUT]Sync data returned unknown top block: 201 -> 748247 [748046 blocks (1038 days) behind] SYNCHRONIZATION started 2017-Mar-30 00:08:27.596200 [P2P8][5.9.44.190:10101 OUT] COMMAND_HANDSHAKE INVOKED OK, Remote Daemon Version: Unknown 2017-Mar-30 00:08:27.596371 [P2P0]Connecting to 213.186.170.109:10101(white=0, last_seen: d4.h23.m44.s30)... 2017-Mar-30 00:08:32.597329 [P2P0]Connect failed to 213.186.170.109:10101 2017-Mar-30 00:08:32.597399 [P2P0]Connecting to 176.194.228.74:10101(white=0, last_seen: d36.h7.m36.s4)... Segmentation fault (core dumped) BlockchainDevelopmentCompany boolberry Not run！How to do it? You could run my git repo that got rid of the version string that was causing the segfault if you want to run a daemon with the other features from the BlockchainDevelopmentCompany versoin. |
|
|
|
Hi,
I get an error when trying to mine.
What amI doing wrong?
CL_INVALID_COMMAND_QUEUE
regards,
Enricosofie
Join the slack and you will get an answer via the mining thread, If you are not already registered can you send me your email and i will get you added.  Hang around a min, where are you mining? minerd -a wildkeccak_ocl -o stratum+tcp://bbr.suprnova.cc:7777 -u enricosofie.lap -p x -l scratchpad.bin -k http://bbr.suprnova.cc/scratchpad.bin[2017-03-16 22:14:03.187] [GPU0] scratchpad update 29736544 [2017-03-16 22:14:03.215] [GPU1] scratchpad update 29736544 [2017-03-16 22:14:05.919] [GPU1] error: CL_INVALID_COMMAND_QUEUE Where did you get this miner? I suggest using this one https://github.com/tpruvot/ccminer/releases[2017-03-16 22:26:29] Stratum difficulty set to 9.0 M (2.09202) [2017-03-16 22:26:29] accepted: 1/1 (diff 1.010), 28.35 kH/s yes! [2017-03-16 22:29:44] GPU #0: GeForce GT 720M, 85.02 kH/s [2017-03-16 22:29:44] accepted: 2/13 (diff 0.251), 84.99 kH/s booooo [2017-03-16 22:38:32] GPU #0: GeForce GT 720M, 85.01 kH/s [2017-03-16 22:38:32] accepted: 31/31 (diff 1.073), 85.00 kH/s yes! Is 85kH/s oke for this GPU? I'm not sure for that one. hopefully if it's on a laptop, it doesn't make it too hot |
|
|
|
Hi,
I get an error when trying to mine.
What amI doing wrong?
CL_INVALID_COMMAND_QUEUE
regards,
Enricosofie
Join the slack and you will get an answer via the mining thread, If you are not already registered can you send me your email and i will get you added. Hang around a min, where are you mining? minerd -a wildkeccak_ocl -o stratum+tcp://bbr.suprnova.cc:7777 -u enricosofie.lap -p x -l scratchpad.bin -k http://bbr.suprnova.cc/scratchpad.bin[2017-03-16 22:14:03.187] [GPU0] scratchpad update 29736544 [2017-03-16 22:14:03.215] [GPU1] scratchpad update 29736544 [2017-03-16 22:14:05.919] [GPU1] error: CL_INVALID_COMMAND_QUEUE Where did you get this miner? I suggest using this one https://github.com/tpruvot/ccminer/releases |
|
|
|
Hi,
I get an error when trying to mine.
What amI doing wrong?
CL_INVALID_COMMAND_QUEUE
regards,
Enricosofie
What miner, video card, operating system are you running? |
|
|
|
|
Anyone else having issues depositing to poloniex? I haven't had any show up for a while. (Anyone even here?)
|
|
|
|
Can I get some people to test out mining with my proxy options at http://mining.blue/#getting_started to see if you have any issues? I'm wondering about how well it will work with a lot of concurrent connections. (shamelessly asking for hashrate, really)  but I'd like to know if you use it and how well it runs. You can leave me a P.M. if you like. |
|
|
|
|
I'd just like to jump in to the middle of this love fest to say thank you for a great miner with wildkeccak! Much improved over what's been out there stability-wise. I think there is an issue with getting a new job not and difficulty change not being taken into account on share submission probably based on watching when they start firing (maybe that's from not restarting mining like the other miners do. haven't checked), but it sure is nice to have a miner with more robust code. Thanks Epsylon3 for your work and thanks bensam for ordering it! Sure would be nice if there was a miner for amd support that was as polished as this!
|
|
|
|
NO LUCK WITH SUPRNOVA-- There is a lot of fuss about SpreadCoin and BoolBerrythe last couple of weeks. With the latest v2.0 release of CCminer by TPruvot, I tried BoolBerry at SuprNova using the example batch file within the new v2.0 fileset. I simply connected with the donation address just to see how it worked. I got about 30-60 seconds of accepts, then a long string of rejects. I also pulled sp_ 's SpreadCoin #9 out of mothballs, having never actually used it before. It connects to SuprNova and hashes away, but I never see anything on my dashboard for the single worker. Here is my launch line for BoolBerry (scratchpad.bin is downloaded and in place): ccminer-x64 -a wildkeccak -o stratum+tcp://bbr.suprnova.cc:7777 -u tpruvot.donate -p x -k https://bbr.suprnova.cc/scratchpad.bin -l 64x512 Here is my launch line for SpreadCoin: spreadminer -o stratum+tcp://spr.suprnova.cc:6666 -x 16 -u username.rig1 -p pass The trials were run on an EVGA 980ti Classified, 6GB DDR5 card. I feel like I may be missing the fun... --scryptr I hope you aren't using tpruvot.donate as the user if you are trying to see the hashrate on your account |
|
|
|
|
Show Posts
