Hmm. Can't sleep, but also can't work a mail client, apparently :-)
The thought was related to being in a transaction, but I tested it in the
meantime, and it's not that. Ignore :-)
- Original Message -
From: Johan De Meersman vegiv...@tuxera.be
To: Andy Wallace
Problem is that I don't set the timestamp variable anywhere (except yesterday as
a test to try and fix the problem). This is stuff that has been working
correctly
for many months. We had some network/dns and load issues over the last couple of
days, and the mysql clock is frozen at:
mysql
But the question is how. I have nothing in the code that does it, or this
would have been true for months instead of just the last 24 hours. In
addition, this is currently set globally - no matter what connection to
the database, it all comes up with this value. Which means that all my
time-based
Does show variables like 'init_connect'; return anything?
On Thu, Jun 27, 2013 at 11:19 AM, Andy Wallace awall...@ihouseweb.com wrote:
Benjamin -
Unfortunately:
mysql show global variables like 'timestamp';
+---++
| Variable_name | Value |
It persists across sessions?
Does this return anything:
show global variables like 'timestamp';
Hopefully it returns:
Empty set (0.00 sec)
I vaguely remember reading about a bug in 5.1.4x with something to do with
a global timestamp. I thought it only showed one though, and that you
couldn't
Timestamp is a session variable, so it must have been set to something
other than 0 (1372228034 epoch is the date you're showing) in your current
session.
mysql set timestamp = 1372228034;
Query OK, 0 rows affected (0.00 sec)
mysql select now(), sysdate();
Sort of:
mysql show variables like 'init_connect';
+---+---+
| Variable_name | Value |
+---+---+
| init_connect | |
+---+---+
On 6/27/13 11:23 AM, Eric Bergen wrote:
Does show variables like 'init_connect'; return anything?
On Thu, Jun
Benjamin -
Unfortunately:
mysql show global variables like 'timestamp';
+---++
| Variable_name | Value |
+---++
| timestamp | 1372238834 |
+---++
1 row in set (0.00 sec)
And:
mysql set global timestamp = 0;
ERROR
Hi,
On 06/27/2013 08:19 PM, Andy Wallace wrote:
Benjamin -
Unfortunately:
mysql show global variables like 'timestamp';
+---++
| Variable_name | Value |
+---++
| timestamp | 1372238834 |
+---++
1 row in set (0.00
Well, that begs the question - will restarting the MySQL server instance
tonight fix
the current problem? We do have a plan in place to test and eventually deploy
a more
recent version of MySQL (5.6?), but for now, I have to support 1000's of
customers.
My fingers are crossed.
On 6/27/13
Just out of curiosity, is the hardware stationed, or traveling close
to the speed of light (i.e., 18,000 miles per second)? Sorry I could
not help it
N.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
Ok, I appreciate the Einsteinian and Vonnegut humor... just wanted to say. Still
have the problem though. 8-(
On 6/27/13 9:51 AM, Nick Khamis wrote:
Just out of curiosity, is the hardware stationed, or traveling close
to the speed of light (i.e., 18,000 miles per second)? Sorry I could
not help
12 matches
Mail list logo
