Or hardware failure?
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Thu, Mar 2, 2017 at 5:57 PM, Judd Dare via Mikrotik-users < [email protected]> wrote: > This was a hard crash due to a kernel failure and the watchdog caught it. > Power was probably fine, just a bug somewhere that caused the kernel to > crash. I'd take this opportunity to think about upgrading to another > version which may have that crash fixed. > > Judd > > On Thu, Mar 2, 2017 at 1:13 PM, Brough Turner via Mikrotik-users < > [email protected]> wrote: > >> It was not a power outage and the OSPF issues are minor (coming from a >> separate problem). >> >> But your suggestion of a terminal window is a good one! >> >> There are two messages. I suspect the first is true and the second one >> is anomaly that goes along with the lack of any startup log messages. >> >> >> This is the first time I've seen a kernel failure out of 7 CCRS operating >> for 6 to 14 months. >> >> >> Thanks, >> Brough >> >> Brough Turner >> netBlazr Inc. – Free your Broadband! >> Mobile: 617-285-0433 <(617)%20285-0433> Skype: brough >> netBlazr Inc. <http://www.netblazr.com/> | Google+ >> <https://plus.google.com/102447512447094746687/posts?hl=en> | Twitter >> <https://twitter.com/#%21/brough> | LinkedIn >> <http://www.linkedin.com/in/broughturner> | Facebook >> <http://www.facebook.com/brough.turner> | Blog >> <http://blogs.broughturner.com/> | Personal website >> <http://broughturner.com/> >> >> >> >> On Thu, Mar 2, 2017 at 2:51 PM, Scott Reed <[email protected]> >> wrote: >> >>> Open a terminal window. If it was a power outage, under the banner it >>> will say something like reboot without proper shutdown. >>> >>> Also, the very beginning of the log after power up may have some help. >>> >>> The part you are showing looks like OSPF getting started. >>> >>> On 3/2/2017 2:11 PM, Brough Turner via Mikrotik-users wrote: >>> >>> At 12:24 today, one of our core routers appears to have had a brief >>> outage. It's upstream of our monitoring server so initially everything >>> looked like a disaster, but upon further examination, the outage lasted >>> less than 30 seconds and the 11 VPN sessions at the monitoring server were >>> all back up in less than 37 seconds. Looking at the monitoring server and >>> each of the devices upstream of the monitoring server, all had uptimes of >>> >143 days, except the gateway router, a CCR1036. >>> >>> Strangely, the uptime on the CCR1036 suggests it rebooted at 12:24 >>> today, but there is nothing in its log. How can we have a 30 second >>> service outage and have the router's uptime reset with no log entries? On >>> a router reboot, we normally have dozens of log entries before the router >>> is up, has the correct time and is behaving normally. >>> >>> Here's a Winbox view of date, time, uptime and the log. Any ideas? Am >>> I missing something obvious? >>> >>> >>> >>> >>> Thanks, >>> Brough >>> >>> Brough Turner >>> netBlazr Inc. – Free your Broadband! >>> Mobile: 617-285-0433 <(617)%20285-0433> Skype: brough >>> netBlazr Inc. <http://www.netblazr.com/> | Google+ >>> <https://plus.google.com/102447512447094746687/posts?hl=en> | Twitter >>> <https://twitter.com/#%21/brough> | LinkedIn >>> <http://www.linkedin.com/in/broughturner> | Facebook >>> <http://www.facebook.com/brough.turner> | Blog >>> <http://blogs.broughturner.com/> | Personal website >>> <http://broughturner.com/> >>> >>> >>> >>> >>> _______________________________________________ >>> Mikrotik-users mailing >>> [email protected]http://lists.wispa.org/mailman/listinfo/mikrotik-users >>> >>> >>> >> >> _______________________________________________ >> Mikrotik-users mailing list >> [email protected] >> http://lists.wispa.org/mailman/listinfo/mikrotik-users >> >> > > _______________________________________________ > Mikrotik-users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/mikrotik-users > >
_______________________________________________ Mikrotik-users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/mikrotik-users
