Following changes have been done:
* log when SU restart/failover limits have been reached
* log each time a SU restart/failover occurs
* add a log entry when error escalation is changed
* log each time a component is restarted, or when restart limits have been
reached
Further changes will be done to log info regarding probation timers, so I'm
re-opening this ticket.
---
** [tickets:#870] AMF: syslog error escalation**
**Status:** review
**Milestone:** 4.5.FC
**Created:** Tue Apr 22, 2014 03:15 PM UTC by Hans Feldt
**Last Updated:** Mon May 26, 2014 03:51 AM UTC
**Owner:** Gary Lee
Today AMF is rather silent when it does error escalation. For better
understanding and troubleshooting it would be good to syslog all escalation
decisions and why they are taken. Related timers should also be logged for
example when they expire.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
