Googling for that error indicates that it is a hosting issue. It’s certainly not reported here very often at all, so I’d email your host or look into other hosting options if it persists.
Thank you podz.
We have contacted our host and submitted a support ticket with them. We were just curious to see if this was a WordPress specific problem, seeing as other sites on our server can access mySQL just fine.
I will let you know what our host says as soon as we find out.
The problem has been fixed. Not sure what happened, as the host never contacted me back, but I didn’t change anything, so I can only assume they changed something on their end (or the problem fixed itself in the same way it broke itself).
Hope this doesn’t happen again…
I’m having this very same problem now (easternblot.net/blog) and I think it’s related to the MySQL memory of your host. I’m e-mailing mine now to see what’s going on.
I am having the same problem out of sudden at my blog (http://www.liewcf.com/wp/index.php). However, no problem to view permalink page.
I am getting this error as well now, and I run my own DB. heh, guess that’s what i get for trying to do it all myself. Guess I’ll keep googling to see what i can do to fix the issue…
ok, I found it. I got my solution from this post:
http://forums.xmbforum.com/viewthread.php?tid=743964
Yeah, I know it’s not about WP, but it turns out it’s a mysql/system issue, WP just happened to be the code that was trying to query the DB. Tthis was not a WP issue.
I was getting -1 error. I dumped my db to a file. I checked my tables, no errors. I repaired them just in case, no mention of anything fixed. I optimized cause I read it was a space issue. No avail. So I starting cutting off parts of the query, and even the basic select wasn’t working. But this time I was getting an error 28. “perror 28” will tell you “Error code 28: No space left on device”. (Btw, I couldn’t get perror to look up “-1”. It kept trying to use it as a flag.)
Finally a “df” helped me out. Turns out I was out of /tmp space. I cleaned out the extraneous files in there and voila, mysql started working like a champ. Didn’t even have to restart it.
I thought maybe others might be getting this issue, so I thought I would post my fix in hopes of helping other users like me who try to be DIYers.
Error code 28: No space left on device
Isn’t the error caused because WP generates thousands of files in cache. I supppose it makes the device full. Did anyone of you noticed enormous number of files in your cache/userlogins or cache/users or any cache directory??
