Closed Bug 272633 Opened 20 years ago Closed 16 years ago

Stub installer networking issues cause installation to timeout

Categories

(SeaMonkey :: Installer, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tracy, Unassigned)

Details

(Whiteboard: WFM)

seen on Linux stub installer 2004-12-01-08-1.7

-use the stub installer to do a Complete installation
-during the download phase make note of changes in download speed from modula to
module

tested results: When the Navigator module completed downloading then Mail News
begins, the download speed dropped dramatically. On each subsequent new module
the download speed changes.  Often one of the slowdowns would cause the
indstaller to hang.  During one attempt, a Network connectivity message
appeared, I clicked resume as suggested, but the download never resumed. 

expected results: All modules download without hang, then proceed to and
complete installation.

workaround is to use the full installer
the stub installer is installing xpis, could this bug be related to 
Bug 272599 Crash while try xpi-install into newest Trunk-Nightly
this worked fine for me with the same build.

are you sure there are no networking problems on the computer?  The last change
to the linux installer on the 1.7 branch was 5/22.

Hermann: Tracy is using a 1.7 branch build.
Version: unspecified → 1.7 Branch
Asa and I explored it a bit.  Because sometimes the installation does succeed,
albeit slowly, we believe this maybe a network or mirrors issue. This didn't
affect the stub Windows installer from this morning. Although I did try it later
in the morning. I'll retry again on Linux tomorrow on the same network to see if
those issues may have cleared up.

However, a slow connection, whether it be the network or down/slow mirrors,
shouldn't cause the stub installer to hang.  The Network connectivity message I
got once seemed appropriate. But upon "resume" it hung anyway.
I reinstalled the same build here at work.  Although it was slow it did manage
to get through the download phase without hanging.  

Lowering severity.

Note: I was tracking down a regression window on Mozilla Trunk and found several
stub installers would not complete because the windows-xpi folder was not found.
Anyhow, when using the stub installer against that empty windows-xpi, the
installer came up with the too many network errors dialog which allowed you to
at least retry or cancel without hanging.  In that case, installation was never
going to be able to download because the files were not available.  Just
pointing out what I'd expect to happen with a slow/non working download on the
linux branch.
Severity: blocker → major
Keywords: smoketest
Tracy: has this happened anymore?

> In that case, installation was never going to be able to download because the 
> files were not available.  Just pointing out what I'd expect to happen with a 
> slow/non working download on the linux branch.

The linux installer only repaints the window when it receives network traffic
and/or the network backend gives it an error (the installer is not hung-up, it's
just not repainting).  The connection *will* timeout eventually (and give a
dialog box), but the timeout is pretty long.  The repainting issue is certainly
not good, but (AFAIK) is non-trivial to fix.
Whiteboard: WFM
I filed bug 282989 to get repainting to work better
I do often see this with recent trunk builds.  But, if I remain persistant and
continue to try *resume* from the network errors timeout message, I eventually
get through the download of the various module xpi's.  Is this a networking or
server bug?  

changing summary; the installer isn't hanging, simply timing out.  
Summary: Stub installer networking issues cause installation to hang → Stub installer networking issues cause installation to timeout
Version: 1.7 Branch → Trunk
can you grab a packet trace with tcpdump or ethereal?

tcpdump port http > packet.log
[start download, hit ctrl-C when download finishes/fails]
QA Contact: bugzilla → general
Seamonkey and Firefox are using a new NSIS based installer. resolving this old
bug, please reopen if you still get this with the new installer
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.