Opened 14 years ago

Closed 14 years ago

#27816 closed defect (worksforme)

Install error: NSPortTimeoutException. connection timeout: did not receive reply.

Reported by: cw10025@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 1.9.2
Keywords: NSPortTimeoutException IFPKInstallElement Cc:
Port:

Description

Attempted to install http://distfiles.macports.org/MacPorts/MacPorts-1.9.2-10.6-SnowLeopard.dmg on Snow Leopard 10.6.5 with Xcode-3.2.5 and a prior release of MacPorts (from Leopard, selfupdate wouldn't run). The install failed and left this in the install log:

Dec 30 07:23:17 clozaril-2 Installer[20150]: IFPKInstallElement (1 packages)
Dec 30 07:28:17 clozaril-2 Installer[20150]: An exception was thrown from the install queue while running IFPKInstallElement.  NSPortTimeoutException.  connection timeout: did not receive reply.
Dec 30 07:28:17 clozaril-2 Installer[20150]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Dec 30 07:28:18 clozaril-2 Installer[20150]: IFDInstallController 5E20730 state = 7

I took a guess that since X11 was a prerequisite, maybe it needed to be running while the install was running. I started X, then re-ran the installer, then it worked. I don't know if that proves the installer needs X11 running or if it was just a transient error.

Change History (3)

comment:1 Changed 14 years ago by cw10025@…

Cc: cw10025@… added

Cc Me!

comment:2 Changed 14 years ago by jmroot (Joshua Root)

Cc: cw10025@… removed
Component: portsbase

Please choose the appropriate component as per the ticket guidelines linked from the New Ticket page. You don't need to be in cc when you are the reporter.

The installer doesn't do anything related to X11. More likely the timeout occurred on the rsync connection used to initially download the portfiles.

comment:3 Changed 14 years ago by jmroot (Joshua Root)

Resolution: worksforme
Status: newclosed

In the absence of a reproducible test case, I don't think we can really do anything about this.

Note: See TracTickets for help on using tickets.