Many apologies to readers that this blog has been effectively out of operation for several hours. We haven’t been able to post articles; in fact I lost a very long one I’d been working on for over an hour, which made me very happy indeed. Readers also haven’t been able to post comments. There’s obviously a fairly major problem with Scott’s web host or MT setup, although I have no idea what it is. I’ve emailed him, but he’s probably still asleep (being a night shift worker).
I’m starting to get this nagging fear that Scott’s been so generous and taken so many refugee bloggers into the Ubersportingpundit empire that his entire system is grinding to a halt. I don’t quite know what to do, but it’s certainly not useable in its present state. Posts have been unbearably slow for the last couple of days. I’m actually starting to feel nostalgic about Blogger, believe it or not.
The rss feed has been working okay – sure it’s not something else? Anyway, hope it isn’t serious.
It was the MySQL database.
Not sure why it’s so slow though- it’s been it’s usual smooth self down this end.
It’s probably just God punishing you for posting nudie pix….I’ll check with Fred Nile.
It frequently takes up to 20 minutes or so for a post to appear after being uploaded (although occasionally it’s virtually instantaneous). I’m not having any problems posting material from my home to NTU webservers, even though it goes via Sydney or Melbourne with Bigpond, so I don’t think it’s anything at my end. I suspect it’s a problem with your webhost, Scott, rather than the MT setup. It’s very inconvenient, however, because I generally like to post an item and then preview and edit it after posting (because I find the MT preview function completely useless). However, I’m finding I invariably have to wait around for 15 or 20 minutes for the post to miraculously materialise so I can check, correct and edit it. As I say, maybe it’s a resource problem with just too many users trying to post at the same time. I guess I can revert to my old practice of composing in W.Bloggar, which has a much friendlier interface and preview function than MT anyway, but it’s still nice to be able to check a post on the web after it’s uploaded, just to make sure nothing went wrong.
test
The system also seems to have again reverted to its earlier fault of refusing to retain commenters’ personal details, even when the “Yes” radio button under “Remember Personal Info” is clicked
The only thing I noticed that went wrong was the style sheet disappeared, but I could read the site okay.
I’m with you on the previewing thing, Ken. I always post things first and then adjust them.
In the week I’ve been with UT I’ve never experienced any delay – previewing and posting have been instantaneous. Much better than Blogger in this regard.
Ubersportingpundit?!? Hah! Boo! Hiss! Raspberry!
For what its worth, apart from this morning, the post, preview and all other functions, with the exception of the personal info retainer, have been working perfectly at my end … although I think you’ve somehow gone and infected my home computer … which karked it this morning … and, boy, don’t come near me … I tell you what … @#$&*!
HEHE, Scott’s mysql database is becoming so large that it takes the server too long to search the index and gives all these errors.
Short term fix is to divide up the sites into seperate installations and use seperate mysql files for each division. We had a similar problem at dw.com but I had the database optimized and it appears to be much better now, although the CGI seems to sometimes get a little screwy.
Ideally, if USP is be kept running at 100%, you need to start implementing things to ease the load on the server.
Also, DAMN YOU WICKSTEIN!!!!!!!!!!!!!!!
Ken, some of us prospective tenants of UT are still only in the process of packing boxes and calling the removalists, and as such are barely even registering a presence over at Scott’s yet.
So I don’t think your new neighbours are to blame for any technical problems you may be experiencing?
Gianna,
Bailz’ post above rather suggests that the problems ARE all related, and indirectly spring from the number of users and therefore increasingly large and unwieldy size of the MySQL database. Apparently Bailz had similar problems as he added extra users, and had to reconfigure his database. Thus the problems are real and significant (and extremely inconvenient let me tell you), but solvable.
Everything is related. There is no spoon.
It’s all a MySQL problem, although MySQL is still far superior to the old Berkeley Database system.
The error stems from the fact that MySQL databases are stored on a seperate server to the websites, not often as “cutting edge” as the webservers themselves.
As i say, feasibly the best idea is too break up the sites into seperate installations, presuming of course that scott can have more than one mysql database.
Yeah, I’ve got unlimited Mysqls…
They take a bit of tweaking- I think I will set it up so everyone gets their own. This will be a work in progress. The people this affects will hear from me soon..
Yeah, scott, you can set it up so that each site has it’s own mt.cfg, just rig it so that all the scripts are universally shared (stupid to have X number of copies of the same .cgi file), but each site has a seperate mysql database.
DW.com is currently run on one database, mainly because I don’t have unlimited numbers, but since I had it optimized it’s been running slightly faster.
oh, DAMN YOU WICKSTEIN!!