Attempt to write a readonly database
This is the Alert I keep getting whenever I try to add or Edit a Password or a Login.
I checked the support folder in ~/Library/Containers/2BUA8C4S2C.com.agilebits.onepassword-osx-helper - and nothing is locked there. Any ideas?
Comments
-
What version of 1P are you running, please, and on what OS X version?
Is it possible that you've installed more than one copy of 1P on your Mac?
Stephen
0 -
Thanks for following up.
I'm on 5.1 (510027) AppStore version, running on 10.10.2. The only other copy is on my TimeMachine backup.
If I unmount the TM drive, I still get the Alert, and nothing is added or changed. The app opens fine, and everything seems ok until I hit the 'Save' button...
Rob
0 -
I checked Console, and see the following error message from 1P:
3/12/15 2:42:45.255 PM 1Password[3641]: 510027 [UI:0x618000070e00:] E saveItemChangesWithCompletion: | Error updating item
: Error Domain=SQLite Code=8 "attempt to write a readonly database" UserInfo=0x6180002608c0 {SQLiteExtenderError=8, NSLocalizedDescription=attempt to write a readonly database} 0 -
Hi @mountebank,
Can I ask, your user account, is it a normal one stored only on this machine or is it a networked account existing on an OS X server?
0 -
Not sure if I'm understanding you correctly, but I don't have OS X server - just a MacPro running 10.10.2. I also have a MBP, running 10.10.3 (beta), but I haven't used it in over a week. I created my user account this afternoon when I realized the problems I was having with 1P, so I assume it is a normal one.
0 -
Reading through this again, my OS X account is a normal 'admin' account on my machine - no server involved. I thought you might be referring to the account I had to create on this site in order to post!
0 -
Hi @mountebank,
Google seems to tell me that this could be caused by a few reasons.
This error can be triggered if there is more than 1 app connected to the database at once. Is there any possibility that you're running more than 1 version of 1Password? It looks like you searched and only found the one in TimeMachine.
The next reason is a permissions issue. Could you check that you have permission to write to the database in
Data/Library/Data/OnePassword.sqlite
within the~/Library/Containers/2BUA8C4S2C.com.agilebits.onepassword-osx-helper
container? You should check the -shm and -wal files as well.If you're super technical, we could check the integrity of the database by opening it in Terminal via
sqlite3 OnePassword.sqlite
then runningpragma integrity_check;
. It should either return 'OK' or an error. If it's an error then I would recommend you export your data using our Export to 1Pif feature and follow our Starting Over guide to restart with a fresh database, then re-import from 1Pif. Once a sqlite database has integrity problems, the database shouldn't be trusted anymore.I hope this helps. Looking forward to hearing from you.
Rick
0 -
Hi Rick,
I shutdown my machine last night, and everything seems to be working properly now - nothing has changed on my machine to explain why it works!
I looked in the .../Data/Library/Logs/1Password log, and see this problem has occurred sporadically since January (searching for 'attempt to write a readonly database').
I tried enclosing the log in case it provides any clues to what causes this, but apparently this is not allowed.
Rob
0 -
Very odd @mountebank,
Please do let us know if it continues. If it does we'll request a diagnostic report and let you know how to send that in. While there isn't anything massively sensitive in many of the logs it's best if you don't add them here. As we're going to treat this as ongoing I'm going to leave the thread open.
0 -
Thanks for all your help. I'll let you know if this recurs...
0 -
:smile:
0