syncing is stuck for everyone in our group

Nobody in our group seems to be able to sync. All using Zotero standalone client. ( I'm using 3.0.14 )
Press sync button and get the "Alter" dialog with message "One or more locally deleted Zotero tags have been modified remotely since the last sync. The local versions have been kept.\nView Error Console for full list of changes." Then click "OK" button. The "Processing updated data from sync server" with progress bar pops up and sits there seemingly indefinitely. Memory usage for Zotero client slowly climbs to 3.7GB and then settles to 2.2GB and seems to freeze. Client isn't "completely" dead, as progress bar seems to move from time to time (I could be confused though), but you can move the window around the screen, but can't use menus. Similar problem on with all people trying to sync.

I can't provide a report ID, since the menus are locked up. Is there a way to provide one on next startup??? (Maybe there isn't even an error being reported?) The "report errors" is grey on next startup.

I let the client sit overnight, however Windows installed some updates and restarted. But it ran for at least 4 hours before I left.

The last few operation I did on the db were:
1. Deleting a bunch of useless tags on all items they appeared on.
2. Adding and deleting some references, about 20 or so.

HELP....(please)
  • Also - two machines have gotten "XULRunner" error dialogs. Running 3.0.14, noticed in the forums, that there was an issue with older versions. Any relation?
  • I moved this to the "Troubleshooting" forum. Is this the correct place?
  • forum doesn't matter. You'll have to wait until Dan can take a look at this.
  • If this is happening on any Mac or Linux machines, you could run Zotero with real-time debug output enabled. If you let that go for a while and then zip it up and send it to support@zotero.org with a link to this thread, we can see what's going on. Unfortunately on Windows generating real-time debug output is too slow to be a viable option. You could try going through the Debug ID steps and keep the preferences window open, but I'm not sure if you'll be able to submit the output when the sync is going.

    I don't see anything out of the ordinary in the server logs, at least for your account—I see some repeated download attempts, but they're not particularly large and they certainly shouldn't cause the kind of hang and memory usage increase you're experiencing.
  • More Info
    Menus are now working so I generated a report ID 1706953047
    It's been running for 3hours 10 minutes now on my machine.
  • (Something seems wrong here, but whatever the cause of this, we're overhauling the way syncing works in Zotero 4.0 to avoid this sort of trouble—Zotero will sync items in small batches instead of syncing everything that has changed at once.)
  • edited February 28, 2013
    string(1331) "[JavaScript Error: "[Exception... "'Cannot start a DB transaction from a different wait level' when calling method: [nsIObserver::observe]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "native frame :: :: :: line 0" data: no]"]
    This shouldn't be there, but I'm not sure if it's the cause.

    If you do regain control after a while, I'd try to generate a Debug ID for a fresh sync attempt after a restart of Zotero.
  • And it doesn't need to cover several hours, if you're able to submit it sooner—10 minutes of attempted syncing should be more than enough time.
  • The Debug ID is D1018320178.
  • I fired up a Linux laptop. Updated Zotero. Trying to get the realtime output.

    How do you get debug output with standalone?

    How do you stop auto-sync with standalone - if you can't get to the menus?

    First few runs - segfaulted and got out of memory.
    $ ./run-zotero.sh > zot_log
    ###!!! ABORT: OOM: file /builds/slave/rel-m-rel-xr_lx_bld-0000000000/build/xpcom/string/src/nsTSubstring.cpp, line 533
    ###!!! ABORT: OOM: file /builds/slave/rel-m-rel-xr_lx_bld-0000000000/build/xpcom/string/src/nsTSubstring.cpp, line 533
    Segmentation fault

    $ ./run-zotero.sh
    out of memory
    Segmentation fault

    I did manage to get a debug log sent to zotero server from the advanced pane in preferences, ID in the previous message.
    Is that the same output that real-time logging would provide?
  • Different this time. Submitting to Zotero Server, seems to have allowed the "Processing data" dialog to disappear, but the sync icon is now spinning.

    I'm trying to send another debug Id right now.
    I wanted to get the earlier one in before it seqfaulted.
    I'll let you know if it submits.
  • And I just got this error
    Report ID: 1109430203
  • I started it with Firefox instead of the Standalone client, and emailed the debug output to support@zotero.org
  • edited February 28, 2013
    Is there a reason you just added a new group with another 8700 items? I'm still looking into the problem with your other library, but, for what it's worth, that's not going to help your situation—as I said above, Zotero currently syncs everything that has changed at once, so that's just going to create much more data for Zotero clients to download. Right now you have a huge in-process download on the server that may not finish.
  • edited February 28, 2013
    So I think the main issue here (not counting the new group) is just a lot of new data being added to the group since the last time you synced a month ago—about 3600 items. That certainly shouldn't cause a sync to hang indefinitely, but it could definitely take a while to process.

    What's the current situation? Did the sync finish? If you let it go overnight and it's not interrupted, does it finish?

    Assuming that other group is from you trying to troubleshooting this and it doesn't contain new data, you should delete that other group before trying to sync, since it will make it far more unlikely that your sync will go through. And you should post here when you do so that I can clear your stalled download on the server.
  • edited March 1, 2013
    Background: For my setup I have 3 computers. 1 Linux, 2 Windows, lets call them L1, W1, W2. I do work on one of them, and make sure the syncs work to the 2 others. Mainly I work on L1 and W1, and test with W2. Over the last 2 weeks we've done a lot of work. And it all syncd, even to other users in the group until just a 2 days ago when this started.

    On L1 I created the new group lib as a copy of the original, without any tags. I was guessing the volume of useless tags imported when into the library could be causing a slowdown. There are about 280000 tagitems(?correct field name) in the database. I created it by copying everything to the new group without any tags or child items. Hoping this would be a "cleaner" version. This version syncs just fine (on linux if that matters) for some reason. Again this is on L1 which is last place I successfully synced "TO" the Zotero server. I didn't actually want to sync it, but it automatically started on that client, I thought I had autosync turned off, I didn't.

    Not sure where the 30 days and 3600 items (does that include tags?) is coming from. I was updating (using and syncing) W1 and W2 much more often than that, much more recently. The computer W2 is on isn't even 30 days old (this is the one I'm mainly reporting with, where I discovered the problem)

    W2 ran just less than 7 hours trying to sync without finishing. So I killed it and dropped the entire library from W2 by doing a "Restore from Zotero Server". It has been running since 5pm last night, 17 hours, and it's still spinning. I've now killed that one.

    W1 is still in the same state ( can try the sync again when you instruct me to ), but not trying to sync at the moment.

    On L1 I've deleted all the items in the new group. (There was no option to delete the group, when it's done deleting items, I'll go to the website and try to delete it)
    It is syncing now, so it should be empty soon.

    I'll wait to hear from you before setting up any other syncs. However other users may be syncing.
  • Also - One of the other members of our group had the sync running for over 24 hours, with no results.
  • So everything on your account from the last day is likely irrelevant, since that was due to a stalled download on the server from the new library. That group now appears to be empty, and your stalled process is gone.

    The only download processes I see from your account have a last-sync date of January 25th. (3600 items includes notes and attachments.) I see plenty of uploads since then, meaning at least one of your computers is fully in sync and is uploading new data (which happens after downloading), but the behavior you describe would only happen if there was a large download, which would make sense with a last-sync date of a month ago. (Syncs that don't download anything aren't logged, so the computer that's just uploading wouldn't show up in the download logs if no other data has been added to the group.)

    I didn't check before, but it looks like there are now no other users in that group. Is that correct?

    Having lots of tag-item associations is likely part of the cause of the hang. If you want I can provide some code you can run to clear out all the tags (or all the automatic (orange) ones, if that's the problem) in that library. Your approach—to create a new library without tags—is also OK, but you'd want to delete the old one once that was uploaded so that your other clients didn't have double the amount to download.
  • >but it looks like there are now no other users in that group. Is that correct?
    Yes - I had to create a new group and move them to it. We have a grant due on Tuesday, they couldn't wait, and the boss gave me a Noon today ultimatum.

    At this point I think we are just going to recreate the whole database from scratch instead of using this imported version. It's been too much of a headache. Since many others report no issues with many times as many refs as we have, and you have stated the you don't usually see this kind of memory usage, and other just weird things, it'll just be easier to throw this one away and start over.
  • OK, fair enough, and sorry for the trouble. The new syncing architecture, and some sort of ability to clear out lots of unwanted tags, should help avoid problems like this in the future.
Sign In or Register to comment.