MySQL Bugs: #69605: NOW() is stuck

Bug #69605	NOW() is stuck
Submitted:	27 Jun 2013 17:00	Modified:	27 Jun 2013 18:45
Reporter:	Andrew Wallace	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: General	Severity:	S2 (Serious)
Version:	5.1.46-log	OS:	Solaris (SunOS 5.10 Generic_142901-04 i86pc i386 i86pc)
Assigned to:		CPU Architecture:	Any
Tags:	invalid time, NOW(), time_zone

Description:
We've been having some issues with one of our MySQL servers lately, and
currently the dang thing is "stuck". For at least the last hour, NOW() is
returning the same
value:

mysql> select now();
+---------------------+
| now()               |
+---------------------+
| 2013-06-26 02:27:14 |
+---------------------+

The system variable "timestamp" also has that same time value stored in it. How can we kick this loose so that the values are more current with real time? (it is currently 3:08PM here, despite our MySQL instance thinking it's 2am. The system time on the machine is correct:

$ date
Thu Jun 27 09:57:06 PDT 2013

One suggestion I got was to force a set to the global timezone to try and kick the NTP process, but that won't work because we don't have the time_zone tables loaded - we use the "SYSTEM" value for time_zone.

How to repeat:
Alas, I have no idea. We are stuck in this situation, and I will try restarting the mysql process tonight (it was supposed to happen last night, but there were miscommunications between development and IT).

Suggested fix:
Some way to force a re-start of the time service without restarting the engine would be great....

you should probably upgrade to recent version, this is likely a duplicate of http://bugs.mysql.com/bug.php?id=42054 !