300921 - Update stuck after "deer park was unable to verify the integrity..." (when Mirrors not yet ready)

Status: RESOLVED DUPLICATE of bug 300089

(Toolkit :: Application Update, defect)

Description

[Stebs]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050714 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050714 Firefox/1.0+

After Checking for updates, the message "deer park was unable to verify the
integrity of the incremental update it downloaded, so it is downloading the
complete update package" appears.
After that, update is stuck for good with the message "Connecting to the update
server" with all buttons grayed out exept "Close". Restart of Firefox does not help.

This is NOT bug 288054 because "Allow web sites to install software" IS checked.

Rather this happens only very briefly after a new Nightly is out. It seems that
if you try to update too soon after the nightly was built, its not on all the
mirrors, so the mirror that the auto updater tries to download it from doesnt
have it. This happened to a lot of people in the MozillaZine Nightly Forum.

Fix/Workaround:
Deleting active-update.xml and updates.xml in the Firefox Application Folder
does solve the Problem. When you wait approximately 30 minutes after release of
a new Nightly, you do not run into this Problem.      

Reproducible: Sometimes

Steps to Reproduce:
(because the mirror assigned to you must still be not "ready")
1.Watch closely for the release of a new Nightly
2.Update with "Check for updates" (has to be well within 15 minutes of new
release of Nightly) 


Actual Results:  
Update gets stuck after "deer park was unable to verify the integrity..." message

Expected Results:  
Update ;)

Comment 1

[Jaime Mitchell (use [e-mail] for email)]

This maybe related to bug 300089

Comment 2

[Stebs]

(In reply to comment #1)
> This maybe related to bug 300089
That could be the case, final symptoms are exactly the same. Not sure the cause
is the same though, because it is not described detailed enough in bug 300089.
(Your comment #2 clearly describes this bug though)

Comment 3

[Stebs]

*** This bug has been marked as a duplicate of 300089 ***

Comment 4

[Jerry Baker]

This is marked as a duplicate of bug 300089, but bug 300089 is fixed. This
problem still occurs.

Comment 5

[Jerry Baker]

Interesting. I was capturing packets when I got one of those "cannot verify the integrity" messages, and here's the conversation. What is up with the Range Firefox is sending?

GET /pub/mozilla.org/firefox/nightly/2005-10-24-01-trunk/firefox-1.6a1.en-US.win32.partial.2005102401-2005102405.mar HTTP/1.1
Host: mozilla.osuosl.org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051024 Firefox/1.6a1
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Range: bytes=364940-

HTTP/1.1 416 Requested Range Not Satisfiable
Date: Mon, 24 Oct 2005 14:39:01 GMT
Server: Apache
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
Connection: Close