Bug #1245 MySQL - SIGPIPE error
Submitted: 11 Sep 2003 5:43 Modified: 16 Oct 2003 6:25
Reporter: [ name withheld ] Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.0.12 OS:Solaris (Solaris 2.8)
Assigned to: CPU Architecture:Any

[11 Sep 2003 5:43] [ name withheld ] 
Description:
MySQL throws an SIGPIPE signal to the client approximately after 7-8 hours of time. After this signal, all database calls are failing / hanging / inconsistent. This is found on Solaris platform.

We have used MySQL 4.0.12 and MyODBC 3.51.06

How to repeat:
Run the client program for more than 8 hours continuosly. The client will receive an event SIGPIPE and after that all database calls are failing.
[16 Sep 2003 6:25] Jani Tolonen 
Hi,

I'm sorry, but we can't proceed this bug report without the
following information:

How was MySQL built?
How was MyODBC built?
What is platform for MyODBC, where is it used from?
What is platform for MySQL server, where is it used from?

If MySQL is built with thread_safe_client, e.g. using
./configure --enable-thread-safe-client, it will create
thread safe client library libmysqlclient_r. Using this libary
this problem should not occur.

Please post here only repeatable bugs. We need to be able
to reproduce the problem from scratch on our system.

Regards,
Jani
[14 Feb 2005 22:54] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".