I have had this happen. I had to enable wildcard DNS.
All of my blogs work currently under 3.0.5 as subdomains. So I’ve got wildcard DNS setup. Do you mean there’s something within WordPress you had to actually configure differently?
Did you auto-upgrade or manual?
This is with the auto-upgrade. I’ve got about 9000 blogs so I’m a little scared to try the manual way.
The manual upgrade is, quite literally, copying files up via FTP 🙂 Actually probably safer than the auto at the end of the day.
I would try that.
and I wouldn’t have to worry about the network upgrade part of it?
Well no, you still have to do that, but maybe it’s not doing the network stuff because of an incomplete upgrade. Hard to say.
9000? Are they all real, legit, blogs? Maybe it’s time to prune the splogs…
ok, I just tried updating manually and still no luck. Getting the same error. Please, any way to see this in the logs to track down what the error is? I’ve got full reporting on my php error logs and nothing helpful is going in there. I really want to get my blog network up to date.
p.s. – This blog network is 5 years old, yes there are some blogs that could be pruned but for the most part they’re legit. I’m working on getting everything up to date so it’s easier to maintain at this point.
Rename your plugins folder to plugins-old
Rename your mu-plugins folder to mu-plugins-old
Try the network upgrade/
I missed the mu-plugins folder before so I got excited there. But it failed out with the same error again 🙁
When you get that error, you should be getting the URL that they can’t access. Try going to that URL in your browser and you’ll probably not be able to connect.
To fix it, go into your Network Admin -> Sites panel, find that URL and edit it. Change the URL to something that works.
Usually this happens, in my experience, with domain mapping in which the domain no longer works or no longer points to the WordPress install.
In your case it’s probably failing on the second blog.
Hey Everyone,
It’s failing on the 80th or 81st or 82nd blog, I can’t tell but it’s on the 80 page. The problem is it’s not actually displaying the blog name for me to try and troubleshoot the case. Is there any way for me to have wordpress spit out any and all errors instead of suppressing them as it looks to be doing? I don’t see anything in my php error logging and the page doesn’t display a url on fail. 🙁
This is interesting, in the 3rd post Caroline describes telling wordpress to repair database tables. I’ve never seen that option in WordPress but it could definitely be worth a shot. Is that a plugin maybe I’m not aware of?
http://wordpress.org/support/topic/getting-error-warning-problem-updating?replies=12
It was either a plugin or they went into phpmyadmin to do it.
It’s failing on the 80th or 81st or 82nd blog, I can’t tell but it’s on the 80 page.
Then skip that page. Look at the generated URL, it has a number at the end. change it by 5.
