Posted: 8/12/2014 10:30:58 AM EDT
14:19:37 up 236 days, 3:51, 1 user, load average: 0.00, 0.01, 0.05
|
|
Meh, we rebooted a server a couple of weeks ago that had been up 4000+ days. Don't remember exactly since I wasn't involved (Team Lead, don't do a lot of hands anymore). Both admins that were involved in the reboot were in grade school when the system was last rebooted. Can't say much about the client but this was a Solaris 5 box running on Ultra hardware. They have some strange ideas of "cost efficiency". Running ancient shit until its barely running is one of them. Only had to reboot it twice to get it back up. If the console port had been working it wouldn't have been so hard. Apparently someone unplugged the serial port several years back in the interests of "security". Fortunately hands and eyes actually knew what to look for. "Yeah, nothing plugged into the console port...(sound of someone blowing on something, followed by coughing...) found the cable. Looks like its been unplugged a while. |
|
Quoted:
This is uptime. 18:37:05 up 1473 days, 1:49, 5 users, load average: 1.00, 1.00, 1.0 Edit: For Proof 
http://i.imgur.com/F1RNsGy.png Damn... that's one of the longer ones I've saw. The other day I was on a forum and saw one posted for 1100.. but yours tops that by almost a year. I don't leave my NAS on all the time, because there's just no need to. I had actually had my NAS up for about 3 weeks straight, which is the longest I've left it up... then I was messing around behind the TV, trying to unplug the TV, and accidentally unplugged the NAS instead of the TV... oops.. time to start over. :). Otherwise, it would have been shutdown on Friday anyway. 15:25:28 up 16:16, 3 users, load average: 0.10, 0.07, 0.06 |
|
pe01.nwc uptime is 5 years, 20 weeks, 1 day, 8 hours, 35 minutes
System returned to ROM by reload at 11:40:30 UTC Wed Mar 25 2009 System restarted at 03:44:21 AKDT Wed Mar 25 2009 System image file is "disk0:rsp-pv-mz.124-23.bin" Last reload reason: Unknown reason Cisco RSP8 (R7000) processor with 262144K/8216K bytes of memory. |
|
ah cool,
ROM: System Bootstrap, Version 12.2(17r)S1, RELEASE SOFTWARE (fc1) BOOTLDR: c6sup2_rp Software (c6sup2_rp-PSV-M), Version 12.1(26)E1, RELEASE SOFTWARE (fc2) cr13.cwc uptime is 7 years, 39 weeks, 5 days, 8 hours, 19 minutes Time since cr13.cwc switched to active is 7 years, 39 weeks, 5 days, 7 hours, 29 minutes System returned to ROM by power-on (SP by error - a Software forced crash, PC 0x4012BC64) System restarted at 03:35:01 AKST Thu Nov 9 2006 System image file is "sup-bootflash:c6sup22-psv-mz.121-26.E1.bin" |
|
ROM: System Bootstrap, Version 12.2(17r)S1, RELEASE SOFTWARE (fc1)
BOOTLDR: c6sup2_rp Software (c6sup2_rp-PO3SV-M), Version 12.1(23)E2, RELEASE SOFTWARE (fc1) cr10.nwc uptime is 9 years, 38 weeks, 4 days, 8 hours, 35 minutes Time since cr10.nwc switched to active is 9 years, 38 weeks, 4 days, 9 hours, 24 minutes System returned to ROM by power-on (SP by power-on) System restarted at 02:08:02 AKST Wed Nov 17 2004 System image file is "sup-bootflash:c6sup22-po3sv-mz.121-23.E2.bin" cisco WS-C6509-NEB (R7000) processor (revision 3.0) with 458752K/65536K bytes of memory. |
|
Quoted:
Its not mine but we used to have one here that had 4 years on it. We finally upgraded it a few years ago. http://cdn.arstechnica.net/wp-content/uploads/2013/03/intel-server-uptime.jpg 
|
|
Quoted:
Its not mine but we used to have one here that had 4 years on it. We finally upgraded it a few years ago. http://cdn.arstechnica.net/wp-content/uploads/2013/03/intel-server-uptime.jpg I don't believe that for a minute. 3.12 didn't catch on hard until around 95 in most places. 16 years with zero power failures, datacenter relocations, motherboard/CPU failures, SCSI or other issues requiring a reboot? I totally believe Netware was capable. Just not that environmentals would allow that. 
|