Thread

Thanks Sue. I have tried the upgrade in a local environment, dev environment on the production box, and in production.

Is there an error log created during the upgrade so I can track down the last successful/failed task?

I think my next test might be to disable all plugins and try the upgrade. Not sure if that’s totally safe.. but it should be, right?

Hi rwbaker,

Did all those test upgades fail in the same way? Yes, you can safely remove all plugins and then replace them once the upgrade completes successfully. However, other types of addons (extensions and modules) are more likely to cause issues. This failure though (right at the beginning of the upgrade process) suggests something more fundamental might not be configured correctly. Is your server self-administered or hosted with as a managed VPS? Are you able to go through a complete fresh install of version 2.1.3 on this same server (perhaps on subdomain)?

Cheers

Greg

Thanks Greg.

This is on a Linode 512mb ram VPS managed by our sys admin.

I installed a fresh version of 2.1.3 with no problem.

I pulled out backups of our 3-month-old dev site (v2.1.0 with all the same addons)—the latest version of dev right before we pushed our to prod.  Pulling custom fields (the original topic of this thread) worked fine in the dev site. I then did a diff of the file structure and come up with no core diffs (just diffs in new production uploads and cache folders).  This leads me to believe the problem is either in the DB or somehow related to file permissions.  Thoughts?

Where can I find a download of the 2.1.0 install and themes? I think I might try to install a fresh copy of 2.1.0, then rebuild the system piece by piece then switch to a copy of the production DB and try the upgrade from there.

Hi rwbaker,

Older versions of EE aren’t available for download, unfortunately. You mentioned the cache folders - did you try manually clearing that folder out (except for index.html) via FTP? Also, were members ever imported at any point?

I’ve tried cleaning the cache manually and disabling all addons—nothing seems to work. EE 2.1.3 and 2.2 updates fail the same way.

Members were never imported.

Is the 2.1.0 build available at all?  This EE install seems to be getting worse as time passes, old functions are starting to break that we haven’t touched in months, etc.  I think the best solution would be to setup a 2.1.0 install, move over the db, post-related files and add-ons, then upgrade that fresh install.

Hi, rwbaker -

We don’t keep older versions available, so that is, unfortunately, not an option.

Do you have an online, development environment that we would be able to access?  If so, I think it’s time for the support team to login and see if we can figure out what is going on.  If you do have such an environment, we’ll get you an email with instructions.

Thank you!

I was able to find 2.1.0 from the EE community. I moved over my prod data and was able to update to 2.2.0 without a problem.  You guys should seriously consider providing historic builds for exactly this reason.

Thanks for the help.

Hi, rwbaker -

Glad you were able to get up and running.  That’s an interesting perspective, and we are currently reviewing our download policies, so I’ll be happy to bring that up in our discussions.

Please post a new thread if you have any other questions.