By varmaduchi on

We're running a 4.7 drupal website with about 100,000 visits daily.

Last night we seemed to have a server problem that our host is still investigating.

Our server was rebooted, but our website is still either timing out, giving mysql errors involving the cache table or coming up to a blank page.

I can get root access, but can't get into phpmyadmin to repair the cache table.

Actually, I just got into phpmyadmin and tried to repair the cache table and the error message said not enough memory.

I can't get into root access anymore because it is timing out.

Looking for anyone with the experience to help out.

Please contact me through my drupal profile.

Thanks,
Nick

⋅ Categories: Drupal 4.7.x

Comments

varmaduchi’s picture

varmaduchi commented

Table Op Msg_type Msg_text
xomba.cache repair info Found block with too small length at 16394660; Skipped
xomba.cache repair info Wrong block with wrong total length starting at 58127404
xomba.cache repair info Wrong bytesec: 248-152-190 at 63165160; Skipped
xomba.cache repair error Not enough memory for blob at 66853188 (need 927867886)
xomba.cache repair info Found block with too small length at 16394660; Skipped
xomba.cache repair info Wrong block with wrong total length starting at 58127404
xomba.cache repair info Wrong bytesec: 248-152-190 at 63165160; Skipped
xomba.cache repair error Not enough memory for blob at 66853188 (need 927867886)
xomba.cache repair status Operation failed

coreyp_1’s picture

coreyp_1 commented

1. BACK UP YOUR DATABASE if you haven't already done so.
2. Try running the update.php file. Even if you don't have any updates to apply, when you run the upgrade script and click "Upgrade", it should clear the cache table for you.

- Corey

bmcmurray’s picture

bmcmurray commented

If your website is down or timing out, you probably won't be able to access update.php to run the script. Since you have phpmyadmin access, however, you can EMPTY (note: not DROP) the cache tables from your database to clear them out. You may need to also check to see if your database might be getting too full if your cron isn't running or isn't running often enough (watchdog is notorious for filling databases if not managed carefully with cron clean-ups).

--
B. McMurray

--
Brian McMurray

snufkin’s picture

snufkin commented

similar occurred to me, in that case the mysql binary logs ate all my free space. Your provider should check that, and as it was said previously: BACK UP THE DATABASE!

varmaduchi’s picture

varmaduchi commented

Thanks guys.

Don't worry we have nightly backups.

Everything is fine now.

Statistics module seemed to be causing lots of problems.