10-09-2019 12:37 AM
Hi All,
I guess it is expected for the device to throw the error message below:
Thanks,
Myky
10-10-2019 07:59 AM
not entirely sure, you'll want to take a look at the peer's ms.log and compare what is happening on both sides
10-09-2019 02:35 AM
would need a little more context
did a local commit fail due to an error? in which case it is expected the (failed) config is not synced
10-10-2019 05:52 AM
How can l check that?
There was a commit lock, just 7 seconds before this alert was triggered:
Thanks,
Myky
10-10-2019 07:16 AM
if the system log is not providing more details you could check the jobs/tasks or the ms.log for more details
10-10-2019 07:59 AM
not entirely sure, you'll want to take a look at the peer's ms.log and compare what is happening on both sides
10-11-2019 02:20 AM
Hi again guys,
Logs from the spare unit don't mean much to me:
This was a one-time instance. If it occurs again we will get TAC involved.
Thanks again,
Myky
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!