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

Uploading records failed: "server issue: pool exhausted"

RESOLVED FIXED

Status

Cloud Services
Operations
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: kael, Assigned: jlaz)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
I've had maybe 50 sync failures in the last week. I'm not sure if anything is syncing at all anymore.

Most of the error logs contain things like this:

1367523883416	Sync.Engine.History	INFO	63 outgoing items pre-reconciliation
1367523883416	Sync.Engine.History	INFO	Records: 0 applied, 0 successfully, 0 failed to apply, 0 newly failed to apply, 0 reconciled.
1367523883468	Sync.Engine.History	INFO	Uploading all of 63 records
1367523883470	Sync.Collection	DEBUG	POST Length: 37544
1367523884416	Sync.Tracker.History	DEBUG	Saving changed IDs to history
1367523885839	Sync.Tracker.History	DEBUG	Saving changed IDs to history
1367523895769	Sync.Collection	DEBUG	mesg: POST fail 503 https://phx-sync181.services.mozilla.com/1.1/nncur2kllvchqqzjpu4snkr64cnaoaxz/storage/history
1367523895769	Sync.Collection	DEBUG	POST fail 503 https://phx-sync181.services.mozilla.com/1.1/nncur2kllvchqqzjpu4snkr64cnaoaxz/storage/history
1367523895769	Sync.Engine.History	DEBUG	Uploading records failed: "server issue: pool exhausted"
1367523895770	Sync.ErrorHandler	DEBUG	Got Retry-After: 300
1367523895770	Sync.Status	DEBUG	Status.sync: success.sync => error.sync.reason.serverMaintenance
1367523895770	Sync.Status	DEBUG	Status.service: success.status_ok => error.sync.failed

The sync UI says 'unknown error' and has the Sync Now button, but manually retrying doesn't seem to fix anything.
Had some hardware problems; they're being worked on.
Component: Firefox Sync: Backend → Operations
(Assignee)

Comment 2

4 years ago
Services infra is now stable, please reopen if you continue to have issues
Assignee: nobody → jlaz
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.