hi guys
according to
Quote:[root@www root]# w 16:21:03 up 21:10, 3 users, load average: 0.04, 0.04, 0.00
the site is up only a few hours, which to me is rather annoying....
I didn't reboot it, further examination revealed that all logs are OK and not one of them mentions a reboot or crash, indeed not only that but ifconfig shows data throughput that just 'doesnt happen' on linux-noob.com in 21 hours....
Quote:[root@www root]# ifconfig eth0eth0 Link encap:Ethernet HWaddr 00:B0:D0:88:FF:78
inet addr:100.0.0.3 Bcast:100.0.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:176864105 errors:55592 dropped:0 overruns:11 frame:103017
TX packets:232565472 errors:0 dropped:0 overruns:0 carrier:181978122
collisions:988797 txqueuelen:1000
RX bytes:2689469193 (2564.8 Mb) TX bytes:1705211768 (1626.2 Mb)
Interrupt:10 Base address:0xfc00
ok then, so what is happening here ?
well according to this site the uptime changed after a certain number of days/hours
[/url]http://en.uptime-project.net/page.php?page...ofile&uid=60313
Quote:1. 26.04.2004 14:42 GMT 05.09.2005 16:21 GMT 1y 132d 01h 38m 07s Linux 2.4.22-1.2188.nptl
and we all know that there are 365 days or so in the year, and 365+132 =497 days....
well guess what. the above linux kernel (fedora) was unpatched for a uptime overflow after 497 days, so the server did NOT reboot, but the uptime WAS RESET by a bug in the kernel.
[url=https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97373]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97373
if only i knew before it 'reset' itself.
dam annoying and i'd like to announce this post so that others may be aware in the future.
cheers
anyweb
Quote:well guess what. the above linux kernel (fedora) was unpatched for a uptime overflow after 497 days, so the server did NOT reboot, but the uptime WAS RESET by a bug in the kernel.
[/url][url=https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97373]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=97373
if only i knew before it 'reset' itself.
dam annoying and i'd like to announce this post so that others may be aware in the future.
ah yeah, i remember reading about this on
linux-counter (are you COUNTED! [img]<___base_url___>/uploads/emoticons/default_laugh.png[/img] ) its ashame that you can't view your 'real' uptime without adding on the missing day count..
Quote:NOTE: The Linux kernel (at least up to 2.4.2) has a flaw: It computes the result of the "uptime" based on the internal "jiffies" counter, which counts the time since boot, in units of 10 milliseconds.This is typecast as an "unsigned long" - on the Intel boxes, that's an unsigned 32-bit number.
Well, it turns out that in a 32-bit number, you can store 497.1 days before the number wraps. So all the numbers higher than this on this list are because:
* They are not Intel architectures
* They have sent in updates on both sides of the wrap, and my scripts have successfully correlated them and concluded that it was a wrap, not a reboot.
Thanks to Brian "Z" Frappier for alerting me to the problem!
sending an e-mail to the uptime-project guys... im sure they have experienced this before.. maybe they can inject a fix..
Poor anyweb had his uptime reset... does he need a hug? [img]<___base_url___>/uploads/emoticons/default_rolleyes.gif[/img][img]<___base_url___>/uploads/emoticons/default_laugh.png[/img]
well it did annoy me,
the laptop is still running fedora core release 1 and has this site mirrored on it, however i've installed a separate machine with fedora core release 4 and it is now running linux-noob.com
cheers
anyweb
after e-mailing uptime-project.. i was initially disappointed with the reply, however they have now indcated that they will look into it.. so fingers crossed that the issue is 'fixed' their end :)
screw the project
i finally powered down that fcr1 laptop today after 525 days uptime (zero reboots).
cheers
anyweb
525 days? jeeze that is a LONG time, especially for a laptop too! [img]<___base_url___>/uploads/emoticons/default_ohmy.png[/img]