Closed Bug 689959 Opened 14 years ago Closed 13 years ago

Failed to sync with "server status" button

Categories

(Firefox :: Sync, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: walkerpbus, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 Build ID: 20110902133214 Steps to reproduce: Filed this bug. Expected results: It should have synced.
Reporter, please test again on the latest firefox build or nightly build. We need your sync log to determine the problem. To set up sync logging, see: https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/
Whiteboard: [closeme 2011-10-13]
Do you want from 2 other systems (1 Win XP, 1 Win &)?
Greetings Paul, Several dbs have experienced outages this week (including your node, scl2-sync251). You should now have a new node assignment. Are you still experiencing any issues?
(In reply to Justin Lazaro [:jlaz] from comment #3) > Greetings Paul, > > Several dbs have experienced outages this week (including your node, > scl2-sync251). You should now have a new node assignment. Are you still > experiencing any issues? Thanks, Justin, I don't know what you are talking about, unfortunately. I have had at least 1 incident today with the Sync on this machine.
no additional response. closing as wfm. please reopen if this occurs with current nightly builds. And always provide logs as per instructions at https://philikon.wordpress.com/2011/06/13/how-to-file-a-good-sync-bug/
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
I tried to show my sync-log but you have a limit of 65K characters. file:///C:/Users/walker/AppData/Roaming/Mozilla/Firefox/Profiles/nforv9jq.default/weave/logs/error-1321380438247.txt
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Whiteboard: [closeme 2011-10-13]
paul, that comment just shows that I removed a whiteboard comment. try splitting the log into parts or at least find the part with the failure and post it with some context lines before and after the failure.
"least find the part with the failure and post it with some context lines before and after the failure." How would I recognize the failure?
I'm sorry, I found a smaller & later error log & zipped it. Now, I've forgotten how to upload a zip file. I've re-looked at the Philikon link but it offered no help.
(In reply to Tracy Walker [:tracy] from comment #7) > paul, that comment just shows that I removed a whiteboard comment. > > try splitting the log into parts or at least find the part with the failure > and post it with some context lines before and after the failure. How will I know where the failure is?
(In reply to Tracy Walker [:tracy] from comment #7) > paul, that comment just shows that I removed a whiteboard comment. > > try splitting the log into parts or at least find the part with the failure > and post it with some context lines before and after the failure. How will I know where the failure is?
Search for "Error" in the log. Altnernatively, you can attach the file itself to the bug, rather than inline as a comment: https://bugzilla.mozilla.org/attachment.cgi?bugid=689959&action=enter
Component: General → Firefox Sync: Backend
QA Contact: general → sync-backend
I haven't had an error in sync for some time, sir do I might as well set this as resolved.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago13 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.

Attachment

General

Creator:
Created:
Updated:
Size: