Bug #58409 | (critical) network-backend.c:163: time went backwards | ||
---|---|---|---|
Submitted: | 23 Nov 2010 5:29 | Modified: | 9 Jan 2015 10:23 |
Reporter: | Wan Tao LUO | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Proxy | Severity: | S1 (Critical) |
Version: | 0.8.1 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | network-backend.c time |
[23 Nov 2010 5:29]
Wan Tao LUO
[23 Nov 2010 18:13]
Sveta Smirnova
Thank you for the report. Verified as described mostly feature request "publish log-error-reference" as message itself seems to be correct in this situation.
[24 Nov 2010 2:20]
Wan Tao LUO
Hi, Sveta My poor English told me that you must answer me as simply as possible. o(︶︿︶)o Q1: Whether or not those critical messages are warning me an unstable status of the proxy? if they arn't, see Q2. else see Q3. Q2: Those critical messages should not be classified in "critial" if they are not so "critial", aren'they? They make me difficult to find messages I really want to take a look. (my log-level = message) Q3: What shall I do with this? Thanks.
[29 Nov 2010 8:09]
Wan Tao LUO
Hi, A new test showing: Sometimes when these messages append the log, a lot of TCP connections from php-fgi to myproxy established and holding there( normally they disappear quickly ), so the users can feel a slow-down when they visit the pages.