Opened 9 years ago

Closed 9 years ago

#49050 closed defect (fixed)

El Capitan Installer takes 30+ minutes to run because there is no server-side portindex

Reported by: davidfavor (David Favor) Owned by: admin@…
Priority: High Milestone:
Component: server/hosting Version: 2.3.4
Keywords: elcapitan Cc: ryandesign (Ryan Carsten Schmidt), help@…, rohall@…, ady.romantika@…, lpancescu (Laurențiu Păncescu)
Port:

Description

After upgrading to El Capitan I removed Macports (per guide) same as with all other upgrades.

Installing the MacPorts-2.3.4-10.11-ElCapitan.pkg runs for 10+ minutes with tcl8.5 spinning @ 100%.

Installer does finally complete + Macports appears to be installed.

Nothing shows up in Console out of the ordinary.

This is a new iMac with fast CPU, lots of memory, pure SSD drive.

Question is where the installer log file lives, so I can see what's causing this problem.

Attachments (1)

Installer-Log-2-Oct-2015.txt (2.3 MB) - added by davidfavor (David Favor) 9 years ago.

Change History (23)

comment:1 Changed 9 years ago by davidfavor (David Favor)

Previously, on this same machine, Macports Installer took <1 min for install.

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Component: portsbase
Port: port removed

comment:3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Maybe MacPorts was generating the portindex. You can check if that's the case by showing the installer's log window and turning on Show Everything. Joshua only just turned on server-side indexes for El Capitan in r140729. If the problem persists, maybe the server-side indexes aren't being generated properly.

comment:4 Changed 9 years ago by skymoo (Adam Mercer)

I'm just in the process of setting up MacPorts on a new El Capitan VM and the installer is taking a long time, looking at the logs it is indeed updating the PortIndex.

comment:5 Changed 9 years ago by davidfavor (David Favor)

Just started this process on another computer + install log shows installer hung (well, taking a long time) a the step...

PackageKit: ----- Begin install -----

Hopefully this helps.

comment:6 in reply to:  5 Changed 9 years ago by skymoo (Adam Mercer)

Replying to david@…:

Just started this process on another computer + install log shows installer hung (well, taking a long time) a the step...

PackageKit: ----- Begin install -----

If you switch the log over to show all details, instead of just errors, I imagine you'll see the PortIndex being generated.

comment:7 Changed 9 years ago by davidfavor (David Favor)

Full log, with show errors + progress turned on.

Oct  2 10:23:39 Davids-MacBook-Pro installd[374]: PackageKit: ----- Begin install -----
Oct  2 10:36:56 Davids-MacBook-Pro installd[374]: Installed "MacPorts" ()
Oct  2 10:36:56 Davids-MacBook-Pro installd[374]: PackageKit: ----- End install -----
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: Running install actions
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: Removing temporary directory "/var/folders/m8/pfy1dwlx6w37wmrn03_gvs1r0000gn/T//Install.71159ks4JDn"
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: Finalize disk "Macintosh HD"
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: Notifying system of updated components
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: 
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: **** Summary Information ****
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]:   Operation      Elapsed time
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: -----------------------------
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]:        disk      0.05 seconds
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]:      script      0.00 seconds
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]:        zero      0.00 seconds
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]:     install      798.41 seconds
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]:     -total-      798.47 seconds
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: 
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: IFDInstallController 30C5F430 state = 5
Oct  2 10:36:57 Davids-MacBook-Pro Installer[71159]: Displaying 'Install Succeeded' UI.

Changed 9 years ago by davidfavor (David Favor)

comment:8 Changed 9 years ago by davidfavor (David Favor)

Ah... I see "Show All Logs" is different.

Entire copy of all logs attached.

comment:9 Changed 9 years ago by davidfavor (David Favor)

It appears problem is that rsync failed on index refresh, so as you suspected, likely has to do with generating indexes + having them rsync'ed correctly.

comment:10 Changed 9 years ago by davidfavor (David Favor)

Update ticket when this is fixed + I'll destroy my Macports install + reinstall + update ticket with what occurs.

Last edited 9 years ago by davidfavor (David Favor) (previous) (diff)

comment:11 in reply to:  3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Component: baseserver/hosting
Owner: changed from macports-tickets@… to admin@…
Summary: El Capitan Installer takes 10+ minutes to runEl Capitan Installer takes 10+ minutes to run because there is no server-side portindex

Replying to ryandesign@…:

Joshua only just turned on server-side indexes for El Capitan in r140729. If the problem persists, maybe the server-side indexes aren't being generated properly.

Looks like this script is not automatically updated on the server that runs it. Josh sent an email to the Mac OS Forge administrator on October 1 requesting he manually update the script but we have not received a response.

comment:12 in reply to:  10 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to david@…:

Update ticket when this is fixed + I'll destroy my Macports install + reinstall + update ticket with what occurs.

There is no need to destroy or reinstall anything once this is fixed. You'll receive the server-side index automatically, once it exists, the next time you sync or selfupdate. Until then, your syncs and selfupdates on El Capitan will just take a little while longer since your local machine will have to add any new or changed ports to the index, and as you already noticed fresh installs will take a lot longer since the entire set of ports has to be added to the index.

comment:13 Changed 9 years ago by help@…

Cc: help@… added

Cc Me!

comment:14 Changed 9 years ago by rohall@…

Cc: rohall@… added

Cc Me!

comment:15 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Has duplicate #49309.

comment:16 Changed 9 years ago by ady.romantika@…

Cc: ady.romantika@… added

Cc Me!

comment:17 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Priority: NormalHigh

For some users, it's more like 30 minutes to generate the index. Natually, users don't expect running the MacPorts installer to take that long; some users cancel the installation before the index is generated, thinking the installation has hung. We really need a server side index for darwin 15.

comment:18 Changed 9 years ago by lpancescu (Laurențiu Păncescu)

Cc: lpancescu@… added

Cc Me!

comment:19 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Summary: El Capitan Installer takes 10+ minutes to run because there is no server-side portindexEl Capitan Installer takes 30+ minutes to run because there is no server-side portindex

Has duplicate #49491. Edit: not a duplicate after all.

Last edited 9 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:20 Changed 9 years ago by lpancescu (Laurențiu Păncescu)

I switched to a local mirror as a workaround to the network problems described in bug #49452. The rsync-ing was very fast, but the lack of an index made mirror switching pretty annoying: the first "port selfupdate" thinks that every single port is new, and rebuilds the entire index (I ran it with the -v option, so I could actually watch it adding all 27000+ ports and subports, one by one). So mirror users on "El Capitan" currently have to wait 30+ minutes for the index to build not once, but two times. I have filed bug #49498 with the technical details.

comment:21 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: elcapitan added

comment:22 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

I updated the server's copy of the mprsyncup script so that it will generate a portindex for darwin 15, and it has completed its first run so the index for El Capitan is now there and will be updated with the others.

Note: See TracTickets for help on using tickets.