Showstopping and Killing Stored Procedure.

[smays]

I have a Stored Procedure to which I pass one single integer value that is causing the server to shut down. I can run the actual query contained in the stored procedure manually just fine, but as soon as I try to call the stored procedure, the server shuts down???

I looked at the error log and it keeps claiming the following:
1.) "Recovering after a crash using hual-S-stemay-bin".
2.) "Starting Crash recovery..."
3.) "Crash recovery finished."

Anybody have any clues as to how I can fix this problem? I realize the details are kind of all over the map.

Thanks,
Steve.

 

[DonQuichote]

If the server crashes, it should leave an error in a log file. Check the installation directory (Windows) or /var/log (unix) and see if you see a mysql error log.


+++ Despite being wrong in every important aspect, that is a very good analogy +++
Hex (in Darwin's Watch)

 

[smays]

I mentioned several lines of the error log in the original post. I am using a Winderz XP Pro box with 2GB of RAM. Here is the rest of the error log:

090924 18:40:03 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=hual-S-stemay-bin' to avoid this problem.
090924 18:40:03 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
090924 18:40:04 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 416381403.
InnoDB: Doing recovery: scanned up to log sequence number 0 416381403
InnoDB: Last MySQL binlog file position 0 10276255, file name .\hual-S-stemay-bin.000015
090924 18:40:04 InnoDB: Started; log sequence number 0 416381403
090924 18:40:04 [Note] Recovering after a crash using hual-S-stemay-bin
090924 18:40:04 [Note] Starting crash recovery...
090924 18:40:04 [Note] Crash recovery finished.
090924 18:40:04 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.27-community-nt-log' socket: '' port: 3306 MySQL Community Edition (GPL)

Do you have any idea what the phrase "Please use '--log-bin=hual-S-stemay-bin'" means? Is there some clever SQL statement I should execute somewhere to do whatever that statement means?

The server is up and running at the moment and I ran a query to pull out some test data within the last hour. The server was also backed up at noon. It will get backed up again at 8 PM tonight. Some day in the near future I would like to set up a slave server (IT has been promising to Borg our server and I don't trust them so I would like to have a backup local - I might even set up the master here and let IT 'manage' the slave), but today there is only the master server.

Remember, the server only shuts down when I run a particular Stored Procedure. Executing the SQL query contained in the stored proc *outside* the stored proc works fine (the server executes the query and returns valid data) and leaves the server in tact.

I appreciate your help! Please be patient with me, I'm a dumb ballast designer (power electronics) so I am functional and I can get stuff done, but a lot of this is frankly over my head.

I am tempted to take advantage of this opportunity to upgrade to 5.0.51 and rebuild the database using the backup SQL files.

Steve.

 

[DonQuichote]

See

http://dev.mysql.com/doc/refman/5.1/en/binary-log.html

I can imagine that the binary log shows more than the query log. The query log only shows the procedure call. I hope the binary log shows the statements within the call.

Have you configured replication?

+++ Despite being wrong in every important aspect, that is a very good analogy +++
Hex (in Darwin's Watch)

 

[smays]

No, I have not configured replication (which I think means there is no slave server).

This is what I have in the "my.ini" file for logging:
[mysqld]
log
log-bin
log-slow-queries

Steve.

 

[DonQuichote]

The link I gave you tells how to read the binary log.

+++ Despite being wrong in every important aspect, that is a very good analogy +++
Hex (in Darwin's Watch)

 

[smays]

I followed the link and read part of what was written. I have since printed it out and I try to read all of it. I also found the 5.0 version of the same article and printed it out. What I have read so far means little to me.

I will finish reading the articles and see if I can read through the bin log.

Steve.