Recent mod_wsgi Issue with Self-Hosted Sync Server

Ryan Kelly rfkelly at mozilla.com
Wed Sep 3 22:51:21 PDT 2014


On 4/09/2014 2:25 PM, Reuben Farrelly wrote:
> No joy, I'm afraid.  I uncommented those options in my syncserver.ini
> file and now server side I see this:
> 
> 203.xx.xxx.1 - - [04/Sep/2014:13:29:57 +1000] "GET /token/1.0/sync/1.5
> HTTP/1.1" 401 109 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0)
> Gecko/20100101 Firefox/32.0"
> 
> and this:
> 
> [Thu Sep 04 13:29:59.134875 2014] [wsgi:error] [pid 18941]
> /var/www/mozilla-services/sync-server.reub.net/htdocs/server-full/local/lib/python2.7/site-packages/tokenserver/verifiers.py:47:
> FutureWarning: The BrowserID certificate format has not been finalized
> and may change in backwards-incompatible ways.  If you find that the
> latest version of this module cannot verify a valid BrowserID assertion,
> please contact the author.
> [Thu Sep 04 13:29:59.134948 2014] [wsgi:error] [pid 18941]
> super(LocalVerifier, self).__init__(**kwargs)
> [Thu Sep 04 13:29:59.153143 2014] [wsgi:error] [pid 18941]
> INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS
> connection (1): api.accounts.firefox.com
> [Thu Sep 04 13:30:00.470899 2014] [wsgi:error] [pid 18941]
> INFO:mozsvc.metrics:{"tokenserver.backend.get_user":
> 0.001425027847290039, "code": 401, "request_time": 1.3324501514434814,
> "remoteAddressChain": ["203.219.122.1"], "agent": "Mozilla/5.0 (Windows
> NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0",
> "tokenserver.assertion.verify": 1.329387903213501,
> "token.assertion.verify_success": 1, "path":
> "https://sync-server.reub.net/token/1.0/sync/1.5", "method": "GET"}
> 
> Nothing progresses past that point and sync never kicks off - it
> successfully authenticates me but the actual sync process itself never
> proceeds.

Is there any additional information in the client-client sync logs?
(about:sync-log)

Stopping at this point usually indicates some sort of auth error between
the token and storage parts of the server, which may be caused by:

  * failure to set a fixed "secret" in the config file
  * invalid values for public_url or similar settings


> Incidentally, I've noticed that every time I disconnect and reconnect my
> sync settings in Firefox it resets the services.sync.tokenServerURI
> setting back to default.  This is extremely annoying when testing or
> when sync breaks and I need to disconnect/reconnect the account - is
> this setting supposed to default back by design?

Aye, this is known behaviour that's very annoying for folks setting up
self-hosted sync:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1003708


 Cheers

    Ryan




More information about the Sync-dev mailing list