If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Sync fails, says "unknown error", no more info.

RESOLVED INCOMPLETE

Status

Cloud Services
Firefox Sync: Backend
RESOLVED INCOMPLETE
7 years ago
6 years ago

People

(Reporter: tz, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20110103 Fedora/3.6.13-1.fc14 Firefox/3.6.13
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20110103 Fedora/3.6.13-1.fc14 Firefox/3.6.13

I get the failed to sync message occasionally, but then I click on it for details and it says "Unknown Error".

I would report more, but there isn't anything I can find.

Reproducible: Always

Steps to Reproduce:
1.wait for sync
2. it fails
3. It only says an error ocurred, but it is "unknown"
Actual Results:  
failure, with "Unknown error"

Expected Results:  
Success or at least some detail - did it connect to the server?  Did it not authenticate.

It is really stupid to have "unknown error".

Error While Syncing

sync encountered an error: Unknown error ... will retry..

Comment 1

7 years ago
Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20100101 Firefox/4.0b12

I was unable to reproduce issue.

Can you please try reproducing issue on a clean profile:
http://support.mozilla.com/en-US/kb/managing%20profiles

Also, try it with the latest beta:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/4.0b12-candidates/build1/

Thanks!
sync is an addon and it should work with 3.6.13
Component: General → Firefox Sync: Backend
Product: Firefox → Mozilla Services
QA Contact: general → sync-backend
(Reporter)

Comment 3

7 years ago
Yes, it works as an addon a large portion of the time.  But for some reason (internet and everything else works) it gives this error designed not to be able to be traced.  I'm not going to download the source tree to see where - there should be NO "Unknown Errors" - they should identify something with enough detail - the routine, the problem (connect? authenticate?).

This bug is NOT the fact that sync is failing as much as THERE IS NO INFORMATION PROVIDED WHEN IT FAILS.  That needs to be fixed.  Each place it would produce a failure message should have a unique and informative error string.
The actual error is logged but not necessarily shown in the UI. Please go to about:sync-log, save it to file and attach it to this bug. Thanks.

Comment 5

7 years ago
I've had this "unknown error" for ages as well, and gone thru all the "clean profile" business. Could there be something wrong with a particular bookmark?

Here is my about:sync-log. If someone could decypher which bookmark is failing perhaps I could delete/correct it somehow?

2011-03-21 14:56:56	Service.Main         DEBUG	bookmarks failed: NS_ERROR_ILLEGAL_VALUE JS Stack trace: Channel_onStopRequest([object XPCWrappedNative_NoHelper],null,2147942487)@resource.js:444 < Res__request(...)@resource.js:357 < Res_get()@resource.js:376 < SyncEngine__processIncoming()@engines.js:511 < _processIncoming()@bookmarks.js:212 < ()@engines.js:203 < SyncEngine__sync()@engines.js:768 < wrappedSync(null)@util.js:168 < runInBatchMode([object Object],null)@:0 < batchedSync()@util.js:174 < ()@engines.js:203 < WrappedNotify()@util.js:147 < Engine_sync()@engines.js:213 < WeaveSvc__syncEngine([object Object])@service.js:1739 < ()@service.js:1625 < WrappedNotify()@util.js:147 < WrappedLock()@util.js:119 < WrappedCatch()@util.js:97 < sync()@service.js:1530 < (6)@sync.js:380
(In reply to comment #5)
> I've had this "unknown error" for ages as well, and gone thru all the "clean
> profile" business. Could there be something wrong with a particular bookmark?

Please fill a new bug for your issue. "Unknown error" is about as precise as "browser crashes", so it's very likely that you're seeing something different.

We'd need a full sync log (not just a snippet, and yours looks like it's not the latest version anyway).

Thanks!

Comment 7

6 years ago
Mozilla/5.0 (X11; Linux i686; rv:8.0a1) Gecko/20110711 Firefox/8.0a1

Setting status to Resolved Incomplete. Please reopen if more information can be provided.

Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.