David -
Sorry for the delayed response. ulimit is unlimited.
I am using the RPMs for RH EL3 downloaded from a
mirror so I would assumed they have been built to
allow > 2GB archives.
I am most likely going a different route at this point
as my query response time is much too slow even with a
1GB
Hello.
It is strange for me that there isn't a stack trace. If you can
- switch to the debug version of MySQL and run it under gdb
to find out where it is crashing. See:
http://dev.mysql.com/doc/refman/5.0/en/crashing.html
http://dev.mysql.com/doc/refman/5.0/en/debugging-server.html
laide); mysql@lists.mysql.com
Subject: Re: mysqld crash with archive engine > 2gb
> Is there any message in the log files? or any error
> message from the OS?
David -
When the mysqld process restarts, there is nothing in
the logfile except the basic startup info. I have
listed it below:0:
> Is there any message in the log files? or any error
> message from the OS?
David -
When the mysqld process restarts, there is nothing in
the logfile except the basic startup info. I have
listed it below:0:33).
051116 10:06:33 [Note] /usr/sbin/mysqld: ready for
connections.
Version: '5.0
Hi Marc,
Is there any message in the log files? or any error message from the OS?
Regards
David Logan
Database Administrator
HP Managed Services
148 Frome Street,
Adelaide 5000
Australia
+61 8 8408 4273 - Work
+61 417 268 665 - Mobile
+61 8 8408 4259 - Fax
-Original Message-
From: Mar
Marc:
Define "crashing the server". Does the whole machine shut down? The
mysqld process? What do error logs say? What version of MySQL are
you using? What's the create table statement? what's the current
avg_row_length and max_rows? What is ulimit -f as the MySQL user say?
-Sheeri
On 11/
Abdulla,
- Original Message -
From: ""Paizulaev Abdula"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, April 05, 2004 7:43 AM
Subject: mysqld crash, got following
> InnoDB: Error: record field 3 len 4294967207
> Heap no too big 5888 93
> Error in page 117145 in i
Hi!
On Jan 12, Holm Tiffe wrote:
> >Description:
> mysqld 4.0.17 crash on FreeBSD 5.1-current-alpha
> >How-To-Repeat:
> Any acces over IP (not domain socket) crashes mysqld:
> #/usr/local/bin/mysqladmin: connect to server at 'install' failed
> error: 'Lost connection to MySQL server during q
Hi!
On Jan 12, Holm Tiffe wrote:
> >Description:
> mysqld 4.0.17 crash on FreeBSD 5.1-current-alpha
> >How-To-Repeat:
> Any acces over IP (not domain socket) crashes mysqld:
> #/usr/local/bin/mysqladmin: connect to server at 'install' failed
> error: 'Lost connection to MySQL server during q
Richard,
looks like a clean case of memory corruption.
Your log sequence number is only 29 MB. You got problems very quickly. I
regularly run tests where gigabytes of log are generated, and no crash.
Linux-2.4.20 has the reputation of being stable. This might even be a
hardware problem.
Best re
Diana Soares wrote:
>On Fri, 2002-07-26 at 18:43, Mike Wexler wrote:
>
>
>>Diana Soares wrote:
>>
>>
>>
>>>Hi, just sending a reply in case that someone else has the same problem.
>>>I solved the problem by decreasing the key-buffer from 320M to 288M.
>>>
>>>
>>>
>>We tried that am
On Fri, 2002-07-26 at 18:43, Mike Wexler wrote:
>
>
> Diana Soares wrote:
>
> >Hi, just sending a reply in case that someone else has the same problem.
> >I solved the problem by decreasing the key-buffer from 320M to 288M.
> >
> We tried that among many other things. It turns out that their i
Hi, just sending a reply in case that someone else has the same problem.
I solved the problem by decreasing the key-buffer from 320M to 288M.
On Wed, 2002-07-03 at 12:24, Diana Soares wrote:
> Hi,
>
> I have 2 machine dual-processor Pentium III, with 1G of memory.
> They have the same software
Diana Soares wrote:
>Hi, just sending a reply in case that someone else has the same problem.
>I solved the problem by decreasing the key-buffer from 320M to 288M.
>
We tried that among many other things. It turns out that their is some
kind of problem related to temporary tables. MySQL AB is
Diana,
Wednesday, July 03, 2002, 2:24:51 PM, you wrote:
DS> I have 2 machine dual-processor Pentium III, with 1G of memory.
DS> They have the same software, same architecture, with one-way replication
DS> beetween. Versions:
DS> [root@localhost tmp]# mysql -V
DS> mysql Ver 11.18 Distrib 3.23.51
On Mon, Feb 04, 2002 at 02:33:40PM -0700, Sasha Pachev wrote:
> On Monday 04 February 2002 11:59 am, Jeremy Zawodny wrote:
> > >?This does look like a libc bug. How did you build either one of the
> binaries?
> >
> > They're your binaries. ?I don't buld my own binaries on Linux to save
> > the h
On Monday 04 February 2002 11:59 am, Jeremy Zawodny wrote:
> >?This does look like a libc bug. How did you build either one of the
binaries?
>
> They're your binaries. ?I don't buld my own binaries on Linux to save
> the hassle of using libraries that are different from what you folks
> use. :-)
On Mon, Feb 04, 2002 at 10:08:37AM -0700, Sasha Pachev wrote:
> On Monday 04 February 2002 02:30 am, Jeremy Zawodny wrote:
> > 0x807bb5f handle_segfault__Fi + 383
> > 0x82a94aa pthread_sighandler + 154
> > 0x7cb80076 __evoke_link_warning_llseek + 1954074198
> > 0x7cb7fe19 __evoke_link_warning_llse
On Mon, Feb 04, 2002 at 07:15:33PM +0200, Sinisa Milivojevic wrote:
>
> Yes, this is troubling ...
>
> It could be hardware, though ...
>
> Can you find anything in MySQL log and especially in /var/log/dmesg
> or /var/log/messages.
Nope.
> Sometimes, not often, Linux kernel is capable of not
Jeremy Zawodny writes:
> On Mon, Feb 04, 2002 at 02:27:01PM +0200, Sinisa Milivojevic wrote:
>
> That was your binary on Linux.
>
> Strangely, I just started up that exact same copy of 3.23.47-max and
> it worked fine after a machine reboot.
>
> That's most unusual (and troubling).
>
> Thanks,
On Monday 04 February 2002 02:30 am, Jeremy Zawodny wrote:
> 0x807bb5f handle_segfault__Fi + 383
> 0x82a94aa pthread_sighandler + 154
> 0x7cb80076 __evoke_link_warning_llseek + 1954074198
> 0x7cb7fe19 __evoke_link_warning_llseek + 1954073593
> 0x7cb713e6 __evoke_link_warning_llseek + 1954013638
>
On Mon, Feb 04, 2002 at 02:27:01PM +0200, Sinisa Milivojevic wrote:
>
> Jeremy,
>
> It could also be a bug in glibc.
>
> As you are using Linux, can you try out binary ??
That was your binary on Linux.
Strangely, I just started up that exact same copy of 3.23.47-max and
it worked fine after
TECTED]>
Sent: Monday, February 04, 2002 1:49 PM
Subject: Re: mysqld crash & stack trace from 3.23.47-max (with InnoDB)
> jocelyn fournier writes:
> > Hi,
> >
> > About glibc, I saw the 2.2.5 release included the spinlock.c patch, part
of
> > the intern
jocelyn fournier writes:
> Hi,
>
> About glibc, I saw the 2.2.5 release included the spinlock.c patch, part of
> the internals.h (except the following part :
> -#define STACK_SIZE (2 * 1024 * 1024)
> +#define STACK_SIZE (128 * 1024)
> )
> The local_lim.h is also partially patched :
>
> The fol
ssage -
From: "Sinisa Milivojevic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, February 04, 2002 1:27 PM
Subject: Re: mysqld crash & stack trace from 3.23.47-max (with InnoDB)
> Jeremy Zawodny writes:
> > I just atte
Hi!
InnoDB seems to have created the database and started ok. This does not look
like an InnoDB bug.
I think gethostbyaddr asks from a connection the hostname, and subsequent
code checks that the host has access rights to mysqld.
For some reason gethostbyaddr_r crashes.
Hmm.. if you could run
Try the -q option to mysqldump so it doesn't buffer up the whole thing.
Quentin Bennett wrote:
> Hi,
>
> Doing a mysqldump of a large table to /tmp, I filled up /tmp, which caused
> mysqld to reset.
>
> This is while using 3.23.40 on Solaris 2.6
>
> What additional information should I provi
27 matches
Mail list logo
