[support] Errors showing on 5.16 site, was fine this afternoon

[Jamie Holly]

It's one of those things that just happen. There's nothing from the 
Drupal end that causes it, but rather something happening in the MySQL 
server or even hardware. One of the biggest culprits is an improper 
shutdown of the MySQL server (ie: hard reboot/power outage).

Clearing the table  usually won't fix it. It just ends up repeating the 
error since it can't update the index file. You need to do the repair 
table command.


Jamie Holly
http://www.intoxination.net 
http://www.hollyit.net



Neil Coghlan wrote:
> Jamie,
>
> thanks.
>
> How would that happen normally? Just from the date being entered into it 
> during the normal course of operations?
>
> Will emptying the table, as I've done, solve it permanently?
>
> Neil
>
>
> ----- Original Message ----- 
> From: "Jamie Holly" <hovercrafter at earthlink.net>
> To: <support at drupal.org>
> Sent: Tuesday, April 21, 2009 8:38 PM
> Subject: Re: [support] Errors showing on 5.16 site, was fine this afternoon
>
>
> > One of the index files used my MySQL became corrupt. From PHPMyAdmin or 
> > the MySQL command line, run:
> >
> > REPAIR TABLE cache;
> >
> > That usually fixes it.
> >
> > Jamie Holly
> > http://www.intoxination.net http://www.hollyit.net
> >
> >
> >
> > Neil Coghlan wrote:
> >> I just went to my D5 site and everything looked perfect. I logged in and 
> >> was confronted with this on a white sql error page:
> >>  Warning: Incorrect key file for table './mysite_drupalENG/cache.MYI'; 
> >> try to repair it query: UPDATE cache SET data = 
> >> 'a:959:{s:13:\"theme_default\";s:7:\"mysite\";s:13:\"filter_html_1\";s:1:\"1\";s:18:\"node_options_forum\";a:0:{}s:17:\"menu_primary_menu\";i:2;s:19:\"menu_secondary_menu\";i:2;s:15:\"install_profile\";s:7:\"default\";s:17:\"node_options_page\";a:1:{i:0;s:6:\"status\";}s:12:\"comment_page\";s:1:\"0\";s:14:\"theme_settings\";a:1:{s:21:\"toggle_node_info_page\";b:0;}s:18:\"drupal_private_key\";s:64:\"fe2614ccf5c885bad6bc60bba920218c7b8de0e65a0ae6fef45fad4332c104cf\";s:19:\"file_directory_temp\";s:3:\"tmp\";s:9:\"cron_last\";i:1240350721;s:9:\"site_name\";s:7:\"mysite\";s:9:\"site_mail\";s:21:\"webmaster at mysite.com\";s:11:\"site_slogan\";s 
> >> <mailto:webmaster at mysite.com%5C%22;s:11:%5C%22site_slogan%5C%22;s>: in 
> >> /home/mysite/public_html/includes/database.mysql.inc on line 174
> >>  Warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysitec/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysitec/public_html/includes/bootstrap.inc on line 569
> >>  Warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysitec/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysitec/public_html/includes/bootstrap.inc on line 570
> >>  Warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysitec/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysitec/public_html/includes/bootstrap.inc on line 571
> >>  Warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysitec/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysitec/public_html/includes/bootstrap.inc on line 572
> >>  I went in the db and emptied accesslog, watchdog and all the cache_X 
> >> tables.  That allowed me to log in but the first page I saw, this was at 
> >> the top:
> >>  * warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysite/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysite/public_html/includes/common.inc on line 141.
> >>     * warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysite/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysite/public_html/includes/session.inc on line 96.
> >>     * warning: session_regenerate_id() [function.session-regenerate-id]: 
> >> Cannot regenerate session id - headers already sent in 
> >> /home/mysitec/public_html/includes/session.inc on line 99.
> >>     * warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysite/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysite/public_html/includes/common.inc on line 141.
> >>     * warning: Cannot modify header information - headers already sent by 
> >> (output started at 
> >> /home/mysite/public_html/includes/database.mysql.inc:174) in 
> >> /home/mysite/public_html/includes/common.inc on line 141.
> >>  the site is 5.16 and I was on it this afternoon and all was fine. It 
> >> seems OK now, but I'm aware that there is a problem and want to get to 
> >> the bottom of it.
> >> Any clues as to what this could be? Interpreting Drupal error messages 
> >> was never my particular strong point. :-)
> >>  any help appreciated
> >>  regards
> >>  Neil
> >> ------------------------------------------------------------------------
> >>
> >> --
> >> [ Drupal support list | http://lists.drupal.org/ ]
> > --
> > [ Drupal support list | http://lists.drupal.org/ ]
> > 
>
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
>