Yep, was just going to post this:
http://youadmin.net/wiki/Linux:RedHat_uptime_reset_after_497_days
It's a linux bug.
Rory McCann
Minn-Kota Ag Products
P: 701-403-4877 | E: [email protected]
On 8/30/2012 2:06 AM, Chupaka wrote:
http://forum.mikrotik.com/viewtopic.php?p=98190#p98190
2012/8/30 Bill Prince <[email protected]>
We had an RB493 do something almost identical. Been quite a while, but I
do recall it also having 400+ days on the odometer. It was like it had
rebooted, but hadn't at the same time.
I never figured it out, and it never did it again. This was at least a
couple years ago, and the RB493 we saw this on was on ROS 3.30.
I chalked it up to some kind of ROS bug.
bp
On 8/29/2012 2:47 PM, Robert Haas wrote:
Anyone see this before?
I got an alert that one of our core routers rebooted at 2am this morning,
but no alarms from any attached devices as being unreachable etc. Got up
and
logged in and the uptime was 8 minutes or so.
This afternoon I had a chance to investigate the router more. The router
has
NOT rebooted - log files lack any indication I would expect to see from a
router reboot (hundreds of PPPoE session coming back up) and attached
devices interface statistics show no loss of link.
Looking at the PPPoE active sessions, some of the session are showing up
496
days - which is the actual uptime of the router, which isn't possible
since
I have the PPPoE session time limit set for 24 hours.
Attached is an image showing the Active PPPoE sessions and the resource
page
showing the reported uptime.
The router is on X86 hardware running v4.17.
I'm hoping to NOT reboot this router if at all possible, but my gut says
it
is down hill from this point.
Is my gut telling me correctly to go ahead and reboot the router to clear
whatever has borked the router (memory leak, memory corruption, phase of
the
moon) at the first chance I get?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 8-29-12.png
Type: image/png
Size: 100974 bytes
Desc: not available
URL: <http://www.butchevans.com/**pipermail/mikrotik/**
attachments/20120829/943ab6f0/**attachment.png<http://www.butchevans.com/pipermail/mikrotik/attachments/20120829/943ab6f0/attachment.png>
______________________________**_________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
______________________________**_________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20120830/dd965b8b/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
