Hi,
We've got a situation happening on a server, and have no idea why.
The server is a PII/600 with 1G memory, running BSDI 4.0.1 .
The Mysql is "mysql-3.22.32", and was compiled with :
gmake distclean
PATH=/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/contrib/bin:/usr/X11/bin
export PATH
CXXFLAGS=-g
export CXXFLAGS
./configure --with-debug --with-mysqld-user=mysql --with-libwrap=/usr/lib --loca
lstatedir=/usr/home/wwwcust1/mysql --enable-static
gmake
We currently use perl 5.004_04, Apache 1.3.14, mod_perl 1.21
Msql-Mysql-modules 1.2213 and php 4.0.3pl1 to access the databases.
This was a pretty stable install for about a year, until we had
2 crashes about a month apart. After that, we updated from running under
root to running under "mysql" user. At that point, it looks like we fail
irregularly :
mysqld started on Sat Apr 21 08:37:56 EDT 2001
/usr/local/libexec/mysqld: ready for connections
010424 11:25:39 /usr/local/libexec/mysqld: Normal shutdown
010424 11:25:40 /usr/local/libexec/mysqld: Shutdown Complete
mysqld ended on Tue Apr 24 11:25:40 EDT 2001
mysqld started on Tue Apr 24 11:25:47 EDT 2001
/usr/local/libexec/mysqld: ready for connections
mysqld started on Thu Apr 26 05:21:05 EDT 2001
/usr/local/libexec/mysqld: ready for connections
mysqld ended on Fri May 11 13:26:34 EDT 2001
mysqld started on Fri May 11 13:41:06 EDT 2001
/usr/local/libexec/mysqld: ready for connections
mysqld ended on Sat May 12 23:46:41 EDT 2001
mysqld started on Sat May 12 23:55:15 EDT 2001
/usr/local/libexec/mysqld: ready for connections
mysqld ended on Tue May 15 10:45:49 EDT 2001
mysqld started on Tue May 15 10:50:24 EDT 2001
/usr/local/libexec/mysqld: ready for connections
mysqld ended on Wed May 16 12:05:14 EDT 2001
mysqld started on Wed May 16 12:12:56 EDT 2001
/usr/local/libexec/mysqld: ready for connections
April 24 is when we changed from running as root to running as
the "mysql" user.
The ODD thing is that we don't get a core dump of any sort. The
only way we get ANY indication something happened is that we see :
Starting mysqld daemon with databases from /usr/home/wwwcust1/mysql
Segmentation fault
mysqld daemon ended
as the output of starting it as :
echo "/usr/local/bin/safe_mysqld"|at now
We also were doing a "mysqladmin status" on it every 10 minutes, and
the last one was :
Uptime: 90576 Threads: 1 Questions: 59880 Slow queries: 10 Opens: 19 Flush
tables: 1 Open tables: 11
We run about 3 other servers configured with the same versions,etc,
and they are all stable.
I know the first thing people will say is "UPGRADE", but I'd like to
see if there is something we can do while we try to schedule this with the
user. Or, something we should do when we put the lastest in incase it
has the same behaviour.
Thanks, Tuc/TTSG Internet Services, Inc.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
