Title: Little Help also new :3
Post by: killzon32 on July 28, 2012, 09:58:41 AM
Hi first post for bitcointalk :D I been messing around with bitcoin for a while and decided to make a post I need a little help understanding bitcoind my brain cant seem to put everything in order and what I am suppose to do.
I downloaded python spent hours figuring out how to install modules and managed to do that... pretty sure ;p Then I can't seem to figure out how to get bitcoind working. Whenever I put conf file into right place and start it, its blank and crashes when I exit. When I leave the hashtags it says I should use recommended passwords...
I spent sometime looking in bitcoin forum spent at least 3 hours trying to figure this out I am no expert with programming at all and I have hit a wall and had to make a post:/.
If anyone could help me with the steps or have a tutorial that be great. I can't seem to find anything about bitcoind.
Title: Re: Little Help also new :3
Post by: SRoulette on July 28, 2012, 11:12:31 AM
paste your config file please.
Title: Re: Little Help also new :3
Post by: killzon32 on July 28, 2012, 11:26:07 AM
# bitcoin.conf configuration file. Lines beginning with # are comments. # Network-related settings: # Run on the test network instead of the real bitcoin network. #testnet=0 # Connect via a socks4 proxy #proxy=127.0.0.1:9050 ############################################################## ## Quick Primer on addnode vs connect ## ## Let's say for instance you use addnode=4.2.2.4 ## ## addnode will connect you to and tell you about the ## ## nodes connected to 4.2.2.4. In addition it will tell ## ## the other nodes connected to it that you exist so ## ## they can connect to you. ## ## connect will not do the above when you 'connect' to it. ## ## It will *only* connect you to 4.2.2.4 and no one else.## ## ## ## So if you're behind a firewall, or have other problems ## ## finding nodes, add some using 'addnode'. ## ## ## ## If you want to stay private, use 'connect' to only ## ## connect to "trusted" nodes. ## ## ## ## If you run multiple nodes on a LAN, there's no need for ## ## all of them to open lots of connections. Instead ## ## 'connect' them all to one node that is port forwarded ## ## and has lots of connections. ## ## Thanks goes to [Noodle] on Freenode. ## ############################################################## # Use as many addnode= settings as you like to connect to specific peers #addnode=69.164.218.197 #addnode=10.0.0.2:8333 # ... or use as many connect= settings as you like to connect ONLY # to specific peers: #connect=69.164.218.197 #connect=10.0.0.1:8333 # Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to # find other peers. #noirc=0 # Maximum number of inbound+outbound connections. #maxconnections= # JSON-RPC options (for controlling a running Bitcoin/bitcoind process) # server=1 tells Bitcoin-QT to accept JSON-RPC commands. server=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser= rpcpassword= # How many seconds bitcoin will wait for a complete RPC HTTP request. # after the HTTP connection is established. #rpctimeout=30 # By default, only RPC connections from localhost are allowed. Specify # as many rpcallowip= settings as you like to allow connections from # other hosts (and you may use * as a wildcard character): #rpcallowip=127.0.0.1 #rpcallowip=192.168.2.3* # Listen for RPC connections on this TCP port: rpcport=8332 # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind # running on another host using this option: rpcconnect=127.0.0.1 # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate # with Bitcoin -server or bitcoind #rpcssl=1 # OpenSSL settings used when rpcssl=1 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH #rpcsslcertificatechainfile=server.cert #rpcsslprivatekeyfile=server.pem # Miscellaneous options # Set gen=1 to attempt to generate bitcoins #gen=0 # Use SSE instructions to try to generate bitcoins faster. #4way=1 # Pre-generate this many public/private key pairs, so wallet backups will be valid for # both prior transactions and several dozen future transactions. #keypool=100 # Pay an optional transaction fee every time you send bitcoins. Transactions with fees # are more likely than free transactions to be included in generated blocks, so may # be validated sooner. paytxfee=0.00 # Allow direct connections for the 'pay via IP address' feature. #allowreceivebyip=1 # User interface options # Start Bitcoin minimized #min=1 # Minimize to the system tray #minimizetotray=1
Title: Re: Little Help also new :3
Post by: SRoulette on July 28, 2012, 11:29:14 AM
check debug.log in the bitcoin data directory ~/.bitcoin
You may also want to set something for rpcuser and rpcpassword
Title: Re: Little Help also new :3
Post by: killzon32 on July 28, 2012, 11:34:00 AM
I do have a password and user set did not no if thats important to show or not :3
Title: Re: Little Help also new :3
Post by: killzon32 on July 28, 2012, 11:39:37 AM
This might be useful maybe? is this the debug info you want? Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400) Default data directory C:\Users\brendan\AppData\Roaming\Bitcoin Loading addresses... dbenv.open LogDir=C:\Users\brendan\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\brendan\AppData\Roaming\Bitcoin\db.log Loaded 12521 addresses addresses 157ms Loading block index... LoadBlockIndex(): hashBestChain=00000000000008170660 height=191188 Verifying last 2500 blocks at level 1 block index 34394ms Loading wallet... nFileVersion = 60300 wallet 93ms Done loading mapBlockIndex.size() = 191194 nBestHeight = 191188 setKeyPool.size() = 100 mapWallet.size() = 65 mapAddressBook.size() = 4 Bound to port 8333 ThreadRPCServer started addrLocalHost = 192.168.2.3:8333 ThreadSocketHandler started ThreadIRCSeed exiting ThreadDNSAddressSeed started Loading addresses from DNS seeds (could take a while) ThreadMessageHandler started ThreadOpenConnections started ThreadOpenAddedConnections started ThreadOpenAddedConnections exiting GetMyExternalIP() received [67.189.41.174] 67.189.41.174:0 GetMyExternalIP() returned 67.189.41.174 trying connection 109.188.130.74:8333 lastseen=-2.2hrs Added 3 addresses from 0:0:0:0:0:0:0:0: 696 tried, 11826 new Added 1 addresses from 178.18.90.41: 696 tried, 11826 new Added 8 addresses from 173.242.112.53: 696 tried, 11827 new 69 addresses found from DNS seeds ThreadDNSAddressSeed exiting connection timeout trying connection 46.138.157.39:8333 lastseen=-2.8hrs connection timeout trying connection 84.108.105.80:8333 lastseen=-16.9hrs EnvShutdown exception: DbEnv::close: Invalid argument (22)
Title: Re: Little Help also new :3
Post by: SRoulette on July 28, 2012, 12:37:52 PM
EnvShutdown exception: DbEnv::close: Invalid argument (22) here is your error, lets see what google says. https://github.com/bitcoin/bitcoin/issues/1165 unfortunately it looks like an resolved bug, have you tried starting with a clean bitcoin data dir ? remember to backup your wallet.dat
Title: Re: Little Help also new :3
Post by: killzon32 on July 29, 2012, 10:07:04 AM
I tried reinstalling bitcoin but I still get error EnvShutdown exception: DbEnv::close: Invalid argument (22) thats the error when I click the close button of the cmd when I load it.. Should I leave it running for along time maybe? for it to load or something?
Title: Re: Little Help also new :3
Post by: killzon32 on July 30, 2012, 10:34:56 PM
This is confusing me x.x can anyone help me with this problem :/
|