The download failed with an EOF error shortly after I sent the email.
We did a huge ‘spring’ cleaning of all the roles/cookbooks before this last run, we had a lot of cruft that needed cleansing.
What’s odd is that the "chef-server-ctl chef12-upgrade-download”
command is just running a “knife download /“ behind the scenes, and that process used 100% of one CPU for the full 7 hours. It appeared to slow down over time, and I noticed that it opens/closes a new https session for every file it downloads.
In comparison, for
backups we’re using the knife backup plugin (I think from https://github.com/mdxp/knife-backup) and it can export the entire server in about 1.5 hours. We run a full backup every
night and a —latest every few hours. We’re still trying to figure out what the difference is and why one works and the other fails. And if there’s a difference in the data that they provide.
Thanks
Mike
—
Michael Hart
Arctic Wolf Networks
226.388.4773
From: Mark Mzyk
Reply-To: " "> " Date: Friday, March 6, 2015 at 08:58 To: " "> " Subject: [chef] Re: Re: Re: Chef Server 12 upgrade failure Having it on the same node is fine; that's the default case the upgrade process was designed for. Hopefully it all goes well this time. If it does not, let us know and we'll help you get it sorted. The upgrade is taking
as long as it is because the process is download all the data/transform it to Chef 12 format/upload all the data to a new server. The more data you have the longer it'll take (having many cookbook versions is a particular culprit here). It was done this way
so that all your data moved through the API so we could ensure it would be in a good format on the Chef 12 server. We recognized that this might take a while, which is why the chef12-upgrade-* commands exist to give you finer control over the process.
- Mark " type="cite"> |
Archive powered by MHonArc 2.6.16.