Bitcoin Forum
December 07, 2016, 06:29:56 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: How can I tell if Bitcoind is working?  (Read 1378 times)
NothinG
Hero Member
*****
Offline Offline

Activity: 560



View Profile
August 06, 2011, 05:38:04 PM
 #1



It just sits there.
I'm trying to get a script to talk to via WAN but wont return any data.

I've made sure my firewalls are open (tcp/udp 8332 & 8333).

How can I tell where the script stops responding?

Also, the site error
Code:
Fatal error: Uncaught exception 'Exception' with message 'Incorrect response id (request id: 1, response id: )' in /home***/public_html/bitcoin/classes/jsonRPCClient.php:152 Stack trace: #0 /home/***/public_html/bitcoin/html/main.php(50): jsonRPCClient->__call('getblockcount', Array) #1 /home/***/public_html/bitcoin/html/main.php(50): jsonRPCClient->getblockcount() #2 /home/***/public_html/bitcoin/index.php(40): include('/home/***/...') #3 {main} thrown in /home/***/public_html/bitcoin/classes/jsonRPCClient.php on line 152

1481135396
Hero Member
*
Offline Offline

Posts: 1481135396

View Profile Personal Message (Offline)

Ignore
1481135396
Reply with quote  #2

1481135396
Report to moderator
1481135396
Hero Member
*
Offline Offline

Posts: 1481135396

View Profile Personal Message (Offline)

Ignore
1481135396
Reply with quote  #2

1481135396
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481135396
Hero Member
*
Offline Offline

Posts: 1481135396

View Profile Personal Message (Offline)

Ignore
1481135396
Reply with quote  #2

1481135396
Report to moderator
1481135396
Hero Member
*
Offline Offline

Posts: 1481135396

View Profile Personal Message (Offline)

Ignore
1481135396
Reply with quote  #2

1481135396
Report to moderator
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
August 06, 2011, 05:40:16 PM
 #2

Open another cmd and run 'bitcoind help'

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
NothinG
Hero Member
*****
Offline Offline

Activity: 560



View Profile
August 06, 2011, 05:42:13 PM
 #3

Open another cmd and run 'bitcoind help'
Looks like it's running. Thanks Smiley

Now...to figure out why it wont connect to the script.

BCEmporium
Legendary
*
Offline Offline

Activity: 938



View Profile
August 06, 2011, 05:43:56 PM
 #4

Had you create a bitcoin.conf file within your data dir?
Also make sure there's a line server=1 and rpcallowip=0.0.0.0 at bitcoin.conf
Remember remember the 5th of November
Legendary
*
Offline Offline

Activity: 1526

Reverse engineer from time to time


View Profile
August 06, 2011, 05:45:26 PM
 #5

Had you create a bitcoin.conf file within your data dir?
Also make sure there's a line server=1 and rpcallowip=0.0.0.0 at bitcoin.conf

Why do you want him to enable server mode. That should only be enabled if he plans to solo mine.

BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
NothinG
Hero Member
*****
Offline Offline

Activity: 560



View Profile
August 06, 2011, 05:46:15 PM
 #6

Had you create a bitcoin.conf file within your data dir?
Also make sure there's a line server=1 and rpcallowip=0.0.0.0 at bitcoin.conf


Quote
# bitcoin.conf configuration file. Lines beginning with # are comments.
 
 
 # Network-related settings:
 
 # Run on the test network instead of the real bitcoin network.
 #testnet=1
 
 # 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=1
 
 # Maximum number of inbound+outbound connections.
 #maxconnections=
 
 
 # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
 
 # server=1 tells Bitcoin to accept JSON-RPC commands.
 server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=--hidden--
 rpcpassword=--hidden--
 
 # 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=173.237.234.100
 
 # 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

BCEmporium
Legendary
*
Offline Offline

Activity: 938



View Profile
August 06, 2011, 05:49:53 PM
 #7

try changing this:

rpcallowip=173.237.234.100

to this:

rpcallowip=*

(it opens your bitcoind to the world [provinding the correct user/pass], so use it with a wallet.dat empty or nearly empty)
NothinG
Hero Member
*****
Offline Offline

Activity: 560



View Profile
August 06, 2011, 05:52:13 PM
 #8

HORRIBLE fail on my part xD
I forgot to check the cPanel firewall.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!