Can no longer synch between two machines running weave (503 errors from server)

VERIFIED FIXED

Status

VERIFIED FIXED
11 years ago
9 years ago

People

(Reporter: abillings, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
Since just after 8:12 PM on 12/11, I've been getting 503 errors when trying to synch using weave on my two machines.

I've checked the password manager and the passwords are the same as they should be and what I remember setting on both machine for both the service password and the encryption.

The verbose log shows the following for a normal attempt to synch:

2007-12-13 22:22:59	Service.Main	DEBUG	Service lock acquired
2007-12-13 22:22:59	Service.Main	DEBUG	Logging in
2007-12-13 22:22:59	Service.Main	INFO	Hashing username albill@arcanology.com
2007-12-13 22:22:59	Service.Main	DEBUG	Username hashes to dfba9baf82ab25da08625aa27370c44fb46cdf5a
2007-12-13 22:22:59	Service.Main	INFO	Using server URL: https://services.mozilla.com/user/dfba9baf82ab25da08625aa27370c44fb46cdf5a/
2007-12-13 22:22:59	Service.DAV	INFO	Logging in
2007-12-13 22:22:59	Service.DAV	DEBUG	Creating GET request for https://services.mozilla.com/user/dfba9baf82ab25da08625aa27370c44fb46cdf5a/
2007-12-13 22:22:59	Service.DAV	DEBUG	HTTP Header Authorization: Basic YWxiaWxsQGFyY2Fub2xvZ3kuY29tOmdlbmVyYWwx
2007-12-13 22:22:59	Service.DAV	DEBUG	HTTP Header Content-type: text/plain
2007-12-13 22:22:59	Service.DAV	DEBUG	HTTP Header If: 
2007-12-13 22:22:59	Service.EventHandler	DEBUG	Handling event load
2007-12-13 22:22:59	Service.DAV	WARN	_makeRequest: got status 503
2007-12-13 22:22:59	Service.DAV	WARN	Could not log in
2007-12-13 22:22:59	Service.Main	DEBUG	Login error
2007-12-13 22:22:59	Chrome.Login	INFO	Sync login window opened
2007-12-13 22:23:01	Service.Main	WARN	Service lock failed: already locked
2007-12-13 22:23:01	Service.Main	DEBUG	Login error
2007-12-13 22:23:03	Chrome.Login	INFO	Sync login window closed
2007-12-13 22:23:03	Service.Main	DEBUG	Service lock released

I'm running current trunk nightlies (Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b2pre) Gecko/2007121107 Minefield/3.0b2pre) and the Wave 0.1.12.3 version.
(Reporter)

Comment 1

11 years ago
Adding more people so someone can look at why I'm getting 503 errors. I assume that this isn't the case for everyone but I can no longer synch.
(Reporter)

Comment 2

11 years ago
I notice that if I go to the URL used in the requests above (https://services.mozilla.com/user/dfba9baf82ab25da08625aa27370c44fb46cdf5a/), I get prompted for my account credentials. If I give them, I get served a 503 Service Error by Apache which states:

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
(Reporter)

Comment 3

11 years ago
On CBeard's suggestion, I tried the update (0.1.12.4) for the add-on that came out today. This had no affect. It fails to sign in still. 

The log shows:

2007-12-19 15:24:06	Service.Main	DEBUG	Service lock acquired
2007-12-19 15:24:06	Service.Main	DEBUG	Logging in
2007-12-19 15:24:06	Service.Main	INFO	Hashing username albill@arcanology.com
2007-12-19 15:24:06	Service.Main	DEBUG	Username hashes to dfba9baf82ab25da08625aa27370c44fb46cdf5a
2007-12-19 15:24:06	Service.Main	INFO	Using server URL: https://services.mozilla.com/user/dfba9baf82ab25da08625aa27370c44fb46cdf5a/
2007-12-19 15:24:06	Service.DAV	INFO	Logging in
2007-12-19 15:24:06	Service.DAV	DEBUG	Creating GET request for https://services.mozilla.com/user/dfba9baf82ab25da08625aa27370c44fb46cdf5a/
2007-12-19 15:24:06	Service.DAV	DEBUG	HTTP Header Authorization: Basic YWxiaWxsQGFyY2Fub2xvZ3kuY29tOmdlbmVyYWwx
2007-12-19 15:24:06	Service.DAV	DEBUG	HTTP Header Content-type: text/plain
2007-12-19 15:24:06	Service.DAV	DEBUG	HTTP Header If: 
2007-12-19 15:24:06	Service.EventHandler	DEBUG	Handling event load
2007-12-19 15:24:06	Service.DAV	WARN	_makeRequest: got status 503
2007-12-19 15:24:06	Service.Main	DEBUG	Service lock released
2007-12-19 15:24:06	Chrome.Login	INFO	Sync login window opened
2007-12-19 15:24:07	Service.Main	DEBUG	Service lock acquired
2007-12-19 15:24:07	Service.Main	DEBUG	Logging in
2007-12-19 15:24:07	Service.Main	INFO	Hashing username albill@arcanology.com
2007-12-19 15:24:07	Service.Main	DEBUG	Username hashes to dfba9baf82ab25da08625aa27370c44fb46cdf5a
2007-12-19 15:24:07	Service.Main	INFO	Using server URL: https://services.mozilla.com/user/dfba9baf82ab25da08625aa27370c44fb46cdf5a/
2007-12-19 15:24:07	Service.DAV	INFO	Logging in
2007-12-19 15:24:07	Service.DAV	DEBUG	Creating GET request for https://services.mozilla.com/user/dfba9baf82ab25da08625aa27370c44fb46cdf5a/
2007-12-19 15:24:07	Service.DAV	DEBUG	HTTP Header Authorization: Basic YWxiaWxsQGFyY2Fub2xvZ3kuY29tOmdlbmVyYWwx
2007-12-19 15:24:07	Service.DAV	DEBUG	HTTP Header Content-type: text/plain
2007-12-19 15:24:07	Service.DAV	DEBUG	HTTP Header If: 
2007-12-19 15:24:07	Service.EventHandler	DEBUG	Handling event load
2007-12-19 15:24:07	Service.DAV	WARN	_makeRequest: got status 503
2007-12-19 15:24:08	Service.Main	DEBUG	Service lock released
2007-12-19 15:24:08	Chrome.Login	WARN	Unknown observer notification topic: weave:service-unlock:success
2007-12-19 15:24:09	Chrome.Login	INFO	Sync login window closed

Comment 4

11 years ago
This should be fixed now.  A server was down after the latest round of kernel upgrades.

Comment 5

11 years ago
Marking as fixed - reopen if you're still seeing this.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Reporter)

Comment 6

11 years ago
It works now.
Status: RESOLVED → VERIFIED

Updated

9 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.