MySQL Bugs: #58054: The mysql server its CURRENT

Bug #58054	The mysql server its CURRENT_TIMESTAMP stopped tracking time
Submitted:	8 Nov 2010 15:24	Modified:	9 Nov 2010 6:49
Reporter:	Bart Van Hoyweghen	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Options	Severity:	S2 (Serious)
Version:	5.1.50	OS:	Solaris (5.10 i386)
Assigned to:		CPU Architecture:	Any
Tags:	now() CURRENT_TIMESTAMP

Description:
MySQL returns the following
select CURRENT_TIMESTAMP;
+---------------------+
| CURRENT_TIMESTAMP |
+---------------------+
| 2010-10-27 12:09:34 |
+---------------------+
1 row in set (0.00 sec)

While Unix reports:
# date
Mon Nov 8 15:37:52 CET 2010

This is the second time this happens (we are aware).

The previous time this happened I restarted and the error log reported the following.
101014 11:41:52 [Note] /opt/mysql/mysql/bin/mysqld: Normal shutdown

101014 11:41:52 [Note] Event Scheduler: Purging the queue. 0 events
101026 7:30:10 InnoDB: Starting shutdown...
101026 7:30:12 InnoDB: Shutdown completed; log sequence number 32 2183196722
101014 11:41:52 [Note] /opt/mysql/mysql/bin/mysqld: Shutdown complete

101026 07:30:14 mysqld_safe mysqld from pid file /data/mysql/svr-214.pid ended
101026 07:30:28 mysqld_safe Starting mysqld daemon with databases from /data/mysql
101026 7:30:29 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
101026 7:30:29 [Note] Plugin 'FEDERATED' is disabled.
101026 7:30:30 InnoDB: Started; log sequence number 32 2183196722
101026 7:30:30 [Note] Event Scheduler: Loaded 0 events
101026 7:30:30 [Note] /opt/mysql/mysql/bin/mysqld: ready for connections.
Version: '5.1.50-log' socket: '/var/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)

The server was not halted for 12 days, it was restarted at 7:30 in the morning. However, the shutdown registers the wrong time.

It seems the server did run for 29 hours correct, and the problem re-appeared, but was only noticed now.

We have 3 servers running with pretty similar configurations, only this one shows this problem.

We upgraded on 7 sept. to 5.1.50, and never noticed this problem before.

Short term work around: reboot the server daily

How did we notice the problem: The disk usage slowly increased due to log files not cleaned up after 2 days.

Solaris is running on VMWare, and is using an NTP server for time management.

No other problems are visible (very surprised by this).

How can we investigate further?
Can a client generate this type of problem?
Is there a work-around without restarting the server?

How to repeat:
No idea?

Not even an idea on how to investigate this further.

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #42054

- We're not using timezones (it seems this is the way to repeat the problem)

Is it correct to state:
- Mysql has problems when running on Solaris which has an NTP client configured?
- There won't be any bug six issued quickly (since the previous bug report dates from jan. 2009)?