EricJ2190
|
|
July 17, 2011, 12:04:40 AM |
|
So if I run bitcoind in testnet mode and it downloads the block chain, and then I switch to the live chain, what happens? What do I need to delete/reset/watch out for?
And vice versa - what if I've already downloaded the live block chain and switch to testnet mode.
Bitcoin uses a different default location for the testnet blockchain and wallet, so you can switch between networks freely.
|
|
|
|
Furyan
|
|
July 17, 2011, 01:58:56 AM |
|
So if I run bitcoind in testnet mode and it downloads the block chain, and then I switch to the live chain, what happens? What do I need to delete/reset/watch out for?
And vice versa - what if I've already downloaded the live block chain and switch to testnet mode.
Bitcoin uses a different default location for the testnet blockchain and wallet, so you can switch between networks freely. Awesome, thanks. Pool's all set up... testing now. Only took one day. Not bad.
|
|
|
|
Furyan
|
|
July 17, 2011, 03:09:46 AM |
|
Hmm.. odd but testnet won't work for me: ./bitcoind -daemon -testnet -rpcuser=hungry -rpcpassword=forfood -rpcport=8332 results in the following log: Bitcoin version 0.3.25-beta Default data directory /home/randomuser/.bitcoin Bound to port 18333 Loading addresses... dbenv.open strLogDir=/home/randomuser/.bitcoin/testnet/database strErrorFile=/home/randomuser/.bitcoin/testnet/db.log Loaded 0 addresses addresses 28ms Loading block index... LoadBlockIndex(): hashBestChain=00000007199508e34a9f height=0 block index 0ms Loading wallet... nFileVersion = 32500 fGenerateBitcoins = 0 nTransactionFee = 0 fMinimizeToTray = 0 fMinimizeOnClose = 0 fUseProxy = 0 addrProxy = 127.0.0.1:9050 wallet 44ms Done loading mapBlockIndex.size() = 1 nBestHeight = 0 setKeyPool.size() = 101 mapPubKeys.size() = 102 mapWallet.size() = 0 mapAddressBook.size() = 1 0 addresses found from DNS seeds ThreadRPCServer started sending: version (85 bytes) pv4 eth0: MYSERVERIP addrLocalHost = MYSERVERIP:18333 ThreadSocketHandler started ThreadIRCSeed started ThreadOpenConnections started ThreadMessageHandler started connect() failed after select(): No route to host IRC connect failed IRC waiting 71 seconds to reconnect ThreadRPCServer method=getinfo keypool reserve 2 keypool return 2 at which point bitcoind simply hangs and no blocks are ever downloaded. The sticky part appears to be the inability to connect to MYSERVERIP:18333. I've just replace MYSERVERIP there. No, that doesn't show up as 127.0.0.1 or localhost. What is going on here?
|
|
|
|
error
|
|
July 17, 2011, 03:38:12 AM |
|
Hmm.. odd but testnet won't work for me: ./bitcoind -daemon -testnet -rpcuser=hungry -rpcpassword=forfood -rpcport=8332 results in the following log: Bitcoin version 0.3.25-beta Default data directory /home/randomuser/.bitcoin Bound to port 18333 Loading addresses... dbenv.open strLogDir=/home/randomuser/.bitcoin/testnet/database strErrorFile=/home/randomuser/.bitcoin/testnet/db.log Loaded 0 addresses addresses 28ms Loading block index... LoadBlockIndex(): hashBestChain=00000007199508e34a9f height=0 block index 0ms Loading wallet... nFileVersion = 32500 fGenerateBitcoins = 0 nTransactionFee = 0 fMinimizeToTray = 0 fMinimizeOnClose = 0 fUseProxy = 0 addrProxy = 127.0.0.1:9050 wallet 44ms Done loading mapBlockIndex.size() = 1 nBestHeight = 0 setKeyPool.size() = 101 mapPubKeys.size() = 102 mapWallet.size() = 0 mapAddressBook.size() = 1 0 addresses found from DNS seeds ThreadRPCServer started sending: version (85 bytes) pv4 eth0: MYSERVERIP addrLocalHost = MYSERVERIP:18333 ThreadSocketHandler started ThreadIRCSeed started ThreadOpenConnections started ThreadMessageHandler started connect() failed after select(): No route to host IRC connect failed IRC waiting 71 seconds to reconnect ThreadRPCServer method=getinfo keypool reserve 2 keypool return 2 at which point bitcoind simply hangs and no blocks are ever downloaded. The sticky part appears to be the inability to connect to MYSERVERIP:18333. I've just replace MYSERVERIP there. No, that doesn't show up as 127.0.0.1 or localhost. What is going on here? The important part being: connect() failed after select(): No route to host So either your network is down, or something is blocking your connection to IRC.
|
3KzNGwzRZ6SimWuFAgh4TnXzHpruHMZmV8
|
|
|
etotheipi
Legendary
Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
|
July 17, 2011, 04:18:35 AM Last edit: July 17, 2011, 02:57:58 PM by etotheipi |
|
EDIT: Okay I didn't realize this thread was started a year ago... I thought Gavin was proposing a NEW test network, a third one on top of the production and test networks already there. Please ignore this message.
As someone interested in developing a new client soon, can you tell me what is the difference between this new network, and the previous test-network? I mean, I thought that's what the test network was for... right?
In other words, what are the use cases for the two networks? -Eto
|
|
|
|
Furyan
|
|
July 17, 2011, 10:54:01 AM |
|
The important part being:
connect() failed after select(): No route to host
So either your network is down, or something is blocking your connection to IRC.
I checked the log and the IRC connection fails even for the live connection. However, the key part actually seems to be this: 0 addresses found from DNS seeds For the live connection, this list is not empty (it has 48 addresses). If I operate on the assumption that the live connection was NEVER able to connect to IRC, then it got that seed list from somewhere.
|
|
|
|
gim
Member
Offline
Activity: 90
Merit: 10
|
|
July 17, 2011, 11:34:39 AM |
|
0 addresses found from DNS seeds For the live connection, this list is not empty (it has 48 addresses). If I operate on the assumption that the live connection was NEVER able to connect to IRC, then it got that seed list from somewhere. There is no DNS seeding available for the testnet work. Current options are IRC connection or using static --addnodes.
|
|
|
|
Furyan
|
|
July 17, 2011, 11:35:26 AM |
|
0 addresses found from DNS seeds For the live connection, this list is not empty (it has 48 addresses). If I operate on the assumption that the live connection was NEVER able to connect to IRC, then it got that seed list from somewhere. There is no DNS seeding available for the testnet work. Current options are IRC connection or using static --addnodes. Fantastic, that's what I was missing, thanks!
|
|
|
|
haydent
|
|
July 21, 2011, 12:40:56 PM |
|
ive had my client in testnet mode for some time and it says 14 connections but the initial 1000 blocks hasn't changed...
does it normally take ages at moment ??
|
2x Gigabyte 6950 OC @ 920/450 w/ ati tray tools (1 shader modded) - 760Mhs on ozco.in 0% fee aus pool btc: 1HS5Brzcsh7XkJn566XYbvfpa2JuBRBdss
|
|
|
haydent
|
|
July 21, 2011, 12:43:07 PM |
|
restarting it worked, its away now
|
2x Gigabyte 6950 OC @ 920/450 w/ ati tray tools (1 shader modded) - 760Mhs on ozco.in 0% fee aus pool btc: 1HS5Brzcsh7XkJn566XYbvfpa2JuBRBdss
|
|
|
piotr_n
Legendary
Offline
Activity: 2055
Merit: 1359
aka tonikt
|
|
July 21, 2011, 02:16:15 PM |
|
testnet seems to be pretty useless ATM because it doesn't introduce new blocks with a reasonable intervals. you want to test something and you have no idea how long you will need to wait for a new block.
|
Check out gocoin - my original project of full bitcoin node & cold wallet written in Go.PGP fingerprint: AB9E A551 E262 A87A 13BB 9059 1BE7 B545 CDF3 FD0E
|
|
|
|