Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Learn More

Why am I always getting errors with sync

  • 2 απαντήσεις
  • 4 έχουν αυτό το πρόβλημα
  • 7 προβολές
  • Τελευταία απάντηση από FredMcD

more options

I was reading some of the posts with questions about Sync. I found out about about:sync-log and got curious. I looked at mine and found this:

File:error-1391364828451.txt 	19 KB 	2/2/2014 	1:13:48 PM
File:error-1391458084640.txt 	19 KB 	2/3/2014 	3:08:04 PM
File:error-1391692902312.txt 	4 KB 	2/6/2014 	8:21:42 AM
File:error-1391786978286.txt 	4 KB 	2/7/2014 	10:29:38 AM
File:error-1392211822077.txt 	4 KB 	2/12/2014 	8:30:22 AM

I looked at the latest log Everything looks fine until about 75% down. then errors start showing up. I read some of the help files and found this link; Firefox Sync service status and this page says; service is operating, however having some DNS propagation issues, which should be resolved very shortly. Its been like that for a long time. What's the story?

2/12/2014 	8:30:22 AM
1392211748823	Sync.Service	INFO	Logging in user liuxz3ullphl75232jlcw4gdtant3ytg
1392211748823	Sync.Service	DEBUG	Caching URLs under storage user base: https://phx-sync-11-2-2.services.mozilla.com/1.1/liuxz3ullphl75232jlcw4gdtant3ytg/
1392211822076	Sync.Service	DEBUG	verifyLogin failed: NS_ERROR_NET_RESET JS Stack trace: Res_get@resource.js:413 < verifyLogin@service.js:683 < onNotify@service.js:926 < WrappedNotify@util.js:142 < WrappedLock@util.js:97 < WrappedCatch@util.js:71 < login@service.js:937 < @service.js:1174 < WrappedCatch@util.js:71 < sync@service.js:1170
1392211822076	Sync.Status	DEBUG	Status.login: success.login => error.login.reason.network
1392211822076	Sync.Status	DEBUG	Status.service: success.status_ok => error.login.failed
1392211822076	Sync.Status	DEBUG	Status.login: error.login.reason.network => error.login.reason.network
1392211822076	Sync.Status	DEBUG	Status.service: error.login.failed => error.login.failed
1392211822076	Sync.SyncScheduler	DEBUG	Clearing sync triggers and the global score.
1392211822076	Sync.SyncScheduler	DEBUG	Next sync in 86400000 ms.
I was reading some of the posts with questions about Sync. I found out about about:sync-log and got curious. I looked at mine and found this: <pre><nowiki>File:error-1391364828451.txt 19 KB 2/2/2014 1:13:48 PM File:error-1391458084640.txt 19 KB 2/3/2014 3:08:04 PM File:error-1391692902312.txt 4 KB 2/6/2014 8:21:42 AM File:error-1391786978286.txt 4 KB 2/7/2014 10:29:38 AM File:error-1392211822077.txt 4 KB 2/12/2014 8:30:22 AM </nowiki></pre> I looked at the latest log Everything looks fine until about 75% down. then errors start showing up. I read some of the help files and found this link; '''[https://services.mozilla.com/status/ Firefox Sync service status]''' and this page says; '''''service is operating, however having some DNS propagation issues,''''' '''''which should be resolved very shortly.''''' Its been like that for a long time. What's the story? <pre><nowiki>2/12/2014 8:30:22 AM 1392211748823 Sync.Service INFO Logging in user liuxz3ullphl75232jlcw4gdtant3ytg 1392211748823 Sync.Service DEBUG Caching URLs under storage user base: https://phx-sync-11-2-2.services.mozilla.com/1.1/liuxz3ullphl75232jlcw4gdtant3ytg/ 1392211822076 Sync.Service DEBUG verifyLogin failed: NS_ERROR_NET_RESET JS Stack trace: Res_get@resource.js:413 < verifyLogin@service.js:683 < onNotify@service.js:926 < WrappedNotify@util.js:142 < WrappedLock@util.js:97 < WrappedCatch@util.js:71 < login@service.js:937 < @service.js:1174 < WrappedCatch@util.js:71 < sync@service.js:1170 1392211822076 Sync.Status DEBUG Status.login: success.login => error.login.reason.network 1392211822076 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1392211822076 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network 1392211822076 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1392211822076 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1392211822076 Sync.SyncScheduler DEBUG Next sync in 86400000 ms.</nowiki></pre>

Τροποποιήθηκε στις από το χρήστη cor-el

Όλες οι απαντήσεις (2)

more options

Hi FredMcD, I am sorry for the inconvenience, there is a new sync version that was added to Auroa. DNS does take a while to propagate. I checked in with the #sync channel and am awaiting a reply.

more options

Thanks for the reply.


BTW, have the authorities been called about Mr. Bad Mouth?