Hi Team,
I executed the NCC health checks run_all on two clusters and got the following message (at the end of the run_all script):
Detailed information for sar_stats_threshold_check:ERR : Execution terminated by exception IndexError('list index out of range',):Traceback (most recent call last): File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/ncc_utils/plugin_utils.py", line 128, in handle_exceptions result = fn() File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/base_plugin.py", line 740, in result = putils.handle_exceptions(lambda : check(*check_args), cls.canvas) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 358, in check_thresholds sar_data = SARStatsThresholdCheckPlugin.parse_sar_output(output, tbl_name) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 305, in parse_sar_output line = lines[line_index]IndexError: list index out of rangeERR : Execution terminated by exception IndexError('list index out of range',):Traceback (most recent call last): File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/ncc_utils/plugin_utils.py", line 128, in handle_exceptions result = fn() File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/base_plugin.py", line 740, in result = putils.handle_exceptions(lambda : check(*check_args), cls.canvas) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 358, in check_thresholds sar_data = SARStatsThresholdCheckPlugin.parse_sar_output(output, tbl_name) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 305, in parse_sar_output line = lines[line_index]IndexError: list index out of rangeERR : Execution terminated by exception IndexError('list index out of range',):Traceback (most recent call last): File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/ncc_utils/plugin_utils.py", line 128, in handle_exceptions result = fn() File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/base_plugin.py", line 740, in result = putils.handle_exceptions(lambda : check(*check_args), cls.canvas) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 358, in check_thresholds sar_data = SARStatsThresholdCheckPlugin.parse_sar_output(output, tbl_name) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 305, in parse_sar_output line = lines[line_index]IndexError: list index out of rangeERR : Execution terminated by exception IndexError('list index out of range',):Traceback (most recent call last): File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/ncc_utils/plugin_utils.py", line 128, in handle_exceptions result = fn() File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/base_plugin.py", line 740, in result = putils.handle_exceptions(lambda : check(*check_args), cls.canvas) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 358, in check_thresholds sar_data = SARStatsThresholdCheckPlugin.parse_sar_output(output, tbl_name) File "/home/hudsonb/workspace/workspace/ncc-2.0.2-stable_release/builds/build-ncc-2.0.2-stable-release/ncc-python-tree/bdist.linux-x86_64/egg/ncc/plugins/health_checks/sar_checks.py", line 305, in parse_sar_output line = lines[line_index]IndexError: list index out of rangeDetailed information for hdd_latency_threshold_check:Node 10.149.112.183:ERR : Sar command failed to executeNode 10.149.112.187:ERR : Sar command failed to executeNode 10.149.112.185:ERR : Sar command failed to execute
The cluster is running smoothly and no errors are shown up, but I would like to know what kind of issue are the provoking these messages.
Thank you!
Solved
NCC Health checks SAR command failed to execute
+3Best answer by Jon
You can upgrade NCC to the latest version (2.2) non-disruptively, right from the GUI.
If you do that, and are still having problems, please open a support ticket so we can track
View originalIf you do that, and are still having problems, please open a support ticket so we can track
This topic has been closed for comments
+29- Nutanix Employee
Hey - Thanks for reaching out.
First, I'd recommend opening a support ticket, so at worst, they could track this as a bug.
That said,
What version of NOS is this cluster running?
If it's above 4.1.3, you can upgrade NCC to a later release, without upgrading NOS.
You should be able to do that from 1click upgrade software if you have internet access from the cluster.
NCC 2.2 recently came out with the release of NOS 4.6, but again, you can install this back on 4.1.3 and above clusters.
I'm guessing this is just a silly bug, but if its still happening on a newer version of NCC, definitely open a support ticket if you haven't already.
First, I'd recommend opening a support ticket, so at worst, they could track this as a bug.
That said,
What version of NOS is this cluster running?
If it's above 4.1.3, you can upgrade NCC to a later release, without upgrading NOS.
You should be able to do that from 1click upgrade software if you have internet access from the cluster.
NCC 2.2 recently came out with the release of NOS 4.6, but again, you can install this back on 4.1.3 and above clusters.
I'm guessing this is just a silly bug, but if its still happening on a newer version of NCC, definitely open a support ticket if you haven't already.
+3Hi Jon,
The cluster is currently running NOS 4.1.5 and NCC 2.0.2.
So I assume it might be a bug in a previous version of NCC / Nutanix. I will pay attention if we run into the same issue during the next nutanix installation.
Thank you,
Andreas
The cluster is currently running NOS 4.1.5 and NCC 2.0.2.
So I assume it might be a bug in a previous version of NCC / Nutanix. I will pay attention if we run into the same issue during the next nutanix installation.
Thank you,
Andreas
+29- Nutanix Employee
You can upgrade NCC to the latest version (2.2) non-disruptively, right from the GUI.
If you do that, and are still having problems, please open a support ticket so we can track
If you do that, and are still having problems, please open a support ticket so we can track
+3Better later then never..
I was a bug as confirmed from Nutanix side and has been fixed with version 2.2 / 2.5 already
I was a bug as confirmed from Nutanix side and has been fixed with version 2.2 / 2.5 already
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.