Sounds like a clock slip/ntp issue> -----Original Message----- > From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users- > bounces at lists.digium.com] On Behalf Of Jeff LaCoursiere > Sent: Monday, February 14, 2011 10:39 PM > To: asterisk-users at lists.digium.com > Subject: [asterisk-users] uptime > > > Now this is what I call uptime... > > minipbx*CLI> show uptime > System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 > seconds > Last reload: 8 hours, 3 minutes, 51 seconds > > Bizarre bug? > > root at minipbx:~# asterisk -V > Asterisk 1.4.37 > root at minipbx:~# uname -a > Linux minipbx 2.6.32-dockstar #2 Thu Nov 25 18:03:25 UTC 2010 armv5tel > GNU/Linux > root at minipbx:~# uptime > 03:29:27 up 5 days, 9:33, 2 users, load average: 0.28, 0.15, 0.10 > root at minipbx:~# > > > > j > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
Now this is what I call uptime... minipbx*CLI> show uptime System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds Last reload: 8 hours, 3 minutes, 51 seconds Bizarre bug? root at minipbx:~# asterisk -V Asterisk 1.4.37 root at minipbx:~# uname -a Linux minipbx 2.6.32-dockstar #2 Thu Nov 25 18:03:25 UTC 2010 armv5tel GNU/Linux root at minipbx:~# uptime 03:29:27 up 5 days, 9:33, 2 users, load average: 0.28, 0.15, 0.10 root at minipbx:~# j
On Tuesday 15 Feb 2011, Jeff LaCoursiere wrote:> Now this is what I call uptime... > > minipbx*CLI> show uptime > System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds > Last reload: 8 hours, 3 minutes, 51 seconds > > Bizarre bug?I'm guessting, this is a brand new machine on its first ever boot, with no "last bootup time" information saved anywhere. So it assumes the last bootup date was 1970-01-01 00:00:00, i.e. "zero time" on all Unix-like systems. That would explain the 41 years, anyway. -- AJS
On 15 Feb 2011, at 03:39, Jeff LaCoursiere wrote:> minipbx*CLI> show uptime > System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds > Last reload: 8 hours, 3 minutes, 51 secondsWhat's the highest current 'genuine' one on-list?.. klein*CLI> core show uptime System uptime: 2 years, 1 week, 4 days, 21 hours, 52 minutes Last reload: 41 weeks, 6 days, 16 hours, 6 minutes, 39 seconds That's the best I can come up with.. S
On Tue, 15 Feb 2011, A J Stiles wrote:> On Tuesday 15 Feb 2011, Jeff LaCoursiere wrote: >> Now this is what I call uptime... >> >> minipbx*CLI> show uptime >> System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds >> Last reload: 8 hours, 3 minutes, 51 seconds >> >> Bizarre bug? > > I'm guessting, this is a brand new machine on its first ever boot, with > no "last bootup time" information saved anywhere. So it assumes the last > bootup date was 1970-01-01 00:00:00, i.e. "zero time" on all Unix-like > systems. That would explain the 41 years, anyway. > > -- > AJSNo, it is a few months old now with lots of reboots. It is my experiment to build a reliable PBX out of Seagate Dockstar hardware and USB sticks. I've now blown up about three 4G sticks, presumably for heat issues (?), and have just bought an "SLC" based stick (which was not easy to find) that supposedly has a better heat range and longer write life. Once I got it working I saved a dd image of the stick and have just been imaging the new sticks as I try them. This *is* the first boot on this new stick, but the filesystem itself is "old", with several reboots. I don't really care about the uptime calculation, just thought it was funny. It is strange that asterisk and the OS don't agree... so how does asterisk compute it? FWIW it makes a fantastic home PBX. I use it daily to make conference calls that last for hours, and other extensions in the house make and receive calls at the same time. It has *just* enough RAM to not swap, and I have turned off all the logging, so there aren't that many writes to the USB stick. Pretty fantastic for about $40 in hardware. j
On Mon, Feb 14, 2011 at 10:39:20PM -0500, Jeff LaCoursiere wrote:> > Now this is what I call uptime... > > minipbx*CLI> show uptime > System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds > Last reload: 8 hours, 3 minutes, 51 seconds > > Bizarre bug?Hi. I see that 41 years, 7 weeks,...,46 seconds is $ TZ=EST5EDT date -d @`dc -e '41 365*7 7*+6+24*3+60*26+60*46+p'` Mon Feb 14 22:26:46 EST 2011 about 13 min. before your post, meaning Asterisk apparently used 0 as its start time when calculating uptime. How do you set the system time? Is it possible that Asterisk starts before the time is set? Do you run "ntpdate -b" at startup, or set the time by some other means before the boot completes? Could this result in some really humorous CDRs? -- Barry