Bug #29380 mysql-service-agent does not process SIGHUP
Submitted: 27 Jun 2007 9:08 Modified: 1 Aug 2008 15:53
Reporter: Kristian Koehntopp Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Agent Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jan Kneschke CPU Architecture:Any
Tags: mysql-service-agent log sighup

[27 Jun 2007 9:08] Kristian Koehntopp
The agent does not process SIGHUP.

It should close and reopen all files on reception of sighup to better integrate with logrotate.

How to repeat:
Find PID of agent.
See what happens.

Suggested fix:
Handle SIGHUP as demons should handle it.
[22 Aug 2007 15:21] Jan Kneschke
added in [7230] for trunk/
[22 Aug 2007 22:03] Jan Kneschke
merged into 1.2.0 in [7237]
[9 Jun 2008 11:07] Jan Kneschke
For 2.0 the logfile rotation has been changed to log the progress of the rotation:

At startup:

  2008-06-09 12:58:50: (message) mysql-proxy 0.7.0 started

When a SIGHUP is received:

  2008-06-09 12:59:05: (message) received a SIGHUP, rotating logfile

The new logfile gets:

  2008-06-09 12:59:05: (message) rotated logfile

At shutdown:
  2008-06-09 12:59:44: (message) shutting down normally
[9 Jun 2008 11:14] Jan Kneschke
revno: 771
revision-id: jan@mysql.com-20080609110316-982t1rdpse1tjw0g

  added logfile rotation through SIGHUP
[1 Aug 2008 10:13] Carsten Segieth
checked OK with
[1 Aug 2008 15:53] Tony Bedford
An entry was added to the 2.0 changelog:

The agent did not process SIGHUP.