Bug #23829 Process List Time Column Impossible Value

• Submitted: 1 Nov 2006 6:57
• Modified: 1 Dec 2006 12:32
• Reporter: David Hillman
• Status: No Feedback
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 4.1.18
• OS: Linux (Linux ( FC4 ))
• CPU Architecture: Any
• Tags: process list, time

[1 Nov 2006 6:57] David Hillman

Description:

   After restarted one of my slave servers, I noticed the following impossible value in the Time column...

show full processlist;
+----+-------------+-----------+--------+---------+------------+-----------------------------------------------------------------------+-----------------------+
| Id | User        | Host      | db     | Command | Time       | State                                                                 | Info                  |
+----+-------------+-----------+--------+---------+------------+-----------------------------------------------------------------------+-----------------------+
|  1 | root        | localhost | db     | Query   |          0 | NULL                                                                  | show full processlist |
|  2 | system user |           | NULL   | Connect |        631 | Waiting for master to send event                                      | NULL                  |
|  3 | system user |           | NULL   | Connect | 4294967292 | Has read all relay log; waiting for the slave I/O thread to update it | NULL                  |
+----+-------------+-----------+--------+---------+------------+-----------------------------------------------------------------------+-----------------------+
3 rows in set (0.00 sec)

mysql> show status like "%uptime%";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| Uptime        | 679   |
+---------------+-------+
1 row in set (0.00 sec)

mysql> 

How to repeat:

   All I did was restart the server.  It may or may not be related to the fact that I re-mastered it, and the proces-in-question is a slave thread.

Suggested fix:

   At a minimum, process time should never be larger than uptime.  Maybe a sanity check is in order.

[1 Nov 2006 12:32] Valeriy Kravchuk

Thank you for a problem report. Please, try to repeat with a newer version, 4.1.21, and inform about the results.

[2 Dec 2006 0:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".