Environment

• YugabyteDB Anywhere - 2.20, 2024.1, and 2024.2

Issue

The Node Health Check for a Universe fails while checking node agent status. The following error message is reported on the Health Check page for the Universe and in the YugabyteDB Anywhere (YBA) logs:

YW 2025-04-29T05:04:21.114Z [ERROR] 295608a0-0000-0000-0000-f1e30296d69e from NodeAgentClient$BaseResponseObserver in NodeAgentGrpcPool-5 - Error encountered for 15237713-6a6c-4077-a5f8-53a3f5a204ba-/home/yugabyte/bin/node_health.py - Error(1) 2025-04-29 00:04:21,081 INFO: Script started at 2025-04-29T05:04:21Z
Traceback (most recent call last):
File "/home/yugabyte/bin/node_health.py", line 2536, in <module>
main()
File "/home/yugabyte/bin/node_health.py", line 2412, in main
checker = NodeChecker(
File "/home/yugabyte/bin/node_health.py", line 586, in __init__
self.prev_process_results = self._load_previous_per_process_results(temp_output_file)
File "/home/yugabyte/bin/node_health.py", line 592, in _load_previous_per_process_results
js = json.load(f)
File "/usr/lib64/python3.9/json/__init__.py", line 293, in load
return loads(fp.read(),
File "/usr/lib64/python3.9/json/__init__.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/lib64/python3.9/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib64/python3.9/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Resolution

Overview

This issue occurs when the "process stats" file created when the health check script runs exists but does not contain valid JSON. In the example above, the process stats file existed but was empty. To resolve this issue, remove the stale process stats file.

Steps

1. Log into the affected node as the yugabyte user

2. Remove the stale process stats file. By default, this file is located at /tmp/process_stats.json

rm /tmp/process_stats.json

3. Wait for the following health check to run and confirm that the issue is resolved

Additional Information

A permanent fix for this issue will be available in a future release.  The permanent fix is being tracked in Jira ticket PLAT-17515.