as-agent/ AS member logs shows "node resetting, need restart".What doesthis mean for an AS cluster?

as-agent/ AS member logs shows "node resetting, need restart".What doesthis mean for an AS cluster?

book

Article ID: KB0087724

calendar_today

Updated On:

Products Versions
TIBCO ActiveSpaces -
Not Applicable -

Description

Resolution:
If an as-agent reports a log message such as, "node resetting, need restart", that member needs to be restarted.


Why: If an AS cluster suffers from continuous missed heartbeats due to memory availability in the host / swapping / network disruption more than member timeouts, the manager / members node kicked out from the AS cluster and the same as-agent will report "node resetting, need restart" in the logs.


What to do: Restart the as-agent but do not restart it right away because there will be a redistribution. The restart should be done at a time where redistribution is acceptable. From as-admin>  you can check redistribution progress.


How to monitor: If you enable a Hawk monitor on as-agent logs to look for patterns, you can add a new Hawk rule for finding the string "node resetting, need restart" in the as-agent log files. This will generate an alert when any as-agent reports the message.

Issue/Introduction

as-agent/ AS member logs shows "node resetting, need restart".What doesthis mean for an AS cluster?

Additional Information

Powered by Wolken Software