Upgrade issue multisite 4.4.10 to 4.5 Duplicate key segmentation fault
-
I am wondering if anyone has seen something like this before. I have a client who did not update their WP multi installation since 3.8. Now I’m trying to bring them to 4.8 after they were hacked (no surprise at all).
I am stuck at WP 4.4.10, an interim step to 4.5 or 4.6. I’m unable to get past 4.4.10 with a working site, and the only errors I can find are these:
WordPress database error Duplicate key name ‘meta_key’ for query ALTER TABLE wp_usermeta ADD KEY meta_key (meta_key(191)) made by wp_upgrade, make_db_current_silent, dbDelta
WordPress database error Duplicate key name ‘domain’ for query ALTER TABLE wp_site ADD KEY domain (domain(140),path(51)) made by wp_upgrade, make_db_current_silent, dbDelta
WordPress database error Duplicate key name ‘meta_key’ for query ALTER TABLE wp_sitemeta ADD KEY meta_key (meta_key(191)) made by wp_upgrade, make_db_current_silent, dbDelta
WordPress database error Duplicate key name ‘domain_path’ for query ALTER TABLE wp_signups ADD KEY domain_path (domain(140),path(51)) made by wp_upgrade, make_db_current_silent, dbDelta
These appeared first around the 4.2 release, with different tables. I did not find a problem going from 4.0 to 4.2 or 4.4 but could not make the jump to 4.6, eventually whittled it down to 4.4.10 as the newest release I can get working.
When I Upgrade Network on a 4.5 WP install, the site starts sending 500 errors to my dashboard. The apache logs contain the errors above, and every page load causes a seg fault like this:
[Tue Aug 01 17:57:24.984745 2017] [core:notice] [pid 20564] AH00052: child pid 20568 exit signal Segmentation fault (11)
I’ve tried a lot of different approaches to getting past 4.4.10, but nothing’s worked yet. I am fairly unfamiliar with Multisite, this is my first major update, so I may have made an error in a previous version. But, at 4.4.10 everything looks to be working very well.
Any insight would be most welcome!
- The topic ‘Upgrade issue multisite 4.4.10 to 4.5 Duplicate key segmentation fault’ is closed to new replies.