2012-02-18 Nightly failing to update - LoadSourceFile: destination file size 24769536 does not match expected size 24771072

RESOLVED WORKSFORME

Status

()

Toolkit
Application Update
RESOLVED WORKSFORME
6 years ago
3 years ago

People

(Reporter: Unfocused, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

My 2012-02-18 Nightly build is failing to update. The partial update prompts a restart, on startup when it tries to apply the update, it fails. Then when trying a full update, that fails at the end of the download.

I couldn't see the logs from the partial update, as the error console scrolls those out of view on startup (thanks to content-related log messages). But here's the log from the end of the download of the full update:



AUS:SVC Downloader:onProgress - progress: 22200000/22022539
 ----------
AUS:SVC Downloader:onStopRequest - original URI spec: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/02/2012-02-19-03-12-23-mozilla-central/firefox-13.0a1.en-US.win64-x86_64.complete.mar, final URI spec: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/02/2012-02-19-03-12-23-mozilla-central/firefox-13.0a1.en-US.win64-x86_64.complete.mar, status: 2147549183
 ----------
AUS:SVC Downloader:onStopRequest - non-verification failure
 ----------
AUS:SVC getStatusTextFromCode - transfer error: Failed (unknown reason), default code: 2152398849
 ----------
AUS:SVC Downloader:onStopRequest - setting state to: download-failed
 ----------
AUS:UI gErrorsPage:onPageShow - update.statusText: Failed (unknown reason)
 ----------
AUS:SVC Downloader:onStopRequest - all update patch downloads failed
Hmm... oddly, I restarted in safe-mode to test something else. Partial update failed again, so the full update started to download - and that completed successfully, and successfully applied. Kinda scary that an addon could potentially be causing updates to fail.

Here's my list of enabled extensions:


        Adblock Plus
        2.0.3
        true
        {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}

        AutoAuth
        2.1
        true
        autoauth@efinke.com

        BugzillaJS
        1.3.5
        true
        jid0-NgMDcEu2B88AbzZ6ulHodW9sJzA@jetpack

        Clearly
        4.3328.304.485
        true
        readable@evernote.com

        ConsoleĀ²
        0.9
        true
        {1280606b-2510-4fe0-97ef-9b5a22eafe80}

        Context Search
        0.4.6
        true
        {902D2C4A-457A-4EF9-AD43-7014562929FF}

        Customizable Shortcuts
        0.5.9
        true
        customizable-shortcuts@timtaubert.de

        Developer Assistant
        0.3.0.20110927
        true
        {75739dec-72db-4020-aa9a-6afa6744759b}

        DOM Inspector
        2.0.10
        true
        inspector@mozilla.org

        FlashGot
        1.3.9
        true
        {19503e42-ca3c-4c27-b1e2-9cdb2170ee34}

        HTTPS-Everywhere
        1.2.2
        true
        https-everywhere@eff.org

        Mass Password Reset
        1.05
        true
        masspasswordreset@johnathan.nightingale

        pdf.js
        0.2.218
        true
        uriloader@pdf.js

        SearchLoad Options
        0.6.3
        true
        searchloadoptions@esteban.torres

        Spool
        0.3.58.0
        true
        spool@getspool.com
You could look in the updates/last-update.log and backup-update.log for clues. I'm not sure where win64 puts those but %LOCALAPPDATA% is probably a good place to start.
Created attachment 598994 [details]
backup-update.log

Ah, of course. Here's the backup-update.log, which contains the following error:

EXECUTE PATCH xul.dll
LoadSourceFile: destination file size 24769536 does not match expected size 24771072
LoadSourceFile failed

Comment 4

3 years ago
bad download?
Flags: needinfo?(nthomas)
Summary: 2012-02-18 Nightly failing to update → 2012-02-18 Nightly failing to update - LoadSourceFile: destination file size 24769536 does not match expected size 24771072
With the LoadSourceFile failure and an incorrect size for the complete mar when compared to the update.xml I suspect it offered the wrong mar files. There is bug 1157233 for the current known issues along these lines. This cleared itself up as it is suppose to when it downloaded the complete.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(nthomas)
You need to log in before you can comment on or make changes to this bug.