Report bugs at https://github.com/gandrewstone/BitcoinUnlimited/issues or HERE

[theZerg]

Go here: https://github.com/BitcoinUnlimited/BitcoinUnlimited/issues

But if you absolutely cannot post there, please put your bugs in this thread NOT spread all over bitco.in, reddit or the GCBU thread (I won't be able to find them).

Thanks!!!

 

[freetrader]

> But if you absolutely cannot post there, please put your bugs in this thread NOT spread all over bitco.in, reddit or the GCBU thread (I won't be able to find them).

Since this will happen despite best intentions I think we can help if we find such "distributed" bug reports by linking them here and directing their originators to this place and the Github.

 

[lebing]

I tried setting up an unlimited node in the cloud with these instructions: https://www.reddit.com/r/btc/comments/3xwcnl/how_i_stopped_bitching_and_started_my_own/

Here is the script I used:

wget -O-https://gist.githubusercontent.com/snakecharmer1024/922e31196c98675b54b5/raw/02b5e8d2e7296fbb41c3fc28e5b39f192d9cb2c6/bitcoin-unlimited-installer.sh | sudo bash

Errors flew out all over the place and now there seems to be a password required as well.

I got the XT node working just fine but will switch obviously if you manage to figure out what is happening.

Thanks

 

[sickpig]

@lebing

such script attempt to compile BU from the source code. A bazillions of things could go wrong while compiling from source, even if I think that all the output you get on the console is not related to error but simply what the compiler spit on the stout while compiling.

Lastly, the script requires a password because you invoke it using sudo.

If I were you I'll try a simpler way, download BU binary from bitcoinunlimited.info following this instructions (if you are on 32bit platform change commands accordingly):

$> wget http://www.bitcoinunlimited.info/public/downloads/bitcoinUnlimited-0.11.2-linux64.tar.gz
$> tar xf  bitcoinUnlimited-0.11.2-linux64.tar.gz
$> cd  bitcoinUnlimited-0.11.2/bin
$> ./bitcoind -daemon

all the aforementioned cmds do not require root/admin access (so no need to use sudo)

not mandatory:

1) sudo cp bitcoind /usr/bin
2) set RPC password and rcpuser in ~/.bitcoin.conf

point 1) copy the binary in a PATH directory so that you could execute Bitcoin without specifying the full path. point 2) restrict access to the access RPC (remote procedure call) interface.

As last thing: never ever execute random script on your computer using sudo.

It is like giving the keys of your house to the first random stranger you find on the street, i.e. bad things could happen.

 

[lebing]

Thanks SP for the reply. I should reiterate that this was all in cloud.google.com so no harm possible on my computer.

I just tried using your code but it didn't work. It gave me this error:
-bash: $: command not found

 

[sickpig]

@lebing

the $> symbol was just a mere reference to the terminal prompt, sorry if it was confusing.

same commands without symbols (you could cut and paste them without problems)

wget http://www.bitcoinunlimited.info/public/downloads/bitcoinUnlimited-0.11.2-linux64.tar.gz
tar xf bitcoinUnlimited-0.11.2-linux64.tar.gz
cd bitcoinUnlimited-0.11.2/bin
./bitcoind -daemon

 

[lebing]

Getting closer... but here is the authentication error I just got:

Bitcoin server starting lebing@unlimited-y7kl:~/bitcoinUnlimited-0.11.2/bin/bitcoinUnlimited-0.11.2/bin$ Error: To use bitcoind, or the -server option to bitcoin-qt, you must set an rpcpassword in the configuration file:/home/lebing/.bitcoin/bitcoin.confIt is recommended you use the following random password:rpcuser=bitcoinrpcrpcpassword=AM97unzzLkDeUww1Ug8bMZtrXo7HwsBbjsSLwmqDvBr(you do not need to remember this password)The username and password MUST NOT be the same.If the file does not exist, create it with owner-readable-only file permissions.It is also recommended to set alertnotify so you are notified of problems;for example: alertnotify=echo %s | mail -s "Bitcoin Alert" admin@foo.com

 

[sickpig]

Sure I forgot we need to set up RPC credentials. just use this command to set it up. it's one time thing, you don't need to execute it every time.

printf "rpcuser=bitcoirpc\nrpcpassword=$RANDOM$RANDOM$RANDOM\n" >> ~/.bitcoin/bitcoin.conf

now every time you want to execute bitcoind just use

./bitcoind -daemon

to interact with the bitcoin process you have to use the bitcoin-cli binary (it is in the same dir as bitcoind), e.g. this is the command to stop the process:

./bitcoin-cli stop

bitcoind log could be found in ~/.bitcoin/debug.log

 

[lebing]

Ok! It is now working! Thanks SP

 

[BrianM]

I posted another problem here (regarding a crash in the OSX version downloads of Unlimited):
https://github.com/BitcoinUnlimited/BitcoinUnlimited/issues/47

(The URL at the top of this thread doesn't seem to be accurate anymore.)

 

[theZerg]

thanks, I saw it. actually I've got some apple hardware now so plan to make the OSX version actually work in the next release

 

[BrianM]

Thanks. For the Unlimited user-base to achieve their growth goals, it's best to Not post builds that are Untested.
(Or at a minimum, name them "Untested".)

 

[Justaphf]

The link at the top of the thread is not current, as mentioned by @BrianM . The correct link, (as of this posting) is:
https://github.com/BitcoinUnlimited/BitcoinUnlimited/issues

@theZerg could you update the link in post #1 to match the issues link for the current default branch. If my HCI courses taught me anything it's that users want instant gratification, no scrolling! Also, if you or @solex could perma-sticky this post (or a locked post with just the URL so we don't end up with multiple pages). IMO, if there is any type of semi-formal bug/issue reporting procedure for an active project like this, it's paramount to make that procedure clearly and permanently visible to users/guests.
Thanks!

----------------------------------------------------------------------------------------------------------------------

Also, just FYI, already posted on GitHub (Issue #65), added possible single-line issue which may be the cause of:
1. The client's ability to connect to more than the hard coded limit of 8 outgoing nodes by specifying more than the recommended 8 "-addnode" lines in bitcoin.conf
2. A possible reason why users may never be able to achieve the "-maxconnections" specified if they also specify "-addnode" parameters at the command line and/or in bitcoin.conf. In the extreme, but unlikely case, this could possibly prevent all inbound connections.

 

[Peter Tschipper]

@theZerg We should really have a link on our main BitcoinUnlimited web page that points to the issues list. I think users might find it easier to report bugs there...

 

[theZerg]

@Justaphf: done thanks!
@ptschip: good idea, I'll work on it