Closed Bug 692096 Opened 13 years ago Closed 6 years ago

'resp.obj is null' on bookmarks upload

Categories

(Firefox :: Sync, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jkassay, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Build ID: 20110928134238 Steps to reproduce: Firefox Sync is no longer working and displaying the following error message: "Sync encountered an error while syncing: Unknown error. Sync will automatically retry this action." Actual results: I first thought it was a quota issue but I am only using 2.1MB. Here is the info from the Firefox Sync Log: (Note: You will see that towards the bottom, the "resp.obj is null" error message with a stacktrace) --------------------------------------------------------------------------------- 1317821678266 Sync.Service DEBUG Exception: Some engines did not sync correctly No traceback available 1317822024209 Sync.Service INFO Starting sync at 2011-10-05 07:40:24 1317822024211 Sync.SyncScheduler DEBUG Clearing sync triggers. 1317822024211 Sync.Service INFO In sync(). 1317822029507 Sync.Resource DEBUG mesg: GET success 200 1317822029507 Sync.Resource DEBUG GET success 200 1317822029507 Sync.Service DEBUG Fetching global metadata record 1317822029507 Sync.Service DEBUG Weave Version: 1.10.0 Local Storage: 5 Remote Storage: 5 1317822029507 Sync.Service INFO Sync key is up-to-date: no need to upgrade. 1317822029507 Sync.Service DEBUG Fetching and verifying -- or generating -- symmetric keys. 1317822029507 Sync.Service INFO Testing info/collections: 1317822029507 Sync.CollectionKeys INFO Testing for updateNeeded. Last modified: 1293119089.25 1317822029507 Sync.Service DEBUG Refreshing client list. 1317822029508 Sync.Engine.Clients INFO 0 outgoing items pre-reconciliation 1317822029508 Sync.Engine.Clients INFO Records: 0 applied, 0 failed to apply, 0 newly failed to apply, 0 reconciled. 1317822029508 Sync.Service INFO Updating enabled engines: 2 clients. 1317822029509 Sync.Engine.Bookmarks INFO 343 outgoing items pre-reconciliation 1317822041618 Sync.Collection DEBUG mesg: GET success 200 1317822041618 Sync.Collection DEBUG GET success 200 1317822041619 Sync.Engine.Bookmarks INFO Records: 0 applied, 0 failed to apply, 0 newly failed to apply, 0 reconciled. 1317822043371 Sync.Engine.Bookmarks INFO Uploading 0 - 100 out of 343 records 1317822043373 Sync.Collection DEBUG POST Length: 33585 1317822107538 Sync.Collection DEBUG mesg: POST success 200 1317822107539 Sync.Collection DEBUG POST success 200 1317822107676 Sync.Service DEBUG bookmarks failed: resp.obj is null JS Stack trace: ("0 - 100 out")@engines.js:1005 < innerBind("0 - 100 out")@util.js:1159 < SyncEngine__uploadOutgoing()@engines.js:1034 < SyncEngine__sync()@engines.js:1092 < wrappedSync(null)@bookmarks.js:257 < _sync()@bookmarks.js:263 < WrappedNotify()@util.js:164 < Engine_sync()@engines.js:399 < WeaveSvc__syncEngine([object Object])@service.js:1617 < ()@service.js:1509 < WrappedNotify()@util.js:164 < WrappedLock()@util.js:132 < _lockedSync()@service.js:1415 < ()@service.js:1406 < WrappedCatch()@util.js:106 < sync()@service.js:1394 1317822107721 Sync.SyncScheduler CONFIG Starting backoff, next sync at:Wed Oct 05 2011 10:13:34 GMT-0600 (Mountain Daylight Time) Expected results: Firefox Sync should work correctly.
Component: General → Firefox Sync: Backend
Product: Firefox → Mozilla Services
QA Contact: general → sync-backend
Version: 7 Branch → unspecified
Thanks for the report. I wonder if this is a symptom of the load issues we're currently having, or if it's unrelated.
Summary: Sync Encountered an error while syncing: Unknown Error. → 'resp.obj is null' on bookmarks upload
Related to Bug 685941?
Blocks: 696137
We haven't seen this recently, and it's likely that a lot of our work over the last few years has addressed this.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.