Topic: Bitcoin-qt will not open in testnet mode (Read 881 times)

Hi All,

I am not new to programming, have been using Bitcoin for 6 months, and developing Bitcoin software since 4 months ago.
Got into this forum a few days ago, so, well, must post in newbies.

Have been running Bitcoin-qt on Ubuntu since february, and running it in testnet since one week or so.
Yesterday it stopped working with these messages:

1. a pop-up windows reading: An error occurred while setting up the RPC port 18332 for listening on IPv4: bind: Address already in use

2. a line in terminal reading: "Segmentation fault (core dumped)"

Any help will be greatly appreciated.
Thanks in advance.

Follows my Bitcoin.conf


##########################################################################
# 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
 
# 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
 
# 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=bitcoinrpc
rpcpassword=7GtL8Y9vaBooNXxgiRswWP1kRqgkCXGSaJj3GJwSTHF1
 
# 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=10.1.1.34
#rpcallowip=192.168.1.*
 
# Listen for RPC connections on this TCP port:
host=127.0.0.1
port=18332
 
# 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=1

# 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

##########################################################################
# End of configuration
#########################################################################