Skip to main content
10 events
when toggle format what by license comment
Jul 31, 2012 at 8:06 comment added Mike @arjan Thanks for your help. Converting to InnoDB solved the crashes for the most part and it seemed that the hosing was causing some of the other problems. We converted some tables to innoDB and changed the hosting and it is running fairly well now.
Jul 31, 2012 at 8:04 vote accept Mike
Jun 8, 2012 at 17:54 answer added Charlie Schliesser timeline score: 1
May 15, 2012 at 13:31 comment added Mike Thanks, I'll give that a try and post back here when I have some more information. Thanks for your help :)
May 14, 2012 at 15:53 comment added arjan I'm no expert in this area, but I would say this is most likely due to your server configuration (e.g. running out of disk space, connection to DB-server timed out), rather than a problem with Drupal (custom) modules. So you should also check the MySQL and other server logs. But converting write-intensive tables such as sessions (perhaps even all tables) to InnoDB seems like it's worth a shot (see this for example).
May 14, 2012 at 11:04 comment added Mike Yes, it does. REPAIR TABLE does solve the problem temporarily. The time it takes for the table to crash again varies. All the tables are MyISAM and I found out I might be able to solve it by converting the table to InnoDB or perhaps or adding the following code to my /etc/my.cnf file : [mysqld] myisam-recover=backup,force . But both of these solutions seem more like patches instead of fixes?
May 14, 2012 at 0:33 comment added arjan So does the problem reoccur after doing REPAIR TABLE 'sessions' (or 'repair table' option in phpMyAdmin)? (edit: should be backquotes around sessions, markdown filter)
May 8, 2012 at 2:15 history tweeted twitter.com/#!/StackDrupal/status/199683858122285058
May 7, 2012 at 13:41 history edited Mike CC BY-SA 3.0
added 34 characters in body
May 7, 2012 at 13:09 history asked Mike CC BY-SA 3.0