Comment 3 for bug 364450
Revision history for this message
| Graham Binns (gmb) wrote Re: Spurious TooMuchTimeSkew error when updating DebBugs watches | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Okay, so in an example of spurious behaviour suddenly not being quite so spurious, it's happened again: OOPS-1207CCW717.
A couple of questions spring to mind:
1. What's going on at the same time as this (it failed this time at ~13:00; last time at ~13:51; maybe there's a process on loganberry chewing up CPU at about that time).
2. How long is it taking to get from the time that the expected server time is declared (i.e. server_time = datetime.now()) to where it's checked against the *actual* server time (also datetime.now())? Are we getting stuck in a stupidly long-running loop at some point?
I'm going to bump this up to high for investigation purposes.