| Summary: | ASTERISK-17511: adjust system time to cause asterisk timer run wrong | ||
| Reporter: | aaa (shihchuan) | Labels: | |
| Date Opened: | 2011-03-04 02:13:31.000-0600 | Date Closed: | 2011-03-08 12:43:29.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Resources/res_timing_pthread |
| Versions: | 1.8.3 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) extensions.conf ( 1) timer_bad.txt ( 2) timer_ok.txt | |
| Description: | 1. system time is "2011/3/4" 2. asterisk timer run wrong if adjust system time to "2011/3/3" so playback sounds fail after adjust system time 3. I enter asterisk cli "timing test" when timer run wrong Attempting to test a timer with 50 ticks per second. Using the 'pthread' timing module for this test. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. poll() timed out! This is bad. It has been 1009 milliseconds, and we got 0 timer ticks | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-03-08 12:43:29.000-0600 It has always been recommended that you never change the time significantly on a running Asterisk system because all sorts of things can happen. This is one of those cases where you shouldn't change the time of a running system significantly. | ||