smf_sessions.MYI - Permanent fix?

[phil_roy]

SMF Version: SMF 1.1 RC2
Hi all,

I've just migrated my site from phpBB to a Joomla bridged version of SMF. Less than 24 hours into the forum being up, I discovered my site was down due to the error...

smf_sessions.MYI' (errno: 145)

Searching these forums meant I found a quick solution (a table repair) but phpBB had an issue like this as well...the option was to repair the sessions table whenever the problem occurred, but then someone also wrote a small hack that fixed the problem on the fly during regular forum use.

I guess my worry is that if this has happened after less then 24 hours, how often is it going to happen and is there a permanent fix that solves the issue? I can't find anything like that in the forums here.

I'm not on a dedicated server and do not have root access to it I believe. If you need some more info here is the status results attached. Any advice welcome, but I'll probably be able to do little to alter the server. I also had to turn GZIP compression off on Joomla as it was causing issues with Opera browsers for some odd reason. Compression on the forum is switched off.

Cheers,

Phil

Basic Information
March 27, 2006, 04:42:59 PM

Operating System:
Fedora Core release 1 (Yarrow)

Processor:
IntelÆ Xeon(TM) CPU 2.80GHz (2799.306MHz)

Load averages:
1.74, 2.01, 2.49

Current processes:
230 (227 sleeping, 3 running, 0 zombie)

Processes by CPU:
httpd (53) 35.3%, mysqld (43) 8.0%, python (9) 2.1%, named (1) 1.0%, (other) (48) 1.3%

Memory usage:
95.966% (1991624k / 2075352k)
Swap: 0% (0k / 2048276k)

MySQL processes

Total processes:
2 (1 sleeping, 1 running, 0 locked)

MySQL Statistics
MySQL 4.1.x

Connections per second:
2.5204

Kilobytes received per second:
16.0422

Kilobytes sent per second:
152.6823

Queries per second:
97.2896

Percentage of slow queries:
0.0001

Opened vs. Open tables:
(table_cache)
1.4235 (should be <= 80)

Table cache usage:
(table_cache)
0.946 (should be >= 0.5 and <= 0.9)

Key buffer read hit rate:
(key_buffer_size)
0.003 (should be <= 0.01)

Key buffer write hit rate:
(key_buffer_size)
0.0866 (should be <= 0.5)

Thread cache hit rate:
(thread_cache_size)
0.005 (should be <= 0.05)

Thread cache usage:
(thread_cache_size)
0.1641 (should be >= 0.8 and <= 0.9)

Temporary table disk usage:
(tmp_table_size)
0.5043 (should be <= 0.5)

Sort merge pass rate:
(sort_buffer)
0 (should be <= 0.001)

Query cache enabled:
(query_cache_type)
1 (should be >= 1 and <= 1)

Query cache miss rate:
(query_cache_limit)
0.158 (should be <= 0.1)

Query cache prune rate:
(query_cache_size)
0.1413 (should be <= 0.05)

[Fizzy]

Hi Phil,

As I recall I have only had this 145 error happen to me personally twice in the last 5 years or so. That was as a result of a server crash each time. I know it may not be the answer you are looking for (and you suggestion is actually a very good one) but it sounds like your host is having some stability problems.

As a solution though, could you set a cronjob to repair your tables every so often?

[Ben_S]

Admin > Server Settings > Feature Configuration > Automatically fix broken tables

[phil_roy]

Ben_S, that settings is (and was) on when the error occurred ??

Phil