Closed Bug 474221 Opened 16 years ago Closed 16 years ago

Signed In But Can't Sync

Categories

(Cloud Services :: General, defect)

Product:
Cloud Services
Component:
General
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: jim.b, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 Build Identifier: 0.2.98 I just upgraded from Vista 32-bit to Server 2008 64-bit :^}. I have the latest build of FF from the Mozilla Web site and the latest Weave .xpi (0.2.98). However when I try to synchronize it gives me this error: "2009-01-18 10:53:15 Sync.Status INFO Skipping modal sync". The window flashes for a few ms and then this gets put in the log. I asked my friend Google but he told me that this had been fixed in a previous version? I'm suspecting that it has something to do with the x64 installation or Server 2008 but I would hope there's a workaround!?? Thanks, Jim Reproducible: Always Steps to Reproduce: 1. Log in - Successful 2. Try to synchronize 3. Actual Results: Sync window flashes for a second and logs this error: "2009-01-18 10:53:15 Sync.Status INFO Skipping modal sync" Expected Results: Synchronization.
The "skipping modal sync" error means login did not succeed. Are there any errors in your log about that?
(In reply to comment #1) > The "skipping modal sync" error means login did not succeed. Are there any > errors in your log about that? Nope, it says it logged in successfully. I just launched FF and below is the log I received: 2009-01-20 08:03:24 Service.Main INFO Weave Service Initializing 2009-01-20 08:03:24 Chrome.Window INFO Logging in... 2009-01-20 08:03:24 Chrome.Window INFO User string: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 2009-01-20 08:03:24 Chrome.Window INFO Weave version: 0.2.98 2009-01-20 08:03:29 Chrome.Window INFO Login successful 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:30 BmkTracker WARN Attempted to add undefined ID to tracker 2009-01-20 08:03:57 Sync.Status INFO Skipping modal sync
I suspect you are seeing bug 471076 and login actually failed. Can you check the verbose log in between these timestamps? 2009-01-20 08:03:24 Chrome.Window INFO Logging in... ... 2009-01-20 08:03:29 Chrome.Window INFO Login successful
Hm, though that fix should be in 0.2.98. So perhaps you have a different bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #3) > I suspect you are seeing bug 471076 and login actually failed. Can you check > the verbose log in between these timestamps? > > 2009-01-20 08:03:24 Chrome.Window INFO Logging in... > ... > 2009-01-20 08:03:29 Chrome.Window INFO Login successful Here's the verbose log: 2009-01-20 15:31:12 Chrome.Window INFO Sync window closed 2009-01-20 15:31:17 Service.Main INFO Weave Service Initializing 2009-01-20 15:31:17 Service.Main CONFIG Weave scheduler enabled 2009-01-20 15:31:17 Service.Main DEBUG Event: weave:service:login:start 2009-01-20 15:31:17 Chrome.Window INFO Logging in... 2009-01-20 15:31:17 Chrome.Window INFO User string: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 2009-01-20 15:31:17 Chrome.Window INFO Weave version: 0.2.98 2009-01-20 15:31:17 Service.Main DEBUG Logging in user jabit85 2009-01-20 15:31:17 Service.Main DEBUG Event: weave:service:verify-login:start 2009-01-20 15:31:17 Service.Main DEBUG Verifying login for user jabit85 2009-01-20 15:31:18 Net.Resource DEBUG GET request successful (301) 2009-01-20 15:31:18 Service.Main DEBUG Event: weave:service:verify-login:error 2009-01-20 15:31:18 Service.Main DEBUG Event: weave:service:login:success 2009-01-20 15:31:18 Chrome.Window INFO Login successful 2009-01-20 15:31:18 Service.Main DEBUG Event: weave:service:sync:start 2009-01-20 15:31:18 FaultTolerance DEBUG Original exception: aborting sync, not logged in Async stack trace: module:wrap.js:164 :: WeaveCatchAllWrapper module:wrap.js:94 :: WeaveNotifyWrapper module:service.js:603 :: WeaveSvc_sync module:service.js:313 :: WeaveSvc__onStartup module:util.js:501 :: EL_notify Last callback created at module:wrap.js:133 :: WeaveLocalLockWrapper 2009-01-20 15:31:18 Service.Main DEBUG Event: weave:service:sync:success 2009-01-20 15:31:21 Sync.Status INFO Skipping modal sync
What is your server URL set to? The server should not be returning a 301. (and problem #2: the client should not consider that 'successful').
Blocks: 468694
Target Milestone: -- → 0.3
(In reply to comment #6) > What is your server URL set to? The server should not be returning a 301. (and > problem #2: the client should not consider that 'successful'). Before I got this log, I seen that the login was indeed failing because it couldn't find the sync directory on MyDisk.se. It was now looking for https://mydisk.se/jabit85/weave/0.3/jabit85..... instead of https://mydisk.se/jabit85/weave/jabit85..... So I created that directory and now I'm getting the above errors. From the log, it looks like it's getting an error on the verify-login call but then a success right after??
Weave 0.2.90 and higher use the 0.3 server API, which is not WebDAV. MyDisk.se is a WebDAV provider, so it will not work. See the forums for how to set up your own 0.3 server, or check back for how to get an account with Mozilla (coming soon).
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Thanks, I'll continue using the older plugin then since that still works. Unless you can get me an account with Mozilla....?? :p
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.