sync error "invalid response from server"

dabender
When attempting to sync my database over the server I get an: "invalid response from server" error. I have successfully synced this database before, however now after my browser hangs for the standard 5minutes and the then sync arrow spins for several more, I get that error. I'm attempting to generate a large database for a research group at MIT.

2.0's sounds pretty good right now! Anything we can do from the community to speed it along?
  • dstillman
    Can you provide debug output for the 15 or so lines before the "Invalid response" line?
  • dabender
    Hi Dan,

    Here are the lines. I've got the whole report saved if needed. Thanks!
    _____________________________________________________________________

    zotero(3): Translate: binding sandbox to http://forums.zotero.org/categories/

    zotero(3): Translate: searching for translators for http://forums.zotero.org/categories/

    zotero(5): SELECT detectCode FROM translators WHERE translatorID = ?

    zotero(5): Binding parameter 1 of type string: "e7e01cac-1e37-4da6-b078-a0e8343b0e98"

    zotero(3): Translate: executed detectCode for unAPI

    zotero(3): Translate: executed detectCode for COinS

    zotero(5): SELECT detectCode FROM translators WHERE translatorID = ?

    zotero(5): Binding parameter 1 of type string: "951c027d-74ac-47d4-a107-9c3069ab7b48"

    zotero(3): Translate: executed detectCode for Embedded RDF

    zotero(3): Translate: running handler 0 for translators

    zotero(3): Translate: binding sandbox to http://forums.zotero.org/10/

    zotero(3): Translate: searching for translators for http://forums.zotero.org/10/

    zotero(5): SELECT detectCode FROM translators WHERE translatorID = ?

    zotero(5): Binding parameter 1 of type string: "e7e01cac-1e37-4da6-b078-a0e8343b0e98"

    zotero(3): Translate: executed detectCode for unAPI

    zotero(3): Translate: executed detectCode for COinS

    zotero(5): SELECT detectCode FROM translators WHERE translatorID = ?

    zotero(5): Binding parameter 1 of type string: "951c027d-74ac-47d4-a107-9c3069ab7b48"

    zotero(3): Translate: executed detectCode for Embedded RDF

    zotero(3): Translate: running handler 0 for translators

    zotero(3): Translate: binding sandbox to http://forums.zotero.org/discussion/3901/sync-error-invalid-response-from-server/#Item_0

    zotero(3): Translate: searching for translators for http://forums.zotero.org/discussion/3901/sync-error-invalid-response-from-server/#Item_0
  • dabender
    FYI: I believe there are well over 1000 entries in this database
  • dstillman
    That's just the debug output for loading this page. We'll need the last lines of the output generated while attempting a sync.
  • dabender
    I'm sorry, I'm relatively new at this and don't know how to Identify the error in the log. I have to output from the terminal saved; it's really long and it doesn't have the work error anywhere. Any advice?
  • dstillman
    You can send it to support@zot....org.
  • dstillman
    It looks like you're hitting a timeout on the initial sync. The server side of things still needs to be heavily optimized, and it's probably currently taking too long to handle your library (which, in addition to over 1,000 items, has ~3,500 creators) in time.

    It also looks, though, that your sync has started to go through a few times and hit an error due to overly long tags. When that happens, you would see a message about tags in the debug output instead of "An internal server error occurred. Please try again later." So you might want to shorten a few of the long tags and see if you can get it to go through.

    (Also, the five minutes isn't "standard"—it's just that your Zotero isn't completing the initial sync, so each time it regenerates the massive XML dump to send to the server. Once it succeeds, subsequent syncs should be pretty much instantaneous.)

This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.