Zotero won't open

MacOs Mojave 10.14.6
Zotero won't launch - Application is not responding
Created a new profile, uninstalled, reinstalled, upgraded to 6.0.4, nothing works.
Debug is unresponsive, too. Jconsole is unable to complete and freezes
Run ZoteroDebugText -console on terminal window. And the following came up:

JavaScript warning: resource://zotero/loader.jsm -> resource://zotero/bluebird/util.js, line 205: unreachable code after return statement
JavaScript warning: resource://zotero/loader.jsm -> resource://zotero/bluebird/util.js, line 205: unreachable code after return statement
JavaScript warning: chrome://zotero/content/zoteroPane.js, line 5453: unreachable code after return statement
zotero(3)(+0000000): Using data directory /Users/Cengiz/Zotero

zotero(3)(+0000021): IPC: Initializing pipe at /Users/Cengiz/Zotero/pipes/1648459049074

zotero(3)(+0000021): Asynchronously opening database 'zotero'

zotero(3)(+0000001): /Users/Cengiz/Zotero/zotero.sqlite

zotero(4)(+0000005): PRAGMA main.locking_mode=EXCLUSIVE

zotero(4)(+0000001): PRAGMA page_size

zotero(4)(+0000001): PRAGMA cache_size=2000

zotero(4)(+0000000): PRAGMA foreign_keys=true

zotero(3)(+0000001): IPC: Trying to broadcast "releaseLock /Users/Cengiz/Zotero/zotero.sqlite" to instance 1648458414580

zotero(3)(+0000100): IPC: Removing defunct pipe 1648458414580

zotero(4)(+0000010): SELECT version FROM version WHERE schema='system'

zotero(3)(+0000001): Proxy not required for https://zoteroproxycheck.s3.amazonaws.com/test

zotero(4)(+0000002): SELECT version FROM version WHERE schema='userdata'

zotero(4)(+0000000): SELECT version FROM version WHERE schema='compatibility'

zotero(4)(+0000002): SELECT value FROM settings WHERE setting='db' AND key='integrityCheck'

zotero(3)(+0000002): HTTP GET resource://zotero/schema/global/schema.json

zotero(3)(+0000002): HTTP GET resource://zotero/schema/global/schema.json succeeded with 200

zotero(4)(+0000003): SELECT version FROM version WHERE schema='globalSchema'

zotero(3)(+0000000): Global schema needs update from 11 to 15

zotero(3)(+0000001): HTTP GET resource://zotero/schema/userdata.sql

zotero(3)(+0000000): HTTP GET resource://zotero/schema/userdata.sql succeeded with 200

zotero(3)(+0000001): Backing up database 'zotero'

zotero(4)(+0000023): PRAGMA main.locking_mode=NORMAL

Any help is much appreciated.
  • Have you tried restarting your computer?

    Are you using any sort of external tool on your computer that accesses zotero.sqlite?

    When you tried with a new profile, did that create a new data directory or use your existing one? If the latter, you can use -datadir from the command line to specify a different data directory location, in order to test with a fresh data directory.
  • Restarted the computer many times.
    Have been using AirPort Time Capsule for a long time, but never had a problem like this.
    With the new profile, I deleted the content of the new data directory and pasted the content of the old one into it, with storage, sqlite etc.
  • Right, but the question is whether it works in a new data directory, not with your old files.
  • Yes, zotero works with a new directory
  • How big is zotero.sqlite?

    Are there *.bak files in the data directory? Does it help if you move them out of the way?

    You can try the DB Repair Tool, or if you know how to use an SQLite client you can run PRAGMA integrity_check; on the file to see if it's corrupted.
  • Zotero.sqlite is 2.72 GB

    I also have zotero.sqlite.1.bak, and zotero.sqlite.bak files, each 2.71 GB

    Also have zotero.sqlite-journal, and zotero.sqlite.tmp (1.08 GB)

    I removed them all, except zotero.sqlite, out of the way, but nothing has changed.

    I'll try DB Repair Tool, but not sure how to overcome max 150 MB limit. I don't know SQLite client, but will try to learn.
  • Could you please provide me with specific instructions on how to use SQLite?
  • Also, I copied my zotero.sqlite file in my macbook zotero data directory, and it worked there - I was able to access the database. I suppose this means that the database is not corrupted and something in my desktop computer preventing me from accessing the database, right?
Sign In or Register to comment.