My site is down, database error

I've got that not again feeling.

Not sure if anyone is working on my site, I've not been told, looks like my site has been down since 6.26pm.

I've got this error:

Query:

SELECT * FROM `sys_banners` WHERE `Active` <> 0 AND `campaign_start` <= NOW() AND `campaign_end` >= NOW()  AND `Position` LIKE '%2%' ORDER BY RAND() LIMIT 1

Mysql error: Can't create/write to file '/tmp/#sql_2318_0.MYI' (Errcode: 28)

Found error in the file '/home/admin/public_html/inc/banners.inc.php' at line 44.
Called 'db_arr' function with erroneous argument #0.

Not sure if you need to see the rest.

Is this to do with the template?

Check your /tmp directory and see if the permissions are set to 777

Mysql error: Can't create/write to file '/tmp/#sql_2318_0.MYI' (Errcode: 28)

Ok cool, I'll change everything to 777

are you with tmd?

 What's this?

 I've changed everything to 777, hasn't worked.

Anything else?

 don't worry, it's the hosting company i'm with and my site went down about the same time as well so i thought it might be the same thing

If you are referring to the /base and /tmp_* folders within the /templates directory, yeah.. umm you might wanna check to see if anyone is working on (or screwing with) your site. Those just don't disappear.

I know it sounds crazy, but you are checking your 'live' site via FTP/cPanel right? I have seen where some were actually looking ion the wrong place before.

I'm now getting this sort of query:

Query:

SELECT `bx_photos_main`.`ID` as `medID`, `bx_photos_main`.`Categories` as `Categories`, `bx_photos_main`.`Owner` as `medProfId`, `bx_photos_main`.`Title` as `medTitle`, `bx_photos_main`.`Uri` as `medUri`, `bx_photos_main`.`Desc` as `medDesc`, `bx_photos_main`.`Tags` as `medTags`, `bx_photos_main`.`Date` as `medDate`, `bx_photos_main`.`Views` as `medViews`, `bx_photos_main`.`Status` as `Approved`, `bx_photos_main`.`Featured` as `Featured`, `bx_photos_main`.`Rate` as `Rate`, `bx_photos_main`.`RateCount` as `RateCount`, `bx_photos_main`.`Ext` as `medExt`, `bx_photos_main`.`Size` as `medSize`, `bx_photos_main`.`Hash` as `Hash`,  COUNT(`share1`.`ID`) as `Count`,  `sys_albums`.`ID` as `albumId`, `sys_albums`.`Caption` as `albumCaption`, `sys_albums`.`Uri` as `albumUri`, `sys_albums`.`AllowAlbumView`, `sys_albums_objects`.`obj_order`
                     FROM `bx_photos_main`
                     LEFT JOIN `bx_photos_main` as `share1` USING (`Owner`)
                     
                INNER JOIN `sys_albums_objects` ON `sys_albums_objects`.`id_object`=`bx_photos_main`.`ID`
                INNER JOIN `sys_albums` ON (`sys_albums`.`ID`=`sys_albums_objects`.`id_album` AND `sys_albums`.`Type`='bx_photos')
            
                     WHERE `bx_photos_main`.`Uri`='DSC033213' GROUP BY `share1`.`Owner` LIMIT 1

Mysql error: Can't create/write to file '/tmp/#sql_2318_0.MYI' (Errcode: 28)

Found error in the file '/home/admin/public_html/inc/classes/BxDolFilesDb.php' at line 286.
Called 'getRow' function with erroneous argument #0.

 So you had to change this to 777 (meaning it wasn't this before)?

You can manually clear the /cache. /cache_public, and /tmp directories via FTP (EXCEPT for the .htaccess files). 

Yeah, was checking in the wrong place, they're fine.  Getting a little worried though.

I'm getting those two errors above, repeated, every minute.

Do you need anymore of the error?  I've just copied & pasted the top part.

Umm.

You all are looking at the wrong folders. This error.

Mysql error: Can't create/write to file '/tmp/#sql_2318_0.MYI' (Errcode: 28)

Is from the mysql storage engine. It's the servers tmp folder. Not dolphins. It is normally caused by low hard drive space on the partition /tmp is mounted on.

Contact your host.

Good catch Deano..

EDIT: I was in the process of pulling up that exact error code and you are correct.

how strange is that, that's just what i was getting at exactly the same time as you but with a different hosting company, according to my hosting company the problem was an incorrect rewrite rule within the .htaccess file, don't know how that happened as i don't touch them but that's what they said, hopefully it's the same thing for you

Not likely. That exact error cannot be caused by anything in the htaccess file.

 to be honest, i haven't got a clue, but that's what they told me, looks like i'll be ordering a Z800 sooner than i had originally planned 

does the set up fee include site transfer 

I don't think it's to do with disk space:

ftpd	up
imap	up
nginx	up
cpsrvd	up
named	up
Server Load	0.30 (4 cpus)
Memory Used	15.3 %
Swap Used	9.52 %
Disk /dev/sda3 (/)	4 %
Disk /usr/tmpDSK (/tmp)	31 %
Disk /dev/sda1 (/boot)	9 %
Disk /tmp (/var/tmp)	31 %
Disk /dev/sdb1 (/mnt/disk1)	0 %

If you would like to ask more questions regarding Zarconia, feel free to send me a PM or you can start a new topic since this would be a different discussion and don't want to 'hijack' this one (hehe). But to answer your question, yes we will move your site :)

I can't even log into my admin panel, although it does show up, unlike the site.

We are going to need to know the site address either via PM or here. If it's an adult site, please state that too.

Message sent.  Cheers!

First of all, what do you mean everything?  You should not have changed everything.  You have to do this stuff like a surgeon; you were not told to change everything.  What did you change to 777?

It could be your tmp directory is full and thus it can not write to the tmp directory.

I want you to stop doing anything at this time.  With all due respect, you don't have the skills to handle this.  Just sit and wait a bit.

Exactly that, using FTP, and all sub-folders, just to make sure.  It sounded like a solution.

Now I am sitting back.

You misunderstood what they were telling you.  Also, in this case the /tmp folder is not the one in Dolphin but the server /tmp folder that mySQL uses.  If you just changed the Dolphin tmp folder to 777, then no big deal.  However, at this point I have no idea what you did with the permissions but they can be fixed later.

I was able to log into your control panel.

I mentioned that.

Then he replied he does not think so. What he does not realize is that the server /tmp folder is a scratch space for the server and how much data is in it is in constant flux. Also the size is not mentioned. 31% of what?

Also not listed there are a thing linux has called inodes. Which if low will also cause a problem regardless of how much space it says is available.

Does not matter. The error code is quite specific and is a server issue that needs to be taken care of by your host.

Let's meet in that chat room if we can, we need to talk.

Well, I need to get in touch with someone else that helped with that server to ask some questions.  I am seeing a 7.5 meg file in the /temp folder.  The mysql.sock file is zero.  This is a WHM server so I need to walk around that as well.

He is his own host as this is an unmanaged server; I help him with the server and recently someone else has also helped.

Zarcon is currently looking at it.

I have messaged the host company to query the disk space as Dean mentioned.

I'm really having a bad time lately.

OK, I am in the chat, join me there.

You have an unmanaged server, they won't handle such things.

You'll have to link me that chat again, I've not bookmarked it.  Message me.

Sent

Mysql needs a lot of room to move. It may be writing a very large table. I can't imagine a table being 1gig in size but is possible. There also have to be a certain percentage of extra room.

If it was my server i would delete the contents of the /tmp folder and reboot the server. But that's just me.

@LikesDumbBimbos - Please let me know if you are getting anyone else to work on this. We don't want multiple people walking over each other or doing duplicate work.

GG had to use a special program to install the SQL.  I gather it is big.

Regarding this problem, no just you.

Yes, I assumed that the contents of the /temp could be dumped but wanted to make sure.  I took my site offline doing a backup that wrote to the /tmp and mySQL could not write to it.  One solution to make sure is to move where mySQL uses from the /tmp folder since that is used by many things.  I make sure to not download things into the /tmp folder; for software installs I do it in the /temp folder; similar but enough that I know that it is my temp folder for such things.

No, I am hands off but if you need to talk to me in real time I can PM the chat room we are using.

 Could this do the job Zarcon?

 It's possible but first need to find out what is causing the database errors. Currently looking into this. Hang tight.

Website is back online.

Summary:

The issue resided in the /tmp folder. Clearing the /tmp folder and restarting MySQL seemed to do the trick.

To prevent this from happening again and due to database size, the SQL temp files have been moved to the main partition of the drive instead of the /tmp folder. A job was added to then clear any files that have not been used in 48 hours.

Special 'Thank You' to my Zarconia co-partner Nathan for his assistance.