I have 675 files with extension .log I do not have a master.log or a
bootstrap.log. I also cannot find a log subdirectory anywhere within MySQL.
What I did find is a file called YOUR-randomnumbers.err in C:\Program
Files\MySQL\MySQL Server 5.0\data\
When I ran the wizard, there was no default location for InnoDB files, I
chose one of the locations from the dropdown. Is this the problem and
how do I undo it? I also searched for *.cnf but only found two files
called openssl under \PHP\extras\
Here is the part of the file with a normal shutdown and today's, minus
most of the 00's and spaces:
081218 3:08:12 InnoDB: Started; log sequence number 0 1882488
081218 3:08:19 [Note] C:\Program Files\MySQL\MySQL Server
5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.67-community-nt' socket: '' port: 3306 MySQL Community
Edition (GPL)
081228 18:35:09 [Note] C:\Program Files\MySQL\MySQL Server
5.0\bin\mysqld-nt: Normal shutdown
081228 18:35:09 InnoDB: Starting shutdown...
081228 18:35:10 InnoDB: Shutdown completed; log sequence number 0 3757629
081228 18:35:10 [Note] C:\Program Files\MySQL\MySQL Server
5.0\bin\mysqld-nt: Shutdown complete
InnoDB: The first specified data file C:\MySQL InnoDB Datafiles\ibdata1
did not exist:
InnoDB: a new database to be created!
081228 18:35:12 InnoDB: Setting file C:\MySQL InnoDB Datafiles\ibdata1
size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Error: all log files must be created at the same time.
InnoDB: All log files must be created also in database creation.
InnoDB: If you want bigger or smaller log files, shut down the
InnoDB: database and make sure there were no errors in shutdown.
InnoDB: Then delete the existing log files. Edit the .cnf file
InnoDB: and start the database again.
081228 18:35:13 [ERROR] Default storage engine (InnoDB) is not available
081228 18:35:13 [ERROR] Aborting
081228 18:35:13 [Note] C:\Program Files\MySQL\MySQL Server
5.0\bin\mysqld-nt: Shutdown complete
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
081228 18:35:30 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...
InnoDB: Page directory corruption: supremum not pointed to
081228 18:35:30 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
00000....0;
asc
;InnoDB: End of page dump
081228 18:35:30 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form
checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
081228 18:35:30 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00000....0;
asc
;InnoDB: End of page dump
081228 18:35:30 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form
checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
081228 18:35:30 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.
key_buffer_size=0
read_buffer_size=65536
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 32000 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=00000000
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
006CDEA6 mysqld-nt.exe!???
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
081228 18:46:58 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...
InnoDB: Page directory corruption: supremum not pointed to
081228 18:47:03 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00000....0;
asc
;InnoDB: End of page dump
081228 18:47:03 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form
checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
081228 18:47:03 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00000....0;
asc
;InnoDB: End of page dump
081228 18:47:03 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form
checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
081228 18:47:03 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.
key_buffer_size=0
read_buffer_size=65536
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 32000 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=00000000
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
006CDEA6 mysqld-nt.exe!???
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Martin Gainty wrote:
cant accurately diagnose the problem w/o looking at the logs specifically
%MYSQL_HOME%/log/master.log
%MYSQL_HOME%/log/bootstrap.log
Drupal is a very buggy product..in fact the original project-lead quit
and no longer supports Drupal
you'll need to turn on maximum diagnostics in PHP to see which
operations Drupal is not performing correctly
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained
within this transmission.
> Date: Sun, 28 Dec 2008 19:27:45 -0600
> From: [email protected]
> To: [email protected]
> Subject: mysqld-nt.exe crashing
>
> This is on my WinXP Media Center laptop running Apache1.3.41, PHP5.2.6,
> mySQL5.0.67. The first two I installed manually, I found a Windows
> installer for mySQL. I have been able to install Drupal (which I'm
> learning) and SMF, which I'm using on my host but ran into some issues
> upgrading recently, so installed locally to test. I also had to adjust
> php.ini to get ZenPhoto running.
>
> I loaded a lot of modules into Drupal 5, and turned them on. Instead I
> got a page of errors about table watchdog not being able to be locked.
> When I googled that, one fix was to increase the max_allowed_packet
file
> in my.cnf. I apparently do not have a file named my.cnf. So, from
> start > all programs I ran the MySQL Server Instance Config Wizard. I
> accepted all the defaults for a production server. The first time I hit
> finish it couldn't start the server, but it did the second time.
>
> Went back to my Drupal install, hit back and then saved my
configuration
> again. It couldn't connect to the server. I rebooted the computer, and
> got a popup about mysqld-nt.exe crashing and did I want to report it to
> Windows.
>
> What do I do next? I still don't have a my.cnf file according to
> search. Drupal and SMF are both giving me the can't connect to database
> error. OK, I do have a my.ini file which seems to be what I need for
> Windows? It was modified today, created in September so when I
> installed mysql. I am trying to open ib_logfile0 in Notepad++ but that
> is still trying.
>
> Janine
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[email protected]
