I just recently bought a new Dual Xeon server for my site, working great except MySQL keeps crashing, seems likes happening at least once a day. mysql crashes and does not come back up until I manualy start the service again.

I never see any error on my actualy phpnuke site: www.canadaka.net
but the same sequence of events happens in the mysql log file each time:

050314 9:14:07 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)
050314 9:14:07 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)
050314 9:14:07 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)
050314 9:14:07 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)
050314 9:14:07 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)
050314 9:14:07 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)
050314 9:32:26 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050314 9:32:26 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 276756.
InnoDB: Doing recovery: scanned up to log sequence number 0 276756
050314 9:32:26 InnoDB: Flushing modified pages from the buffer pool...
050314 9:32:26 InnoDB: Started; log sequence number 0 276756


I have never had this problem before, and after looking around on this forum and google, can't really come up with a reason or solution. these threads on nuke cops did not help:
http://www.nukecops.com/postlite36639-nukesession+myi.html
http://www.nukecops.com/postlite34980-nukesession+myi.html
http://www.nukecops.com/postlite30678-nukesession+myi.html

Each time I manual restart the mySQL server i think repair the nuke-sessions table and it seems to have no errros.

Anyother question is if there is a way to make mySQL automaticaly restart after it crashes? my site was down 4 hours yesterday becasue i wasn't there to restart it.

bump, still crashing :(

I really didnt feel like entering or even browsing your sites (personal reasons)..

But let me ask you a question, do you have any PHPBB forums installed, was there any PHPNuke updates you did not follow up with?

Peace,

yes of course there is a phpbb forum, it is built into phpnuke.
I am hosting more than one phpnuke site though (seperate database and was on old server as well)

the thing is that the site file and database were working fine on my old server, i just copied them to this new server

Originally posted by Canadaka
yes of course there is a phpbb forum, it is built into phpnuke.
I am hosting more than one phpnuke site though (seperate database and was on old server as well)

the thing is that the site file and database were working fine on my old server, i just copied them to this new server

Are the versions of your php .12, higher or lower?

Peace,

do you mean php or phpbb?

PHP Version 5.0.3
Mysql 4.1.10

Phpnuke 7.6
phpbb 2.0.11

ok I just upgraded my forum to phpBB: 2.0.13

last night i found some tables in the database were marked as "in use" and were missing there .myi files. just had .frm

i recreated the tables and the .myi files were made properly and the "in use" is gone

Originally posted by Canadaka
do you mean php or phpbb?

PHP Version 5.0.3
Mysql 4.1.10

Phpnuke 7.6
phpbb 2.0.11

I meants phpbb,

phpbb 11 have have a major bug in of which was fixed in 12. One of the bugs causes your server to overload (both mysql and httpd)..

Good you updated,

Peace,

hmm well after clearing out those "in use" table and upgrading phpbb it hasn't crashed in 24 hours. but im still not sure if the problem is gone. i still get entrees in the log file all day

050316 19:57:41 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)

and now im getting a new one more and more:

050316 22:13:42 [Warning] Aborted connection 78747 to db: 'canadaka_net' user: 'username' host: `localhost' (Got an error reading communication packets)

well the database has been pretty stable the last couple days, ahsn't crashed, but im still getting the same errors in the mysql log. and i noticed errors are being logged in the Windows event log:


C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)

For more information, see Help and Support Center at http://www.mysql.com.


also some users are reporting the have session errors, but this is pretty rare, so far.

still getting errors in mysql log and windows event log, but mysql hasn't crashed for a week, so thats good.

But would like to know why im getting these errors and how to fix it.

8 months late and im still getting these errors i the mysql and windows logs. "Can't open file: 'nuke_session.MYI' "

but mysql almost never crashes, maybe onces every month. But it might have other effects....?

ok do the following:

Log into phpmyadmin...

create DELETE nuke_session.MYI..

recreate it manually (via sql)..

It should solve the problem..

chances that you copied the table from your localhost..

Peace,

ok I will try that tonight when the site traffic is low

well tried the advice above, no change. still get the errors

You need to repair the table, as this is a very common problem with nuke.

REPAIR TABLE nuke_session

How are you on disk space? Sometimes this problem occurs when disk space is low.

/me reserves comments about *nuke

Please don't bump threads, as this is against the rules that you agreed to when creating an account.

I have tried the repait table many times. from the MySQL Administrator GUI. there is several options for repairing, have tried them all.

plus re-creating the table from scratch should be better than repairing correct?

60GB free on mysql drive. :/

recently this problem has come back... well never went away. but has been pretty stable for almost a year.

But a couple times in the last week mysql has crashed, luckely i was around to restart it. The windows Event log is full of My SQL aplication errors.

Event 100
C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'nuke_session.MYI' (errno: 145)

and when it crashed there was an error 1000
Faulting application mysqld-nt.exe, version 0.0.0.0, faulting module mysqld-nt.exe, version 0.0.0.0, fault address 0x001ea72c.

Upgrade MySQL.

Upgrade MySQL.

you think that will fix it?

Upgrade to what? 5.x?

I tried 5.0 some of the sites I host were messed when i upgraded to 5.x