Unable to open 1Password database stored on NFS with Yosemite
Hi. My 1Password Database is stored on an NFS partition on Yosemite. When I run 1Password 5.0.1 I get the following error message. 1Password 4.1.3 works as expected.
Failed to open 1Password database
1Password mini failed to open database because of the following problem: 'unable to open database file'.
Additional information:
2014-10-24 20:40:13 +0000
5.0.1
501000
Error Domain=SQLite Code=14 "unable to open database file" UserInfo=0x7f9dda672340 {SQLiteExtenderError=14, NSLocalizedDescription=unable to open database file}
Comments
-
Hi @sjackman,
Can you explain how you're storing the data file on the NFS share? Are you sym-linking the 1Password folder or are you using the Folder Sync?
1Password does not support running from an NFS share because of an SQlite's file lock limitation. You have to use Folder Sync to store the data file on the NFS share and 1Password will then keep its database in sync with data file on the NFS share.
0 -
Hi, @MikeT. My home directory on Mac OS is mounted on an NFS partition. It's synced via Dropbox. I moved the 1Password Database to a local hard drive folder, but the problem persisted. I finally (a year later!) resolved the issue by deleting
~/Library/Application\ Support/1Password\ 4/
and also~/Library/Containers/*onepassword*
. It works now! When I restarted 1Password 5.3, it found the Dropbox folder, and I lost no data. So, this issue is resolved. I wanted to report my experience here.Error message
Failed to open 1Password database 1Password mini failed to open database because of the following problem: 'unable to open database file'. Additional information: 2015-04-22 21:38:42 +0000 5.3 530032 Error Domain=SQLite Code=14 "unable to open database file" UserInfo=0x7fced846c870 {SQLiteExtenderError=14, NSLocalizedDescription=unable to open database file}
Solution
Quit 1Password
rm -rf ~/Library/Application\ Support/1Password\ 4/ rm -rf ~/Library/Containers/*onepassword*
Restart 1Password
0 -
Thanks for the update @sjackman. Great to hear that this is working for you now. I wonder what was making sqlite mad there.
Rick
0