m https://order.mysql.com/
- Original Message -
From: "Richard Gabriel" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Friday, August 08, 2003 11:50 PM
Subject: read_const error 127 - then MySQL dies
> Hi all,
>
> The following keeps happening and
> 0x80e6d8a
> > > 0x80ea88b
> > > 0x80e5ed3
> > > 0x80ebe0e
> > > 0x80e50bf
> > > 0x40035941
> > > 0x420da1ca
> > > New value of fp=(nil) failed sanity check, terminating stack trace!
> > > Please read http://www.mysql.com/doc/en/Using_stack
qld-max.sym -n mysql.stack
0x80dbe1f handle_segfault + 423
0x4003b47e _end + 934910594
0x8101e09
mysql_select__FP3THDP13st_table_listRt4List1Z4ItemP4ItemP8st_orderT4T3T4UlP13select_result
+ 6937
0x810e90d handle_select__FP3THDP6st_lexP13select_result + 101
0x80e6d8a mysql_execute_command__Fv +
Hi all,
The following keeps happening and I can't pinpoint a query that is
causing it. It did not happen in 3.23.x, but started upon upgrading to
4.0.14. The operating system/hardware information is as follows:
RedHat 8.0 - kernel 2.4.18SMP
4x Xeon Processors
4x 80GB SCSI drives (hardware RAID-
I get this message in mysqld.log when trying to access the server via
TCP/IP.
When using sockets it works fine.
Regards
Michael Skaastrup
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
h
t;[EMAIL PROTECTED]>
Sent: Wednesday, January 29, 2003 11:25 AM
Subject: MYSQL dies after FreeBSD 4.6.2-cvsup-4.7
> Hi,
>
> We just cvsup'd a FreeBSD machine from 4.6.2 to 4.7, made
world,
> and installed a new kernel. Now mysql is complaining :
>
>
> Fatal err
Hi,
We just cvsup'd a FreeBSD machine from 4.6.2 to 4.7, made world,
and installed a new kernel. Now mysql is complaining :
Fatal error 'Can't create gc thread' at line ? in file /usr/src/lib/libc_r/uthre
ad/uthread_create.c (errno = ?)
030129 10:36:35 mysqld restarted
Fatal error 'Can
jschleigh,
Tuesday, October 01, 2002, 4:06:15 PM, you wrote:
jahdc> I had a working install of mysql 3.23 in /usr/bin and /var/lib/mysql.
I installed 4.0.3 to /usr/local/mysql and can't get it to run. I followed the
installation instructions to the
jahdc> T. When I run '/usr/local/my
ix:
Not known
>Submitter-Id:
>Originator:[EMAIL PROTECTED]
>Organization:
>MySQL support: [none | licence | email support | extended email support ]
>Synopsis: mysql dies when starting
>Severity: critical
>Priority: medium
>Category: my
My MySQL server 3.23.51 died in an hour after
I created a table containing "longtext" field.
I am not sure that this was the reason but
suspect so since it was running for few weeks
w/out problems.
It stopped accepting answering TCP & UNIX socket
connections, although was still listening on TCP.
On Saturday 23 February 2002 05:34 pm, you wrote:
> (gdb) thread 1
> [Switching to thread 1 (process 31905, thread 1)]
> #0 ?0x82011ce in memcpy ()
> (gdb) bt
> #0 ?0x82011ce in memcpy ()
> #1 ?0x82a33c0 in mysql_bin_log ()
> #2 ?0x80b7cd8 in ha_commit_trans ()
> #3 ?0x8076e24 in mysql_execute_com
ED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, February 24, 2002 5:32 PM
Subject: Re: Mysql dies with Signal 11
> Richard,
>
> >(gdb) thread 1
> >[Switching to thread 1 (process 31905, thread 1)]
> >#0 0x82011ce in memcpy ()
> >(gdb) bt
> >#0 0x82011ce in mem
and latest news on InnoDB
-Original Message-
From: "Richard Clarke" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Date: Sunday, February 24, 2002 2:42 AM
Subject: Mysql dies with Signal 11
>Hi,
>I seem to be getting intermittant crashes of mysql. The
Hi,
I seem to be getting intermittant crashes of mysql. The error log prints
the following,
mysqld got signal 11;
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
y 11, 2002 8:00 AM
To: '[EMAIL PROTECTED]'
Subject: MySQL dies
Hi,
I'm in desperate need of help.
MySQL keeps dying and I just can't figure out why...
Here goes:
Clients connect from Windows machines via VB and Delphi apps
through myodbc doing queries on databases with *b
sing connection because mysql dies, queries have to be done
again.
Error log says that mysqld restarted, i.e. safe_mysqld immediately restarts
the server.
Only mysql is running on the machine.
Queries may look like this:
CREATE TEMPORARY TABLE tmpTable(FRM varchar(5),ARKL varchar(5),KNR
varchar(10)
>Description:
Mysql dies in signal 11
>How-To-Repeat:
Don't know. Seems to happen when machine runs for more than 24 hours.
>Fix:
Unknown.
We will be trying the latest version of Mysql (3.23.46).
>Submitter-Id: [EMAIL PROTECTED]
>Originator:
I am using my laptop running win98 to develop a php site using Apache/mySQL.
Inevitably, after working for about 45min-60min, I can no longer connect to
mySQL, and apache will no longer refresh the pages properly.
At this point, restarting the mySQL server and Apache does not do any good.
The onl
Hi,
When trying to run mysql I get the message
'found old style password for user 'graham' . Restart using --old-protocol'
How can I cure this problem please? I tried running mysql --old-protocol without
success.
Many thanks, Graham
[EMAIL PROTECTED] writes:
> >Description:
>
> After running for a variable amount of time, our server will just die.
> We have run myisamchk several times, with -r and with -o. We even
> checked the actual file system for corruption. This is a real problem
> when the server doesn't automa
>Description:
After running for a variable amount of time, our server will just die.
We have run myisamchk several times, with -r and with -o. We even
checked the actual file system for corruption. This is a real problem
when the server doesn't automatically restart.
This is what the log look
21 matches
Mail list logo
