multisite wp-admin Internal Server Error displayed but 302 in logs after upgrade

  • Resolved s0medude

    (@s0medude)


    10 years, 1 month ago

    Hi all,
    I’m having a strange issue. After updating a multisite wordpress instance from 3.8 to 3.9.2. The multisite network only has 2 sites. For the purposes of this post, the original site lives at /someurl and is configured in wp_options. The second site lives at / and is configured in wp_2_options. Everything works great @ 3.8, but after upgrading the site to 3.9.2 the only way I can get to the admin console is by going to /someurl/wp-admin/ … attempts to access /wp-admin/ load for a bit and then the browser displays the “Internal server error” message. However, there are no 500 errors logged by the web server and there are no php errors logged either. There does seem to be a corresponding 302 logged for /wp-admin/ in the web server logs.

    I’ve tried all the usual items like disabling all plugins but still get the same results. I’ve also double-checked the siteurl & home options in the database and they all match what they should be. Without any errors being logged I’m at a loss for what could be causing this. Any help would be greatly be appreciated.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter s0medude

    (@s0medude)

    Update: to try and isolate the issue, I went back and upgraded each release in between and it breaks down between 3.8.2 -> 3.8.3. I didn’t pay strict attention, but I believe this may have been the first release after 3.8 that included a database update. I’m trying to compare the before and after DB snapshots and immediately notice a huge difference in the wp_options table. In 3.8.2 there were 10527 rows in the table, but in 3.8.3 there are only 306 rows in the table. At face value this seems like a massive decrease to me. Not sure if that’s expected or an indication that something has gone awry. wp_2_options remained constant @ 267 rows in the table.

    Thread Starter s0medude

    (@s0medude)

    Did some more digging the extra row in wp_options were mostly all transient ones that went away post-upgrade so I don’t think they are relevant. I then compared the changes to the table and the only one that jumped out at me as potentially relevant was rewrite_rules so I tried normalizing it to match it’s pre-upgrade state but that didn’t change the behavior. I also enabled query logging and called /wp-admin/ to capture the queries being generated and then compared the data returned from both the pre & post data sets. They return identical data so I’m not sure if the actual data is the issue vs. how something in the code is handling it. Anyone have any ideas?

    Thread Starter s0medude

    (@s0medude)

    I fixed this by running wp-cli.phar –url=https://my-multisite-url/ core update-db

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘multisite wp-admin Internal Server Error displayed but 302 in logs after upgrade’ is closed to new replies.