question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Old testnet bitcoin.conf prevents launch: [Errno 2] No such file or directory

See original GitHub issue
  • I’m submitting a …

    • [ x ] bug report
  • What is the current behavior? Node Launcher won’t start and will crash with below error message.

[Errno 2] No such file or directory: '/Users/somebody/Library/Application Support/Bitcoin/testnet3'
File "run.py", line 22, in File "node_launcher/gui/application.py", line 15, in __init__ File "node_launcher/node_set/node_set.py", line 29, in __init__ File "node_launcher/node_set/bitcoin.py", line 54, in __init__ File "node_launcher/node_set/bitcoin.py", line 128, in get_wallet_paths 
  • If the current behavior is a bug, please provide the steps to reproduce

I had an existing bitcoin testnet installation with a bitcoin.conf for testnet. I removed the testnet data at some point for space and because node wasn’t running anyway and this created a problem. When this bitcoin.conf is present in ~/Library/Application Support/Bitcoin the node launcher won’t start with above error message. Removing/renaming existing bitcion.conf will allow node launcher to start.

  • What is the expected behavior?

Node Launcher starting (preferably) and/or perhaps show a hint for the cause of the error and suggest disabling any current bitcoin installation and renaming the bitcoin.conf file.

  • What is the motivation / use case for changing the behavior?

Not so relevant for this issue, but more robust app launching.

  • Please tell us about your environment:

    • Operating System: [ macOS ]
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
Sosthene00commented, Apr 24, 2019

Hi, I want to give it a shot, I’ve started working on it

0reactions
PierreRochardcommented, Apr 25, 2019

Sorry for all the big changes @BobleChinois! I’ve got more changes coming for the configuration area as well. I have removed testnet support for now, in the future I’d like to find a way to support regtest/testnet without putting if statements all over the codebase

Read more comments on GitHub >

github_iconTop Results From Across the Web

Bitcoin.conf extra section/syntax needed for testnet · Issue #950
I would recommend to stop and undo the sourcing of (config) files where we don't control the ... for reading: No such file...
Read more >
My first full node - no bitcoin.conf
I have tried find . -name "bitcoin.conf" in the ~/.bitcoin directory as well as user ~/ and in /etc all return empty. Where...
Read more >
lightningd-config – Lightning daemon configuration file
Sets configuration file, and disable reading the normal general and network ones. If this is a relative path, it is relative to the...
Read more >
Running A Full Node - Bitcoin.org
/usr/local/bin/bitcoin-qt: error while loading shared libraries: libQtGui.so.4: cannot open shared object file: No such file or directory.
Read more >
Bitcoin Core 22.0
Upgrading directly from a version of Bitcoin Core that has reached its EOL is possible, but it might take some time if the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found