Re: lot of VM problem with 2.4.23
From: Willy Tarreau
Date: Sun Dec 21 2003 - 10:45:09 EST
On Sun, Dec 21, 2003 at 04:03:12PM +0100, Octave wrote:
> # ps auxw | grep -v "0 0.0"
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> mysql 26958 0.0 14.0 275000 144972 ? S Dec19 2:09 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
> mysql 27004 0.0 14.0 275000 144972 ? S Dec19 2:28 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
> mysql 27005 0.0 14.0 275000 144972 ? S Dec19 2:03 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
> root 9621 0.0 0.1 6316 1860 ? S 01:02 0:00 /usr/sbin/sshd
> root 9631 0.0 0.1 2500 1352 pts/0 S 01:02 0:00 -bash
> root 9683 0.0 0.1 6276 1844 ? S 13:47 0:00 /usr/sbin/sshd
> root 9707 0.0 0.1 2504 1356 pts/2 S 13:47 0:00 -bash
> postfix 29728 0.0 0.1 3508 1184 ? S 15:45 0:00 pickup -l -t fifo -u
> mysql 7341 0.0 14.0 275000 144972 ? S 15:59 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
> root 7347 0.0 0.1 2504 1356 pts/2 R 15:59 0:00 -bash
>
> There is nothing to take 1Go of RAM.
Octave,
one of my collegues had a server which occasionally crashed at night with
mysql taking all the memory. I think it was with an old 2.4.18 kernel. He
finally reinstalled all the machine and it never happened anymore. So
eventhough it works for you with 2.4.22, perhaps 2.4.23 triggers a mysql
bug which is fixed in more recent releases ?
Cheers,
Willy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/