From: abush
Date: February 15 2000 2:44pm
Subject: Bad Mysql, Bad Hardware or Bad OS??
List-Archive: http://lists.mysql.com/mysql/27822
Message-Id: <38A96668.B3C22625@microcenter.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This is Mysql-3.22.30 running on RH6.1 Linux with 256MB RAM, one PII333
CPU and a RAID1 / file-system (see snip of bug report below for full gcc
specs).

I have noticed problems with trying to shut the server down with a 
mysqladmin -u root -p shutdown

From pervious posts I see where this will return right away and then
proceed to stop the server.  If do a ps I see that after about 30 to 60
seconds only one mysqld process is running still?  
If I issue another mysqladmin shutdown command I get the cannot connect
using /tmp/mysql.sock error?  Again another ps still shows the mysqld
running.
The hostaname.err log has an entry like this:
<SNIP>
000215 0:00:00 /usr/local/mysql/libexec/mysqld: Normal shutdown

000215 0:00:00 /usr/local/mysql/libexec/mysqld: Shutdown Complete
</SNIP>

The only problem here is that the mysqld is still running.
I had to kill this process with -9 finally.  I have ran isamchk on the
tables and found errors in one that a -r quickly repaired.

Here is some additional disturbing messages that came out of a backup
script.  This script does a shutdown, then tar of the db dir, then a
start via safe_mysqld.  The grep and ps errors are comming from the
safe_mysqld script, the backup_script conatins no greps or ps's.

========================
Starting mysqld daemon with databases from /usr/local/mysql/var
 == COMPLETED mysql_backup.sh @ Tue Feb 15 00:03:38 EST 2000
grep: memory exhausted
ps: error in loading shared libraries: libproc.so.2.0.0: cannot map
zero-fill pages: Cannot allocate memory
grep: memory exhausted

Number of processes running now: 
/usr/local/mysql/bin/safe_mysqld: test: integer expression expected
after -le
mysqld restarted on  Tue Feb 15 05:28:12 EST 2000
mysqld daemon ended
======================================

>>>>> mysqlbug output =====
>Release:       mysql-3.22.30 (Source distribution)

>Environment:
        
System: Linux mysql 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686
unknown
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
/usr/bin/cc
GCC: Reading specs from
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
Compilation info: CC='gcc'  CFLAGS=''  CXX='c++'  CXXFLAGS='' 
LDFLAGS=''
Configure command: ./configure  --prefix=/usr/local/mysql
Perl: This is perl, version 5.005_03 built for i386-linux
======================================

Yesterday this machine also froze completely up?  I could type at the
console an it would echo on the screen but it would not respond (could
login, telnet, ftp, even ctrl+alt+delete wouldn't work, neither would a
ping to it respond).  I had to hit the reset switch on the box finally.
There was nothing logged in the mysql err log when this happened so i
don't believe that mysql could have locked the server up.  I did find
this in the messages log of the server this morning today.  The times
coincide with the last entry on the backup log snip from above:

Feb 15 05:25:04 mysql kernel: Unable to load interpreter 
Feb 15 05:30:07 mysql kernel: Unable to load interpreter 
Feb 15 05:30:08 mysql kernel: Unable to load interpreter

====
The times that this was logged were around the time that the above was
logged??
-->mysqld restarted on  Tue Feb 15 05:28:12 EST 2000

I am starting to think that I may have a bad machine, main board or
memory SIMMS?  Has anyone out there ever seen behavior like this from a
Linux server or Mysql?

Thanks,
Aaron Bush