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

Cannot obtain lock on folder - fixed and was a permissions problem, repeatable #7303

Closed
timb999 opened this issue Jan 6, 2016 · 3 comments
Closed
Labels

Comments

@timb999
Copy link

timb999 commented Jan 6, 2016

Hi,

I recently installed BitCoinCore 0.11.2 on my Windows 7 64bit Pro machine.

The first time I ran the program, all was fine, and the blockchain started to sync. I left this for several hours, but needed to turn my PC off so I shut the program down which was successful.

When I rebooted and ran the program again, I received an error saying...

"Cannot obtain a lock on data directory (location here) Bitcoin Core is probably already running"

I have fixed this issue myself and can inform you that this problem arose because the HDD that I am using for BitCoinCore is not C, but a different internal HDD. This HDD was used on a previous PC installation - I then had to reinstall my PC and I am reusing this same HDD. Because this HDD was used on a previous installation, there are permissions problems. I simply went to the folder that BitCoinCore is using and used the 'sharing' tab to give me full permission and this fixed the problem.

Therefore you might want to check this, or implement this into the error message...

Thanks
Tim

@jonasschnelli
Copy link
Contributor

I think the boost::interprocess::file_lock could not be acquired (file <datadir>/.lock) because you had permission issue (maybe occurred with a improper shutdown or a HDD failure or because you used the HDD which was previously used with another computer).

Looks after a local problem to me.

@maflcko
Copy link
Member

maflcko commented Jan 7, 2016

Indeed a local problem, but we could still extend the error message, if appropriate:

try {

@jonasschnelli
Copy link
Contributor

Seems to be a local issue. Feel free to improve the error output. Closing.

@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants