richardpeters

Ok chaps (sorry for all the updates but saves being given advice that is now superseded),

I’ve spoken to my host and they have now manually unsuspended my DB and the 1142 ERROR is gone it would appear.

So I’m now left with the query of how to put back the wp_commentsmeta table, as per the post one up from above.

Many thanks!

Also, even with this table deleted and my database only half the limit size, I am STILL getting an 1142 INSERT error when trying to optimize tables or create a new admin user!?

Morning,

Ok so after deleting all content form wp_commentsmeta the size was still 76mb. So, I just want to check I’ve got this right before I do the next step:

1) I backed up the DB
2) I backed up JUST the wp_commentsmeta table
3) I dropped the table (it free’d up the much needed 76mn finally)

Can I know just go and re-import the backup of the wp_commentsmeta table or do I need to do something else to put that table back in?

Many thanks
Richard

Thanks Ross.

I’m basically getting the 1142 INSERT error on any table I try to optimize, even when doing them one by one and small ones first.

I’ll try dropping the wp_commentsmeta table I guess as that’s the one causing the problem and it’s not even got anything in it now anyway! I’ve got a back up of that table specifically that I just did, so I’ll see how it goes!

I’ll give this a go a little later and report back…fingers crossed!

Hi Ross, thank you for the reply.

I’ll go through and try that. I had already optimized the entire table in one go, which came back with this yellow warning (the same as when trying to create a new user).

https://i473.photobucket.com/albums/rr95/richardpetersphotography/DB_zps8bf22ce5.jpg

Also, you can see that wp_commentsmeta is where all the size is being eaten up. Originally it had 6000 or so records. I deleted them but now despite saying ZERO records, it is remains 76mb in size even after optimizing.

I can’t download any plugins right now as I have lost admin rights – which was why I was trying to create a new user in the DB, when I discovered the bigger problem ??

Hi all, after more investigation, it appears that my hack has coincided with running out of space on the database which could be causing the INSERT problem?

My hosting allows 150mb database and from within the DB itself it says the size is 149.3 MiB

So, assuming the access denied issue above is due to the DB being full, can anyone explain how I clear out the old post revisions etc to free up space. The issue being, with no admin rights, I can’t install a plugin to do it so must do it at database level…and I’m not an database expert ??

Sorry attempt to embed screen grab didn’t work, here’s the link to it
https://i473.photobucket.com/albums/rr95/richardpetersphotography/MySQL_zps43b0dabc.jpg

Hi Evan,

Thank you for the reply and please accept my apologies for the slow reply. I haven’t had time to address my site issues since I posted this so have only got round to fixing today!

Through some googling, I discovered the issue was my admin account had lost it’s admin rights and I was able to regain access to the site by creating a new admin account in MySQL.

It would appear I have now been able to update the database and get out of the stuck loop I was in.

However, my theme has lost all of it’s customisation in the process so I need to figure out what the issues is there now!

Thanks buddy. I’ve read most of those links several times before, but I’ll go over it all again when I land back in the UK.

Thanks again, appreciate the reply!

Thank you James, appreciate you replying. I’ve deleted the content of that folder now.

Thanks webjunk, appreciate the reply. As an aside, my theme is a paid theme, not free. Although I doubt that makes any difference?!

I’ve replaced all the server side .php files with clean ones and an initial check would suggest they are still clean. Before I re-installed yesterday, the source code and masses of extra code at the top of the page but that is all gone now. I’ve also changed all my passwords and the featured content gallery that I have on the blog home page, which stopped working when the hack kicked in, is also working again now.

So I’m keeping my fingers crossed that I’m clean again, for now!

Guys, just one last bit of info. Remember how I said in my first post that many of the fresh files I was re-uploading, where reverting back to a modified date of that at the time of the hack?

Well I’ve just logged in to my ftp again, and all the fresh files now report the correct modified date i.e. the time that I re-uploaded them!

So it would appear that I am in fact clean again?

Still appreciate any thoughts though on the previous post with the code I mentioned, or any other thoughts as to why the modified times changed!

Thanks again.

I’ve just run that and it came back with a few results, although I understand it can return false positives.

For Level Severe it came back with 4 warnings:
wp-content/uploads/js_cache/tinymce_80806e63a3f51b917a6b6ee9d5fd76c1.js:36

Which contained this huge bit of code.

Plus this:
wp-content/plugins/twitter-goodies/jscolor.js:78
Which contained
eval('prop='+m[3]);

wp-content/plugins/featured-content-gallery/scripts/mootools.v1.11.ext.js:3
and
wp-content/plugins/featured-content-gallery/scripts/mootools.v1.11.js:3
which both contained
eval(function(p,a,c,k,e,d){e=function(c){return(c<

Then under Level Warning I got 23 returns but the top two were:
wp-content/uploads/js_cache/tinymce_80806e63a3f51b917a6b6ee9d5fd76c1.js:36
){v=a[i];if(v==34||v==38||v==60||v==62)continue;l[String.fromCharCode(a[i])]=a[i+1];v=parseInt(a[i]).toString(16);re

And this one, which contained another huge bit of code:
wp-content/uploads/js_cache/tinymce_80806e63a3f51b917a6b6ee9d5fd76c1.js:802
Link to big bit of code.
There were more but they were the main ones.

Does any (or all?!) of that look like something that shouldn’t be there?

Again thank you. Being a bit of a novice makes it hard to know what I’m looking at ??

Thanks so much for all the replies everyone. I re-upload wordpress and theme files after every hack.

This was the first hack since moving to wordpress 3.0.1, I upgraded to that after the last hack.

THanks for the tip about looking at php codes on the server but I’m not entirely sure how to go about doing that, I’ll google it and see if I can make some sense out of it (server side stuff all seems a bit complicated and easy to break things…!).

I’ll look in to the password thing as well, thank you.

Cool thanks, here’s the source code.