Sparrow can't reach Bitcoin Core when started via systemd

2 replies 452 views
leo_farmMember
Posts: 1 · Reputation: 58
#1Apr 19, 2017, 09:04 AM
I've got Sparrow running on one machine and Bitcoin Core on another. When I launch Bitcoin Core from the command line using bitcoind -daemon, everything works perfectly and Sparrow can connect to it. But when I start Bitcoin Core through systemd with bitcoind -daemon in a unit file, it runs just fine but Sparrow can't connect at all. The configuration file is the same for both methods. Anyone have any clue why that's happening? Thanks a lot.
6 Reply Quote Share
im_lynxHero Member
Posts: 515 · Reputation: 2161
#2Apr 19, 2017, 12:49 PM
Does your Bitcoin Core from systemd run as the same user as when you start Bitcoin Core from the command line? Have you checked that both instances of Bitcoin Core actually read the same settings from bitcoin.conf file? Have you tried connecting with bitcoin-cli or other methods (like with curl) from the computer where Sparrow runs to your Bitcoin Core on the other computer? bitcoin-cli help command gives you examples how to talk to Bitcoin Core via curl. Would you post the content of your bitcoin.conf, settings.json and your unit file? (Make sure to redact anything that could be detrimental to your privacy. Redact RPC access credentials, if you've set them up.) Put file content properly in [code]...[/code] tag blocks.
0 Reply Quote Share
hash_bossLegendary
Posts: 1166 · Reputation: 5261
#3Apr 19, 2017, 01:48 PM
Without additional ramification, i would suggest debug.log to see whether same configuration/argument loaded by Bitcoin Core. On my node, i see something like this.
1 Reply Quote Share

Related topics