Re[2]: Warning: Got signal 14 from thread X

[BAUMEISTER Alexandre]

Sinisa,

SM> Alex, you ran out of filedescriptors or out of anodes, depending on OS
SM> that you are using.

  I  though  filedescriptors  could  be the problem. I only had 256. I
  modified the system in order to have 1024 :

=========================================================================
[1:16pm]# ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        8192
coredump(blocks)     0
nofiles(descriptors) 1024
vmemory(kbytes)      unlimited
=========================================================================

  But still :
=========================================================================
010321 13:22:42  Warning: Got signal 14 from thread 4
010321 13:22:44  Warning: Got signal 14 from thread 8
010321 13:22:46  Warning: Got signal 14 from thread 5
010321 13:22:48  Warning: Got signal 14 from thread 8
010321 13:22:50  Warning: Got signal 14 from thread 4
010321 13:22:52  Warning: Got signal 14 from thread 4
010321 13:22:54  Warning: Got signal 14 from thread 4
010321 13:22:56  Warning: Got signal 14 from thread 4
010321 13:22:58  Warning: Got signal 14 from thread 8
010321 13:23:00  Warning: Got signal 14 from thread 8
=========================================================================

  How to know if filedescriptors or anode are the problem ?

  The extended stats below shows

        | Max_used_connections     | 17      |
        | Open_files               | 8       |
        | Open_tables              | 18      |

  I'm fare from 1024 filedescriptors.

=========================================================================
 [1:23pm]# mysqladmin ext
+--------------------------+---------+
| Variable_name            | Value   |
+--------------------------+---------+
| Aborted_clients          | 0       |
| Aborted_connects         | 0       |
| Bytes_received           | 1009183 |
| Bytes_sent               | 468860  |
| Connections              | 46      |
| Created_tmp_disk_tables  | 1       |
| Created_tmp_tables       | 1       |
| Created_tmp_files        | 0       |
| Delayed_insert_threads   | 0       |
| Delayed_writes           | 0       |
| Delayed_errors           | 0       |
| Flush_commands           | 1       |
| Handler_delete           | 0       |
| Handler_read_first       | 1       |
| Handler_read_key         | 18430   |
| Handler_read_next        | 3       |
| Handler_read_prev        | 0       |
| Handler_read_rnd         | 6       |
| Handler_read_rnd_next    | 48      |
| Handler_update           | 0       |
| Handler_write            | 70      |
| Key_blocks_used          | 3       |
| Key_read_requests        | 7       |
| Key_reads                | 3       |
| Key_write_requests       | 0       |
| Key_writes               | 0       |
| Max_used_connections     | 17      |
| Not_flushed_key_blocks   | 0       |
| Not_flushed_delayed_rows | 0       |
| Open_tables              | 18      |
| Open_files               | 8       |
| Open_streams             | 0       |
| Opened_tables            | 24      |
| Questions                | 9331    |
| Select_full_join         | 0       |
| Select_full_range_join   | 0       |
| Select_range             | 0       |
| Select_range_check       | 0       |
| Select_scan              | 1       |
| Slave_running            | OFF     |
| Slave_open_temp_tables   | 0       |
| Slow_launch_threads      | 0       |
| Slow_queries             | 0       |
| Sort_merge_passes        | 0       |
| Sort_range               | 0       |
| Sort_rows                | 6       |
| Sort_scan                | 2       |
| Table_locks_immediate    | 9308    |
| Table_locks_waited       | 0       |
| Threads_cached           | 0       |
| Threads_created          | 18      |
| Threads_connected        | 18      |
| Threads_running          | 1       |
| Uptime                   | 501     |
+--------------------------+---------+  

SM> It could also be caused by a bug in TCP/IP part of the kernel, but the
SM> above causes are much more likely.

  TCP/IP ? How to know if it could be the problem ?

SM> Check out both your global and ulimit values.

  I have copied "ulimit -a" exit in this email.


  Regards,
  Alex.