I'm trying to get our new Windows Server 2008 running. I believe I heard
that I have to install 5.1 on there to get it running. I think I'm aout to
find out, because I'm giong to uninstall 5.1 and install 5.0.xxx At any
rate, here's what's going on:
I bring up the Query Browser GUI, and log in. So far, no problem. I
double-click on a database to open it up. There is a short delay, then it
shows me all the tables. I then try to double-click on a table to view it's
contents, but I can't. It seems to be disabled. After a short delay, it
finally allows me to double-click on it, but then the Execute button is
disabled. I checked the service, and it has been stopped. I then check the
server.err file, and here's what is in there:
080927 9:42:25 - 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=135266304
read_buffer_size=65536
max_used_connections=2
max_threads=800
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 393089
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x1ff9e660
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...
005BEC6F mysqld.exe!???
1FFC0550
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 1FFAA9B0=SHOW FUNCTION STATUS
thd->thread_id=5
thd->killed=NOT_KILLED
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!
080927 9:46:03 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...
080927 9:46:08 InnoDB: Started; log sequence number 0 273250418
080927 9:46:08 [Warning] Neither --relay-log nor --relay-log-index were
used; so replication may break when this MySQL server acts as a slave and
has his hostname changed!! Please use '--relay-log=Naboo-relay-bin' to avoid
this problem.
080927 9:46:09 [ERROR] Column count of mysql.db is wrong. Expected 22,
found 20. The table is probably corrupted
080927 9:46:09 [ERROR] mysql.user has no `Event_priv` column at position 29
080927 9:46:09 [ERROR] Event Scheduler: An error occurred when initializing
system tables. Disabling the Event Scheduler.
080927 9:46:09 [Note] D:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld:
ready for connections.
Version: '5.1.28-rc-community' socket: '' port: 3323 MySQL Community
Server (GPL)
080927 9:46:36 - 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=135266304
read_buffer_size=65536
max_used_connections=1
max_threads=800
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 393089
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x20246c18
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...
005BEC6F mysqld.exe!???
2024F530
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 2027E300=SHOW FUNCTION STATUS
thd->thread_id=1
thd->killed=NOT_KILLED
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!
080927 9:53:04 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...
080927 9:53:05 InnoDB: Started; log sequence number 0 273250418
080927 9:53:05 [Warning] Neither --relay-log nor --relay-log-index were
used; so replication may break when this MySQL server acts as a slave and
has his hostname changed!! Please use '--relay-log=Naboo-relay-bin' to avoid
this problem.
080927 9:53:05 [ERROR] Column count of mysql.db is wrong. Expected 22,
found 20. The table is probably corrupted
080927 9:53:05 [ERROR] mysql.user has no `Event_priv` column at position 29
080927 9:53:05 [ERROR] Event Scheduler: An error occurred when initializing
system tables. Disabling the Event Scheduler.
080927 9:53:05 [Note] D:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld:
ready for connections.
Version: '5.1.28-rc-community' socket: '' port: 3323 MySQL Community
Server (GPL)
080927 9:53:45 - 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=135266304
read_buffer_size=65536
max_used_connections=2
max_threads=800
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 393089
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x20146c18
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...
005BEC6F mysqld.exe!???
2014F530
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 2017E300=SHOW FUNCTION STATUS
thd->thread_id=4
thd->killed=NOT_KILLED
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!
080927 9:53:59 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...
080927 9:54:00 InnoDB: Started; log sequence number 0 273250418
080927 9:54:00 [Warning] Neither --relay-log nor --relay-log-index were
used; so replication may break when this MySQL server acts as a slave and
has his hostname changed!! Please use '--relay-log=Naboo-relay-bin' to avoid
this problem.
080927 9:54:00 [ERROR] Column count of mysql.db is wrong. Expected 22,
found 20. The table is probably corrupted
080927 9:54:00 [ERROR] mysql.user has no `Event_priv` column at position 29
080927 9:54:00 [ERROR] Event Scheduler: An error occurred when initializing
system tables. Disabling the Event Scheduler.
080927 9:54:00 [Note] D:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld:
ready for connections.
Version: '5.1.28-rc-community' socket: '' port: 3323 MySQL Community
Server (GPL)
080927 9:54:32 - 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=135266304
read_buffer_size=65536
max_used_connections=2
max_threads=800
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 393089
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x203a6c18
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...
005BEC6F mysqld.exe!???
203AF938
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 203DA2F0=SHOW PROCEDURE STATUS
thd->thread_id=3
thd->killed=NOT_KILLED
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.
Is this a setting issue, or a bug?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
