Keep backups! That's my foremost thought.
My second thought is to fill out that survey form.
My third thought is: GoDaddy just cost you three days of downtime and income! Surely that should be worth something off your hosting costs. Either that, or it's worth considering moving to a more reliable host.
It seems to me they run some sort of automated weekly cleanup script. Either that, or they actually found a problem with your database and fixed it. Given their lackadaisical attitude thus far, I'm leaning toward automation.
Good grief! How frustrating this has been, for both of us. I'm glad it's resolved. Especially with your fantastic pictures!
"Query failed" instead of a Blog
-
Don Chambers
- Regular
- Posts: 3657
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
I missed this thread when it was originally posted.
2 of my s9y installs are on godaddy... I have also encountered unexplained problems that, despite their assurance that "its not our fault" are miraculously resolved a short time later. Either the left hand does not know what the right is doing there, or they are just covering their butts.
With regard to hudson-valley-dad, I merely ran a REPAIR TABLE on the entries table... no magic syntax to repair all tables in the database. What really stinks is that there is a phpmyadmin link for "repair" for uncorrupted tables, but corrupt ones do not have these links!!!! I had to issue the repair at the mysql command line! The repair link did not appear right where it was needed!!!
2 of my s9y installs are on godaddy... I have also encountered unexplained problems that, despite their assurance that "its not our fault" are miraculously resolved a short time later. Either the left hand does not know what the right is doing there, or they are just covering their butts.
With regard to hudson-valley-dad, I merely ran a REPAIR TABLE on the entries table... no magic syntax to repair all tables in the database. What really stinks is that there is a phpmyadmin link for "repair" for uncorrupted tables, but corrupt ones do not have these links!!!! I had to issue the repair at the mysql command line! The repair link did not appear right where it was needed!!!
=Don=
frustrating
Well after coming good a couple weeks ago, this weekend the blog went down again with this message:
Same message as last time. Same problem. I have waited a couple days to see if Monday morning brings it back up like last time, but no such luck yet. Go Daddy is NOT helpful at all on this, even with talking to them as others have said.
I am going to try this repair table thing, although I am hesitant, not knowing MySQL at all, and time to move to a different server, if anyone has any suggestions on server great.
e.id,
e.title,
e.timestamp,
e.comments,
e.exflag,
e.authorid,
e.trackbacks,
e.isdraft,
e.allow_comments,
e.last_modified,
a.realname AS author,
a.username AS loginname,
a.email
, e.body, e.extended
FROM
serendipity_entries AS e
LEFT JOIN serendipity_authors a
ON e.authorid = a.authorid
LEFT JOIN serendipity_entrycat ec
ON e.id = ec.entryid
LEFT JOIN serendipity_category c
ON ec.categoryid = c.categoryid
WHERE isdraft = 'false'
GROUP BY e.id
ORDER BY timestamp DESC
LIMIT 6
/ Can't create/write to file '/tmp/mysqltmp/#sql_880_1.MYI' (Errcode: 2)
Same message as last time. Same problem. I have waited a couple days to see if Monday morning brings it back up like last time, but no such luck yet. Go Daddy is NOT helpful at all on this, even with talking to them as others have said.
I am going to try this repair table thing, although I am hesitant, not knowing MySQL at all, and time to move to a different server, if anyone has any suggestions on server great.
e.id,
e.title,
e.timestamp,
e.comments,
e.exflag,
e.authorid,
e.trackbacks,
e.isdraft,
e.allow_comments,
e.last_modified,
a.realname AS author,
a.username AS loginname,
a.email
, e.body, e.extended
FROM
serendipity_entries AS e
LEFT JOIN serendipity_authors a
ON e.authorid = a.authorid
LEFT JOIN serendipity_entrycat ec
ON e.id = ec.entryid
LEFT JOIN serendipity_category c
ON ec.categoryid = c.categoryid
WHERE isdraft = 'false'
GROUP BY e.id
ORDER BY timestamp DESC
LIMIT 6
/ Can't create/write to file '/tmp/mysqltmp/#sql_880_1.MYI' (Errcode: 2)
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: frustrating
Hi!
The error is definitely related to the MySQL Server of Godaddy that seems to have a hiccup. My bet is, it will eventually resolve itself when godaddy restarts the server (usually automated at least weekly).
Godaddy support should have a look at this issue, though.
Regards,
Garvin
The error is definitely related to the MySQL Server of Godaddy that seems to have a hiccup. My bet is, it will eventually resolve itself when godaddy restarts the server (usually automated at least weekly).
Godaddy support should have a look at this issue, though.
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
The actual error:
It says "Can't create/write to file". If it had said "Error in SQL syntax", that would've been a blog problem. But it's the server's job to create and write files. Especially .MYI files, which is how MySQL stores its databases.
It's writing to /tmp. That's an absolute, global directory on a server somewhere. We always write to a directory somewhere in your account (unless you've misconfigured something somewhere). Someone could search every file in our code and never find a reference to /tmp; it's coming from the MySQL configuration.
It's trying to write or create a .MYI file. That's a MySQL database file. We don't ever manipulate the database files directly; we use PHP calls. (I'm not even sure we could manipulate those files directly. It would be such a stunningly awful idea that we would never let it in the code, in any case.) Only the MySQL server manipulates those files.
Although I can't see the actual MySQL command that was being executed, I'll bet it's a SELECT. MySQL doesn't have to write anything for a SELECT; it's a 'read' type of operation, not a 'write' type. The JOIN commands partway through the command mean that MySQL has to create a temporary database table, though; that's probably where the "create" part of the error comes from. Note that it's not the blog creating the file, though; it's the MySQL server. When the server can't create the file, something is badly wrong.
If you have access to phpMyAdmin (can't remember from earlier posts), go and try to execute a SELECT with a JOIN from its SQL tab. I'd try:
That should give you exactly the same problem, and since you're doing it from phpMyAdmin, it should be conclusive proof that the blog isn't causing it.
is the bit that tells us it's a server problem. There are several indicators, but here are a few:/ Can't create/write to file '/tmp/mysqltmp/#sql_880_1.MYI' (Errcode: 2)
It says "Can't create/write to file". If it had said "Error in SQL syntax", that would've been a blog problem. But it's the server's job to create and write files. Especially .MYI files, which is how MySQL stores its databases.
It's writing to /tmp. That's an absolute, global directory on a server somewhere. We always write to a directory somewhere in your account (unless you've misconfigured something somewhere). Someone could search every file in our code and never find a reference to /tmp; it's coming from the MySQL configuration.
It's trying to write or create a .MYI file. That's a MySQL database file. We don't ever manipulate the database files directly; we use PHP calls. (I'm not even sure we could manipulate those files directly. It would be such a stunningly awful idea that we would never let it in the code, in any case.) Only the MySQL server manipulates those files.
Although I can't see the actual MySQL command that was being executed, I'll bet it's a SELECT. MySQL doesn't have to write anything for a SELECT; it's a 'read' type of operation, not a 'write' type. The JOIN commands partway through the command mean that MySQL has to create a temporary database table, though; that's probably where the "create" part of the error comes from. Note that it's not the blog creating the file, though; it's the MySQL server. When the server can't create the file, something is badly wrong.
If you have access to phpMyAdmin (can't remember from earlier posts), go and try to execute a SELECT with a JOIN from its SQL tab. I'd try:
Code: Select all
SELECT
e.id,
a.email
FROM serendipity_entries AS e
LEFT JOIN serendipity_authors a
ON e.authorid = a.authorid
Not really patience, just a detached sense of "If I don't think about it I don't have to deal with it" We are in the middle of a large charter with ten guests and are sailing in some roughish seas, so being downstairs trying to make my cel phone connection hang on long enough for someone at Go daddy to actually help me, is not possible, so I wait for their email.
OMG. That sounds like my idea of Hell.
A friend once took me on a deep-sea fishing trip for my birthday. I chummed with my own breakfast, then, determined to have fun on my only birthday for the next four years, I resolutely took up a fishing pole.
I caught a shark. I don't even want to think about what he had been eating.
We wrote a song in the blues tradition, "The Deep-Sea Fishing Greens" on our way home. I've never been so happy to be on solid land.
To keep things on topic: your situation is a support nightmare. Unfortunately, accessing the account requires your password, and probably some other security info; otherwise I'd be happy to call them on your behalf.
A friend once took me on a deep-sea fishing trip for my birthday. I chummed with my own breakfast, then, determined to have fun on my only birthday for the next four years, I resolutely took up a fishing pole.
I caught a shark. I don't even want to think about what he had been eating.
We wrote a song in the blues tradition, "The Deep-Sea Fishing Greens" on our way home. I've never been so happy to be on solid land.
To keep things on topic: your situation is a support nightmare. Unfortunately, accessing the account requires your password, and probably some other security info; otherwise I'd be happy to call them on your behalf.
Sounds like you are definitely not a water baby, and there are some days that are not much fun, but lots of fun diving and looking at sharks!
Reply from Go Daddy today, at least acknowledging that it might be them and it came up again...
Thank you for contacting Online Support. The error in question is most likely due to the temp folder of the shared folder being filled for a time before being reset; if you would, please contact us by telephone at the time the error is happening so that we can verify it. Unfortunately I'm not able to duplicate the problem at this time. Please let us know if we can help you in any other way.
Reply from Go Daddy today, at least acknowledging that it might be them and it came up again...
Thank you for contacting Online Support. The error in question is most likely due to the temp folder of the shared folder being filled for a time before being reset; if you would, please contact us by telephone at the time the error is happening so that we can verify it. Unfortunately I'm not able to duplicate the problem at this time. Please let us know if we can help you in any other way.
They cleared it out before I even got the email response. Still, the entire thing is ludicrous. Hopefully this helps someone else when they have the same problem with Go Daddy. I think it could be a factor of as they are shared servers, once you start getting more popular, these things happen, I did not have them when my blog did not have that many hits.