..that's what I feared too.
It wouldn't need the stated "-server" flag, but a hypothetical "-client" one.
Thanks for confirming!
Ente
Topic: Not able to run bitcoind and GUI at same time (Read 3913 times)
Bitcoind is either a) the RPC server or b) an RPC client.
Bitcoin-Qt is a GUI + optionally the RPC server.
The error you're getting probably means you're already running bitcoind as RPC server, so you can't start Bitcoin-Qt in server mode as well.
Shut bitcoind down (./bitcoind stop), start Bitcoin-Qt with -server, and after that point you can send RPC commands to the GUI.
Bitcoin-Qt is a GUI + optionally the RPC server.
The error you're getting probably means you're already running bitcoind as RPC server, so you can't start Bitcoin-Qt in server mode as well.
Shut bitcoind down (./bitcoind stop), start Bitcoin-Qt with -server, and after that point you can send RPC commands to the GUI.
Aaah, now I get it!
So I was in fact running bitcoind and then trying to start bitcoin-qt as a server, which can't work.
So, my new question, now, is: Can I connect bitcoin-qt as a "client" to a constantly running bitcoind?
As I understand, that's what OP was actually asking. He probably changed his plans with "-server".
Now I think this isn't possible at all.. Then I would write a script to stop bitcoind and start bitcoin-qt automatically, when needed.
Ente
The problem you will have here is that both bitcoin-qt and bitcoind would be trying to access the same wallet. You can't start bitcoin-qt and tell it to just be a client.
Bitcoind is either a) the RPC server or b) an RPC client.
Bitcoin-Qt is a GUI + optionally the RPC server.
The error you're getting probably means you're already running bitcoind as RPC server, so you can't start Bitcoin-Qt in server mode as well.
Shut bitcoind down (./bitcoind stop), start Bitcoin-Qt with -server, and after that point you can send RPC commands to the GUI.
Bitcoin-Qt is a GUI + optionally the RPC server.
The error you're getting probably means you're already running bitcoind as RPC server, so you can't start Bitcoin-Qt in server mode as well.
Shut bitcoind down (./bitcoind stop), start Bitcoin-Qt with -server, and after that point you can send RPC commands to the GUI.
Aaah, now I get it!
So I was in fact running bitcoind and then trying to start bitcoin-qt as a server, which can't work.
So, my new question, now, is: Can I connect bitcoin-qt as a "client" to a constantly running bitcoind?
As I understand, that's what OP was actually asking. He probably changed his plans with "-server".
Now I think this isn't possible at all.. Then I would write a script to stop bitcoind and start bitcoin-qt automatically, when needed.
Ente
Bitcoind is either a) the RPC server or b) an RPC client.
Bitcoin-Qt is a GUI + optionally the RPC server.
The error you're getting probably means you're already running bitcoind as RPC server, so you can't start Bitcoin-Qt in server mode as well.
Shut bitcoind down (./bitcoind stop), start Bitcoin-Qt with -server, and after that point you can send RPC commands to the GUI.
Bitcoin-Qt is a GUI + optionally the RPC server.
The error you're getting probably means you're already running bitcoind as RPC server, so you can't start Bitcoin-Qt in server mode as well.
Shut bitcoind down (./bitcoind stop), start Bitcoin-Qt with -server, and after that point you can send RPC commands to the GUI.
I run bitcoin-qt in server mode but I did it with a change to the config file.
The latest bitcoin-qt runs quite happily in this mode with p2pool.
The latest bitcoin-qt runs quite happily in this mode with p2pool.
Run the gui with the -server switch.
Uhm, sorry for necromancy, but I can't get it to work..
Quote
/opt/bitcoin/bin/64/bitcoin-qt -server
Quote
"Can't lock folder, maybe bitcoin was already started"
Same with --server.I can't see any hint via --help neither. Is this still working in 0.7x?
Why? I want to have the bitcoind running whenever my computer is on. Always having the blockchain up-to-date and helping the network a bit. Then connect to bitcoind via armory and bitcoin-qt, when needed.
Different question: Is it safe to simply shut down linux? bitcoin-qt takes/took a bit to completely shut itself down, I don't want to corrupt anything when linux doesn't wait for bitcoind to cleanly shut down and switches off the computer..
Ente
Run the gui with the -server switch.
At least on my Xubuntu machine, any attempt to start the graphical client fails with the message: "Cannot obtain a lock on data directory /home/rena/.bitcoin. Bitcoin is probably already running." So, any time you want to use the graphical interface you need to first shut down bitcoind, losing all your connections. Or you can leave the GUI open all the time (sitting in taskbar since the option to minimize to tray is disabled), which is kinda inconvenient and makes the daemon not really a daemon anymore.
Can the GUI app not simply work as a frontend to bitcoind, letting it run at all times?
Can the GUI app not simply work as a frontend to bitcoind, letting it run at all times?
Jump to: