Hello Everyone, Yesterday I posted the message listed below. I have some more information. We have found the command that "pushes our database over the edge"! It is:
SHOW VARIABLES; All other db commands work (such as SHOW VARIABLES "%a";) except for: SHOW VARIABLES "%" Does anyone have any idea why this could be happening? In addition we are connecting to the database from a JSP Script using the driver: org.gjt.mm.mysql.Driver The JSP page doesn't actually explicitly call the SHOW VARIABLES; command, but I guess (?) that this is called explicitly in the driver connection somehow... We confirmed that it was the SHOW VARIABLES; command by checking the log file (with --log and --log-update options). We then tried this at the MySQL command line and it caused the db to restart. Could this mean that one of the variables displayed by the SHOW VARIABLES; command is causing some form of problem? Once again, many thanks in advance for taking the time to read this mail, and I hope someone can help! The very best of regards, Stewart ..........................................................._/.............. Stewart Tranter [EMAIL PROTECTED] _/ Hewlett-Packard GmbH Tel: (+49) 7031 14-1554 _/_/_/_/ _/_/_/_/ Software Engineering Services Fax: (+49) 7031 14-4961 _/ _/ _/ _/ Schickard Str.25 Mob: (+49) 1784 701 079 _/ _/ _/ _/ 71034 Böblingen _/ _/ _/_/_/_/ Germany _/ https://ecardfile.com/id/stewarttranter <https://ecardfile.com/id/stewarttranter> _/ ........................................................................... Management and security solutions. We make your e-solutions work. On budget. On time. Every time. External Web Site: http://www.hp.com/hps/ <http://www.hp.com/hps/> Internal Web Site: http://ses.cup.hp.com/ <http://ses.cup.hp.com/> ........................................................................... MESSAGE FROM 2nd April 2003: Hello, I have a MySQL Database with two instances running. They were both working 100% normally, until yesterday. When we connect to one instance we get the following error: mysqld got signal 10; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail key_buffer_size=16773120 record_buffer=131072 sort_buffer=524280 max_used_connections=0 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 80379 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 030402 11:32:22 mysqld restarted The other instance however works totally fine! The server diskspace is ok, we rebooted the server, everything looks ok! We are running "HP-UX B.11.11 U 9000/800 839927861 unlimited-user license" with MySQL version: Ver 3.23.54-max for hp-hpux11.11 on hppa2.0w Can anyone offer any suggestions please? We are all totally stumped!!! Many thanks in advance and best regards, Stewart
