'show system stats' on as-admin throws an error when performance monitor is turned on. The error resembles, "Failed Command: show system stats "Cause: member_not_found".
Article ID: KB0092711
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveSpaces | - |
| Not Applicable | - |
Description
Error resembles, "Failed Command: show system stats "Cause: member_not_found".
as-admin> monitor system true
as-admin> show system stats
SYS_ERROR (action_failed -
Failed Command: show system stats
Cause: member_not_found
Message: Member ID: 0-0-0-0 not found
)
Symptoms:
When running " show system stats" from as-admin from a remote client, error thrown:
SYS_ERROR (action_failed -
Failed Command: show system stats
Cause: member_not_found
Message: Member ID: 0-0-0-0 not found
Cause:
When monitoring is enabled on a remote client, it inserts a row into the "$sys_stats" space with member id 0-0-0-0. Next, when the as-admin sees this member ID and tries to get the member information in order to display the member info, there is no such member and consequently no member information is retrieved. In this case, Admin throws out the error "member ID 0-0-0-0 not found."
Issue/Introduction
Resolution
There is a defect in running the "Monitor system
true" command from the remote client. The "Monitor system true" command will
enable monitor on the remote member, not to all peer-members. You
have to run "monitor system true" on each member that you would like to
enable monitoring.
Alternatively, you can run the following commands from the remote client - as-admin
===================================
First enable monitoring on members.
as-admin > execute on member "as-agent-name-1" monitor system true
as-admin > execute on member "as-agent-name-2" monitor system true
then,
as-admin > show space "$sys_stats" entries
This command will show data such as entries in tuples, unlike what you usually see in a table from.
====================================
Once you collect all the stats, you can disable monitoring.
===============================
as-admin > execute on member "as-agent-name-1" monitor system false
as-admin > execute on member "as-agent-name-2" monitor system false
===============================Additional Information
Feedback
