Skip to content
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

~/path/to/lock should be actual path value #332

Closed
lanzafame opened this issue Mar 8, 2018 · 0 comments
Closed

~/path/to/lock should be actual path value #332

lanzafame opened this issue Mar 8, 2018 · 0 comments
Assignees
Labels
exp/novice Someone with a little familiarity can pick up kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now

Comments

@lanzafame
Copy link
Contributor

Got this when attempting to run ipfs-cluster-service for the first time:

15:57:21.995 ERROR    service: could not obtain execution lock.  If no other process
is running, remove ~/path/to/lock, or make sure that the config folder is
writable for the user running ipfs-cluster.  Run with -d for more information
about the error lock.go:37
error acquiring execution lock: could not obtain execution lock

Would be better if the message contained the actual path to the lock.

@lanzafame lanzafame added kind/enhancement A net-new feature or improvement to an existing feature exp/novice Someone with a little familiarity can pick up P3 Low: Not priority right now labels Mar 8, 2018
@lanzafame lanzafame self-assigned this Mar 8, 2018
@ghost ghost added the status/in-progress In progress label Mar 8, 2018
@ghost ghost removed the status/in-progress In progress label Mar 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/novice Someone with a little familiarity can pick up kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now
Projects
None yet
Development

No branches or pull requests

1 participant