| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Sinisa Milivojevic | Date: | March 21 2001 11:54am |
| Subject: | Re: Warning: Got signal 14 from thread X | ||
| View as plain text | |||
Heikki Tuuri writes:
> Alex,
>
> I looked at the new debug log you sent and obviously some client is
> making connections to your server. This cannot come from
> Innobase, there must be some client process running on your machine.
>
> >From the debug log I find the following:
> ...............................
> T@11 : info: handle_one_connection called by thread 1
> T@11 : info: check_connections called by thread 1
>
> ...<snip>........
>
> T@11 : >vio_read
> T@11 : | enter: sd=10, buf=5a48230, size=4
> T@11 : | error: Got error 11 during read
> T@11 : | exit: -1
> T@11 : <vio_read
> T@11 : info: vio_read returned -1, errno: 11
> T@11 : >thr_alarm
> T@11 : | enter: thread: T@11 sec: 5
> T@11 : | info: reschedule
> T@11 : <thr_alarm
> T@11 : >vio_is_blocking
> T@10 : | >process_alarm
> T@10 : | | info: sig: 14 active alarms: 1
> T@11 : | exit: 0
> ...............................
>
> Obviously vio_read fails on an error 11, and then mysqld calls
> thr_alarm to produce signal 14.
>
> >From /usr/include/sys/errno.h I find:
>
> #define EAGAIN 11 /* Resource temporarily unavailable */
>
> Probably Sinisa can find out what is the problem here.
>
> Regards,
>
> Heikki
>
>
Hi!
Yes, of course. It has nothing to do with Innobase.
Alex, you ran out of filedescriptors or out of anodes, depending on OS
that you are using.
It could also be caused by a bug in TCP/IP part of the kernel, but the
above causes are much more likely.
Check out both your global and ulimit values.
Regards,
Sinisa
____ __ _____ _____ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:sinisa@stripped
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____
^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^
/*/ \*\ Developers Team