Bitcoin Forum
May 12, 2024, 06:54:16 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BTB] The BitBar Information Thread on: January 12, 2016, 08:26:53 PM
Having a few problem with BitBar on a nomp pool, when a block is found the wallet finds it and records the block perfectly but nomp doesnt record it in redis and so payments are just being kept in the configured wallet for the pool. Other coins work ok.

Spidersbox (need help again)  Smiley i remember you saying you had nomp setup privately, did you have to do anything to get it working properly?
2  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BTB] The BitBar Information Thread on: December 23, 2015, 10:34:57 PM

Decided to bin Centos, its to much trouble getting the OS to work with a wallet on any coin.

Took your advice and re-imaged to Ubuntu, all working very quick and have the pool configured just looking at configuration before it goes public.

Difficulty has significantly increased :-( I'll post back when I've got a public solution available.

Now that you are on Ubuntu, I can help -- wait, you don't need help now   Cheesy

haha --yes
3  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BTB] The BitBar Information Thread on: December 23, 2015, 09:09:56 PM
Thanks for helping here.

Running Centos 6.7 and i used this script to install but modified it for Bitbar: https://github.com/mikeminneman/dogecoind-centos

Ok, so my rpc password does match in both the pool config and bitbar.conf files. I think that is working because the debug log in Bitbar shows the rpc request from node "gettransactions".

Heres my Bitbar wallet "getinfo" - (I started a new wallet so its just downloading again)

  "version" : "v0.4.3.004-5-g903edf9-beta",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 83500,
    "moneysupply" : 14044.44104100,
    "connections" : 1,
    "proxy" : "",
    "ip" : "X.X.X.X",
    "difficulty" : 41.30374091,
    "testnet" : false,
    "keypoololdest" : 1450404332,
    "keypoolsize" : 101,
    "paytxfee" : 0.00010000,
    "errors" : ""


Heres the error in NOMP:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  read_some: End of file

2015-12-18 15:45:46 [Payments]  [bitbar] Check finished - daemon rpc error with batch gettransactions {"type":"request error","message":"read ECONNRESET"}
2015-12-18 15:45:46 [Payments]  [bitbar] Finished interval - time spent: 995ms total, 3ms redis, 987ms daemon RPC
2015-12-18 15:45:46 [Pool]      [bitbar] (Thread 1) Could not start pool, error with init batch RPC call: {"type":"offline","message":"connect ECONNREFUSED"}


# bitbard getbalance
0.00000000
# bitbard gettransactions
terminate called after throwing an instance of 'std::vector<json_spirit::Pair_impl<json_spirit::Config_vector<std::string> >, std::allocator<json_spirit::Pair_impl<json_spirit::Config_vector<std::string> > > >'
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  read_some: End of file
Aborted (core dumped)

So it looks like an issue with the wallet when the "gettransactions" call is issued Im guessing there aren't any due to it being a new install. Any thing jump out at you? Maybe I'm missing something obvious....

the bitbard getinfo seemed to work well.
Do you get any errors if you do:
bitbard listtransactions     -or-
bitbard listaccounts

If those work, then I think the wallet database is working ok.

I have a couple of thoughts:
1) Are you running a firewall, blocking any ports??


         (I am unfamiliar with Centros, so this might not work)

2) compile bitbar from source using:
sudo apt-get install build-essential
sudo apt-get install libssl-dev
sudo apt-get install libdb4.8-dev        *this may give you trouble
sudo apt-get install libdb4.8++-dev
sudo apt-get install libboost-all-dev

make -f makefile.unix USE_UPNP=-

- why:
Boost is complaining a lot, and interacts with some of the other dependencies. I'd like to make sure you are using the same libraries.
The boost errors have to do with the RPC calls. (rpc problems keep popping up. humm)

3) you might not like this one:
switch to Ubuntu server (or desktop) It is what I am using and could provide links to step by step instructions on how to set up Ubuntu and NOMP.
guess I could add a link anyway:
scratch that - the web site has been down for a while. I will just have to add it to Bitbar.co when I have time..

just had a thought -
I have to use sudo to start my nomp - it would give errors (but I don't remember what they are) if I don't use sudo:

sudo node init.js     <-- try this first

Let me know how it goes



Decided to bin Centos, its to much trouble getting the OS to work with a wallet on any coin.

Took your advice and re-imaged to Ubuntu, all working very quick and have the pool configured just looking at configuration before it goes public.

Difficulty has significantly increased :-( I'll post back when I've got a public solution available.
4  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BTB] The BitBar Information Thread on: December 18, 2015, 04:01:20 PM
same error even with your git update! Must be me? The NOMP application issues a gettransactions call at start up which my bitbar daemon terminates afterwards :-(
well - let's back up a little. without starting nomp, what happens when you do "bitbard getinfo" ??

Guess I should ask how familiar you are with nomp, wallets, and linix in general.

Thanks for helping here.

Running Centos 6.7 and i used this script to install but modified it for Bitbar: https://github.com/mikeminneman/dogecoind-centos

Ok, so my rpc password does match in both the pool config and bitbar.conf files. I think that is working because the debug log in Bitbar shows the rpc request from node "gettransactions".

Heres my Bitbar wallet "getinfo" - (I started a new wallet so its just downloading again)

  "version" : "v0.4.3.004-5-g903edf9-beta",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 83500,
    "moneysupply" : 14044.44104100,
    "connections" : 1,
    "proxy" : "",
    "ip" : "X.X.X.X",
    "difficulty" : 41.30374091,
    "testnet" : false,
    "keypoololdest" : 1450404332,
    "keypoolsize" : 101,
    "paytxfee" : 0.00010000,
    "errors" : ""


Heres the error in NOMP:

2015-12-18 15:45:44 [POSIX]     [Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2015-12-18 15:45:44 [Master]    [CLI] CLI listening on port 17117
2015-12-18 15:45:44 [Master]    [PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  read_some: End of file
2015-12-18 15:45:44 [Payments]  [bitbar] Payment processing setup to run every 120 second(s) with daemon (bitbar@127.0.0.1:9344) and redis (127.0.0.1:6379)
2015-12-18 15:45:45 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2015-12-18 15:45:45 [Pool]      [bitbar] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
2015-12-18 15:45:46 [Payments]  [bitbar] Check finished - daemon rpc error with batch gettransactions {"type":"request error","message":"read ECONNRESET"}
2015-12-18 15:45:46 [Payments]  [bitbar] Finished interval - time spent: 995ms total, 3ms redis, 987ms daemon RPC
2015-12-18 15:45:46 [Pool]      [bitbar] (Thread 1) Could not start pool, error with init batch RPC call: {"type":"offline","message":"connect ECONNREFUSED"}

Here the Bitbar debug log that shows the last entry before it terminated due to the above request from NOMP.

Flushed 5740 addresses to peers.dat  78ms
Flushed 5740 addresses to peers.dat  78ms
ThreadRPCServer method=getinfo
ThreadRPCServer method=validateaddress
ThreadRPCServer method=getbalance

Heres the error if i run from the terminal as you can see "getbalance" returns info but "gettransactions" kills it.

# bitbard getbalance
0.00000000
# bitbard gettransactions
terminate called after throwing an instance of 'std::vector<json_spirit::Pair_impl<json_spirit::Config_vector<std::string> >, std::allocator<json_spirit::Pair_impl<json_spirit::Config_vector<std::string> > > >'
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  read_some: End of file
Aborted (core dumped)

So it looks like an issue with the wallet when the "gettransactions" call is issued Im guessing there aren't any due to it being a new install. Any thing jump out at you? Maybe I'm missing something obvious....
5  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BTB] The BitBar Information Thread on: December 18, 2015, 12:57:55 AM
same error even with your git update! Must be me? The NOMP application issues a gettransactions call at start up which my bitbar daemon terminates afterwards :-(
6  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BTB] The BitBar Information Thread on: December 17, 2015, 11:24:20 PM
My wallet is syncing now, but I get the feeling my coins are going to be unconfirmed. The million dollar question is have I lost them or not? Huh

The safest answer I can give you is to backup the addresses you received coins to, perhaps a paper wallet or of the wallet.dat file and come back to it in the future after everyone is on the same chain.

I am on the longest chain, connected to the oldest node but things are not certain even for that.

It sucks, but thus isn't the first time anyone has lost due to split chains.

I myself have been a victim of pools going rouge in the past (anyone remember diggers pool?)

until there is more infrastructure surrounding bitbar all we can do is try to help eachother out by spreading information.

Speaking of, I am excited to share some information concerning possible future developments....

more to come



Should I take the wallet offline the one with the unconfirmed coins? Just keep it as back up?


When I messing with my wallets, I close the wallet if it is running, I copy and paste the Bitbar directory - that way everything is backed up - including the chain you were on.
Once that is done, you can mess with whatever you want, because if you screw it up, you can just delete the Bitbar directory, rename 'copy of Bitbar' back to bitbar, and you are back to where you started.

If you want to start fresh (once you have a backup copy) you can delete everything in the Bitbar folder except the wallet.dat, and bitbar.conf files, start up the bitbar-qt.exe and it will start syncing the chain.


To start out, you can do as Luke suggested and put:
connect=68.191.93.33
in your bitbar.conf file.

After you are caught  up, change the 'connect=' to 'addnode=' and add some of the nodes listed at http://btb.cryptocoinexplorer.com/peerinfo

also remember to add:
irc=0
listen=1

Having a few problems setting up the Mullick wallet in linux, every time i sync to the block chain using the afore mentioned process, i then want to initatie my own NOMP but when the application starts i get this error:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  read_some: End of file

followed by:

Check finished - daemon rpc error with batch gettransactions {"type":"request error","message":"read ECONNRESET"}

I have nailed this down to the wallet, when i run the command "gettranactions" against bitbard the wallet produces the same errors which terminates the daemon. Could anyone advise maybe Spidersbox on how they configure their daemon please?





 i issue certain commands to the daemon i receive a termination error.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!