Geth diskspace outside of datadir - Ethereum Stack Exchange

[DEVELOPMENT] Bitcoind IPV4 testnet port (18332) is failing to bind

[SOLVED] Thanks for everyone that have helped!

Hello everyone, this is a development problem that I'm currently having. Since the BTC Development sub is kind of inactive and I couldn't find any rule contraty to posting about BTC Development, I'll try my luck in here as I'm hopeless already. I've posted on BTC Stack Exchange but no answers also. Please, don't get me wrong, I'm trying to solve this problem for many days now, I've looked up everywhere for this.
I'm new to Bitcoin development and I'm currently having difficulties trying to make RPC calls from a Docker Container to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem may be with Firewall or closed ports, but I also do not know much about Network settings.
I'm using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I'm sure the container is functional and is not the problem.
So here's what happening: when I run bitcoind in root user (but normal also won't work) in my SSH server, the IPV4 testnet port seems to be not opened. This message goes up when I run bitcoind:
Binding RPC on address port 18332 failed.
Here's what my bitcoin.conf looks like (I want to use testnet in here). I'm using Bitcoin-Core "subversion": "Satoshi:0.17.1".
server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332 # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx # My machine's IP # rpcallowip=172.19.x.x/xx # Docker's NBOBTC container IP # rpcallowip= # Allowing all IP datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log 
Here's what appears in debug.log right after I run Bitcoind:
2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z block index 19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in 123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat 36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat 29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start 
After all that appears above, there are just "UpdateTip", "Requesting block", "received block" and "getdata" messages. (so the P2P port, 18333, works).

And here is when I netstat:

sudo netstat -nap|grep bitcoin|grep LISTEN
tcp 0 0* LISTEN 31185/bitcoind tcp6 0 0 :::18332 :::* LISTEN 31185/bitcoind tcp6 0 0 :::18333 :::* LISTEN 31185/bitcoind 
Thank you in advance!

PS: A few days ago I could make it work when running bitcoind with root user, but now even that won't solve the problem.
submitted by VicPietro to Bitcoin [link] [comments]

Bitcoin ABC users who didn't upgrade before Nov 13: upgrade to 0.16.1

This is just a heads up for ABC node operators who have not upgraded to the 0.16.x version.
If you haven't noticed by now, you will not be on the upgraded chain.
Also, some miner has decided to mine an alternate, non-upgraded chain that follows the old EDA.
We don't know exactly who, but there's a tweet from Alistair Milne (which is incorrect on the vulnerability aspect btw) that associates this with 'Bitcoin Clashic' - a mocking fork whose purpose in life seems to be to act as fodder for social media trolling campaigns against Bitcoin Cash.
Why does this matter?
Because if you don't upgrade, your node would be at risk of eventually following their chain, once it accumulates enough work to supercede your chain which is currently stuck at the pre-fork block.
As the 'Clashic' (or whatever they want to call themselves) chain has not yet reached the same amount of work as the current Bitcoin Cash chain, your node would not have followed the Clashic chain yet.
Please upgrade swiftly, otherwise you will later need to do more steps to rid your datadir of Clashic blocks.
Your coins are safe nevertheless, but since Clashic did not implement its own replay protection to distinguish it from the Bitcoin Cash network, transactions made on non-upgraded nodes could end up being replayed to the active Cash chain (this is probably not bad if you were thinking that you are transacting on Cash chain anyway).
Update download link:
P.S. Anyone can choose an old block in the blockchain to start a fork. This is not really a threat as long as they have minority of hashpower compared to the main Cash chain, because what matters for selection of the active chain is the amount of accumulated work - not the height of the chain.
Exchanges should just demand that a fork with minority hashpower implement a replay protection to make it impossible to replay onto the majority chain. This is what they have been demanding up to now.
submitted by btcfork to btc [link] [comments]

launch two masternode esbc on one vps WARNING!!! VERY BAD ENGLISH!!! How to create wallet and fast sync network Dimecoin  IT Vlogs Запуск 2 masternode esbc на одном vps - YouTube metamask tutorialUse metamask ethereum walletHow to import your MyEtherWallet account into Metamas

Stack Exchange Network. Stack Exchange network consists of 177 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Visit Stack Exchange. Loading… 0 +0; Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings ... Wissenswertes über Bitcoins Unser Bitcoin Chart zeigt Ihnen den aktuellen Bitcoin Kurs in Euro (Kürzel: BTC und XBT) sowie die Bitcoin Kursentwicklung (Bitcoincharts).Wenn Sie Bitcoins kaufen möchten, können Sie sich hier anmelden.In unseren FAQs und in unserem Tutorial "Mein erster Bitcoin" erfahren Sie, wie Sie Bitcoins verkaufen oder kaufen können. I tried asking this in the bitcoincore sub yesterday, but it only has a handful of members and got no answers, so i now try here. When bitcoin-qt is first started, it asks for the location of datadir. If it is set to a custom location, it remembers it on subsequent launches. Where is this location stored, as no bitcoin.conf... Stack Exchange network consists of 176 Q&A communities including Stack Overflow, ... geth --datadir "<mounted large drive>" --fast --cache 1024 --rpc --rpcaddr <publicip> --rpcport 8545. The chaindata folder in the mounted drive is increasing in size (7GB after a few hours), so I am confident that -datadir is working... But for some reason my home drive is filling up at about the same pace. I ... Change Bitcoin Datadir, Asked change bitcoin datadir 4 mins ago. crypto yugopolis 2018. Geld Für App Store Verdienen!

[index] [6056] [45859] [44397] [36179] [14854] [21597] [25122] [7445] [31190] [42633]

launch two masternode esbc on one vps WARNING!!! VERY BAD ENGLISH!!!

Today I explain how to import metamask account from ethereum wallet account . when we create ethereum wallet account then the folder file generated in mac id to import metamask account.. this is ... How to create wallet and fast sync network Dimecoin Today, I will guide you How to create a wallet of dimecoin. Excuse me for not being able to use the mic to speak to guide people. 1. We first ... esbcoind -datadir=.esbcoin2 -daemon - laucnh wallet daemon of second masternode esbcoin-cli -datadir=.esbcoin2 masternode status - check status second masternode Website: Список команд: cp -p -r .esbcoin .esbcoin2 - копировать папку блокчейна, esbcoin2 можно заменить на любое другое название ...