- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
12-01-2016 07:42 AM - edited 12-01-2016 07:46 AM
I have RMA'd two units now that have had FAILING_NOW in their logs. One of the units was exhibiting odd unreliable behaviors. After RMA I dropped the same OS, config file and state on the device. Problems went away.
From CLI:
> less mp-log mp-monitor.log
It starts from 0% (to quit, press q)
To search a keyword, you have to press / and enter a keyword.
Ex.
Press / and enter FAILING_NOW
Press n —> next
Press q to quit
2016-12-01 07:06:26.030 -0600 --- memory
Last 180 seconds
Type Free (kB) min (kB) Total (kB)
Mem 330248 330248 2575632
Swap 7996 7996 7996
-----------------------------
...skipping...
167 Unknown_Attribute 0x0000 100 100 100 Old_age Offline FAILING_NOW 359
-----------------------------
2016-12-01 07:07:22.232 -0600 --- logging_status
Logging-Status
-----------------------------
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!