| Summary: | ASTERISK-01207: show uptime giving weird results... | ||
| Reporter: | zoa (zoa) | Labels: | |
| Date Opened: | 2004-03-13 08:20:43.000-0600 | Date Closed: | 2004-09-25 02:54:39 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | System uptime: ÐV\ Last reload: 5 minutes, 59 seconds julius*CLI> show uptime System uptime: ps Last reload: 6 minutes, 3 seconds julius*CLI> show uptime System uptime: pJ] Last reload: 6 minutes, 5 seconds julius*CLI> show uptime System uptime: Last reload: 6 minutes, 6 seconds ****** ADDITIONAL INFORMATION ****** it should have shown 2 days or so... an asterisk restart fixed this.. no idea where to look for, is the first time i see this. julius*CLI> show version Asterisk CVS-03/27/04-14:49:08 built by root@julius on a x86_64 running Linux (system date was wrong when i built asterisk, should be 02/27) | ||
| Comments: | By: Brian West (bkw918) 2004-03-13 15:59:36.000-0600 Update fix your date and try again. By: James Golovich (jamesgolovich) 2004-03-13 19:27:33.000-0600 I'd guess that this is some stack corruption here, probably totally unrelated to the uptime. By: zoa (zoa) 2004-03-13 19:36:25.000-0600 any idea how to debug a stack corruption ? should that be caused by asterisk, or could i be corrupted by another program ? By: James Golovich (jamesgolovich) 2004-03-14 04:20:15.000-0600 I had another thought about this and I tested it out. If your clock was set in the future when * started and you corrected the time when it ran then it might do something like this. I commited a fix to make sure the passed value is >= 0. It fixed the problem in my test of setting the time in the future and setting it back. Let me know if it fixes it for you, if your able to reproduce it at all By: zoa (zoa) 2004-03-14 04:54:38.000-0600 in the last few days i changed the server date for some reason. It might be before the last asterisk restart, but it might as well be during the last asterisk run, so i'll close this bug. | ||