Trying to narrow down the cause, but figure this forum is the best place to start.
Running Multi-Site and using the stock CBox theme for the front page. P2 Theme for the subsites below.
I logged into the back end today to make sure all was well. Found WP 3.5.2 upgrade offered, along with some updates to plugins and the P2 theme.
I did the upgrade for WP first and was told I need to update all the sites, so I accepted this option and did so. All was evidently OK until an error popped up saying one of the subsites couldn’t be updated. I believe it suggested I didn’t have sufficient rights to that site, which is odd because my account has control over everything. No other obvious problems, so I did the theme and plugin updates before poking into the single subsite problem.
I then noted that the admin area was dog slow. But the public side of the site remains as snappy as it ever was.
No load is noted on the server during the delays. It looks very much like a DNS timeout problem, where the server has no additional load but simply does nothing until the DNS officially fails… if you know what I mean. No errors that I can find, but I honestly don’t know where besides the typical Apache logs I should be looking. The delay is very close to a minute exactly and the browser simply shows ‘waiting for server’ during the delay. Once the connection with the server is finally established, the page populates as quick as ever.
I found a posting elsewhere discussing a similar symptom and note that the problem was tracked back to a routine that was attempting to notify the admin user of a new theme version. I don’t know if that’s possibly a clue here or not.
Any suggestions as to where I should be looking? I’m tempted to disable CBox and look to see what updates become visible… thinking perhaps one didn’t complete but isn’t visible through the CBox update controls.
I went in and re-did the WP update. Then did the ‘update network’. The error reappeared and is pasted in below, with some domain modifications to protect the innocent…
Warning! Problem updating http://blog.abcconsultants.ca/sitew. Your server may not be able to connect to sites running on it. Error message: couldn’t connect to host
Which is weird, because the sites are all physically on the same drive on the same multi-site install. Why this one is a problem I don’t know! I think it was the last site I created, but don’t think that should matter.
Is this likely to be a CBox issue, or purely WP? If WP, I should move my thread over there!
Any comments are appreciated.
Sounds like a WordPress problem. Though to be sure, try deactivating CBOX and then update the network to see what happens.
Do you have a large network of sites? Any errors in the server log?
I’m now thinking the issue is in the database somewhere. Given that the delay is much like a DNS issue, I’m wondering if a problem in the database could cause similar timeout delays. And if I’m right, you’d be right too – a WordPress problem! And even if I’m wrong, you’re probably still right… 😉 I’m thinking it’s a WordPress issue brought about by a glitch in the upgrade routine.
I did try deactivating CBOX and updating the network… same error.
Fairly small network. Besides the home site, I have a total of 5 additional sites underneath. No problems seen in the logs, but it’s possible I’ll have to work out how to make them more verbose before they’ll give me a proper clue.
In case it helps someone else, the solution is here:
It appears to be a WordPress issue with the database not updating the version number properly. I seem to be running smoothly again… 🙂
Glad to hear you figured this out!
Well…. this was not a one-off problem. The upgrade to 3.6 has caused the same issue. The strange thing is, it’s only happening on the site running CBOX. My other sites (one using BuddyPress, the other simple WordPress) upgraded just fine, as they have always done. It makes me wonder if there is something else going on to cause it. Given that the solution last time was to find the wp_options table and change the db version value to 22442 from 22441, I’m assuming I’ll be toggling to a new number. Perhaps 22443 but I have no way of knowing… although I suppose the obvious thing would be to find the value on one of the working sites.
Is it possible something in CBOX is blocking the change in the database? It’s a bit of a pain to manually poke around in the database – I’m not overly competent in that area!!
You must be logged in to reply to this topic.