Submit a bug: http://bugs.mysql.com Alas, you probably cannot provide a reproducible test case. Still, someone might start at the code and discover a possible cause.
> -----Original Message----- > From: Andy Wallace [mailto:awall...@ihouseweb.com] > Sent: Wednesday, June 26, 2013 3:10 PM > To: mysql list > Subject: NOW() is stuck... > > 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 > Wed Jun 26 15:08:56 PDT 2013 > > > This is MySQL 5.1.46 running on solaris2.10. > > Any ideas short of restarting the MySQL engine? I'm willing to do that, > but would much rather wait and not do it in the middle of the day. > > Thanks, > Andy > > > -- > Andy Wallace > iHOUSEweb, Inc. > awall...@ihouseweb.com > (866) 645-7700 ext 219 > -- > "Sometimes it pays to stay in bed on Monday, rather than spending the rest > of the week debugging Monday's code." > - Christopher Thompson > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
