-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unmounted database directory causes btcd to fail uninformatively #193
Comments
Confirmed. The error is being logged before the logging system is initialized. I'll submit a pr to fix it shortly. |
This commit improves a couple of issues surrounding the creation of the btcd home directory. First, the code was previously attempting to log any errors that occurred while creating the directory using the logging system which is not initialized at that point. Thus, nothing was displayed to the user. Second, if any component of btcd home directory path already exist, but are not a directory, such as in the case of symlinks, the error returned from the os.MkDirAll call indicates the directory can't be created. While this is true, it's not always the most helpful error to display to the user. So, this commit adds logic to detect when the failure case is due to an existing symlink and displays a nicer error message suggesting the user check if the destination of the link is mounted. Fixes btcsuite#193.
@adamkrellenstein: Can you give pr #194 a try to see if that satisfactorily resolves the issue?
|
@davecgh, yep, it works now:
|
Reopened since the pull request isn't merged to master yet. It will close the issue when merged. |
…ble-bridge Make bridge nodes recoverable
On my system,
~/.btcd
is symlinked to a mountable directory in/mnt
(with the drive formatted with btrfs):When this directory isn't mounted, btcd always immediately fails without any error message at all:
C.f.:
The text was updated successfully, but these errors were encountered: