EDIT: Caveat emptor on Ubuntu distributions from 14.10 and forward - init was chosen over upstart and is being phased in the future. I don't know when that will be done nor what impact it will have on upstart scripts.
Extract from the page RentFree refers to; note that it assumes that you have created a user called bitcoinuser for the sake of security:
After having installed Bitcoin core on your machine, run the following command to start synchronising the testnet blockchain
bitcoind -testnet -daemon
The synchronisation starts as a daemon and runs in the background, you can issue the following the command to see the progress
To access the command line apis , just add ...
copy the code below and paste (right click if you use putty) to the script.
while true ; do
echo "Press enter to break loop. Script will loop every 3 seconds"
echo "script by Nixsy 18th august 2013"
echo "If loop freezes press CTRL+C"
echo -e " \033[31mdownloaded\e[0m/\...
There's an upstart script for Ubuntu in the Bitcoin Core source tree. Using that is the most correct way.
However, I just login as the user account I want to run Bitcoin Core daemon, start a terminal (if I'm in the GUI), and run the following command to edit my crontab:
Then I add the following line:
@reboot bitcoind -daemon
Save the file ...
You can run the listtransaction JSON output through this little python script (save it as jsonTOCSV.py). That will produce csv (comma separated value) output that Excel or Google Spreadsheets can import, both of which can sort by columns (if I recall correctly).
bitcoind listtransactions | jsonTOCSV.py > transactions.csv
Once you've installed bitcoind, you should create a configuration file (stored in ~/.bitcoin/bitcoin.conf) containing at least an RPC username and password, and then you just run bitcoind to start the server.
Wolciph over on the Bitcoin forums wrote a bash script specifically for 11.04. You haven't posted your specific build errors, but I'm guessing that the problem is with the wxWidgets lib and you'll probably have less issues when the main Bitcoin client eventually moves over to Qt (which I believe is in the works, correct me if I'm wrong). In case the link to ...
Edited answer after Tom van der Woerdt's comment about using an untrusted repo
sudo apt-get update
sudo apt-get install -y git-core build-essential libssl-dev libboost-all-dev libdb5.1-dev libdb5.1++-dev libgtk2.0-dev
git clone https://github.com/bitcoin/bitcoin.git
make -f makefile.unix ...
The first two lines are just warnings that can be ignored. But the error is a known issue caused by Bitcoin's use of a deprecated API that was removed in your version of Boost. The fix is to modify src/ui.cpp around line 1809 as follows:
On Linux, the Bitcoin client data is kept in the .bitcoin directory in your home directory. Go to ~/.bitcoin/ and you'll see the files in there. You may need to toggle Show Hidden Files in your file manager in order to see the directory.
If you remove blkindex.dat, the client will have to redownload the blockchain. I just tested this locally by moving my ...
Version 0.6.0 introduced more strict validity checks on the keys when loading a wallet, to prevent silent further corruption. It seems like you have a wallet where one or more keys are corrupted (the private and public one don't match, for example). You can try moving the funds away using an older version, but there is a chance that will fail.
I intend to ...
You can use logrotate.
Create a file named bitcoin-debug in /etc/logrotate.d.
This is the contents:
Replace /home/bitcoin/.bitcoin/debug.log with the actual path to ...
.exe files are for windows only. Linux systems do not use the same file extension or file type as windows. I assume you just want to create a Linux binary that can be used on all systems without installing all dependencies. To do that, you can use Bitcoin Core's depends system. Instructions are here: https://github.com/bitcoin/bitcoin/tree/master/depends.
Also, if you want to just run bitcoind (without ./bitcoind), add it to your executable path:
As Andrew mentioned, first be sure to chmod +x bitcoind in your src directory.
Still in the src directory, run pwd to get the full path (for example /home/alex/src)
Add it to your .profile with echo "export PATH=$PATH:/home/alex/src" >> ~/.profile
Now you can ...
This happens with many Ubuntu Apps. The simplest solution is to tap Alt any type the name of the menu item you wish to find.
Alternatively, hit Ctrl-Alt-F2, log in, type DISPLAY=:0.0 unity --replace hit Enter, and then do Ctrl-Alt-F7. The menu bars and the windowing system will reload.
The wildcard syntax is not supported anymore. Instead of 192.168.*.*, use 192.168.0.0/16. Instead of 192.168.1.*, use 192.168.1.0/24.
As an additional debugging step, try running netstat -antlp | grep 8332. If that produces output like the following, that means that it is bound to the port.
tcp 0 0 0.0.0.0:8332 0.0.0.0:...
Answers to your respective questions:
Since 0.12, bitcoind supports cookie file authentication. This means that on startup of bitcoind, a file with a random key in it is created. Anyone who can present the contents of that file to the running bitcoind is allowed access. Since bitcoin-cli runs locally and as the same user, it can read this file and do so.
I suggest to use one of the updated cpuminer versions which support more than one algorithm. This way you are also set up to mine different coins which use other PoW functions. The most versatile one is tpruvot's fork:cpuminer-multi. For me this one worked out of the box on a recent Ubuntu 14.04 installation.
The syntax is similar to all other cpuminer ...
I just installed bitcoind on an RPi and wanted to do this exact thing. Thought I'd post what worked for me:
$ bitcoin-cli getblockcount
Block height is 366678 at the time of this post...long way to go
If you're mining in a pool, bitcoind doesn't even have anything to do with the system. It doesn't need to be running, it doesn't even need to exist on your hard drive. The remote pool does that for you.
I would highly recommend using Ubuntu Server for this, as long as you know what you are doing without a GUI. Not having a GUI at all means smaller OS size and much less OS tasks. This translates into more power savings. If you are using graphics cards, a non-GUI OS will improve your mining performance. If using an ASIC/etc. you probably will not see ...
In Bitcoin Core 0.11 pruning is experimental, and incompatible with the wallet.
So turning on the prune= option automatically disables the wallet function.
In 0.12 the wallet will work with pruning (though you obviously won't be able to rescan past the pruning cutoff).
Try starting with the -reindex command-line flag. That will rebuild the database on disk (as it seems corrupted), without redownloading the blocks you already have.
It's strange that wiping your datadir didn't help though.