VxRail: Health-check Warning for "tcserver"
Summary: Files in the /mystic/radar tree should have user 'tcserver' and group 'pivotal' ownership. If not, this health-check can correct this or warn.
Symptoms
VxVerify checks the file ownership of files in the /mystic/radar folders.
The results of this health-check is listed as one of the following results:
| Test Result | Result code | Result Interpretation |
| Pass | 0 | All files found to have the correct ownership.
Alternatively, this check may be muted for this test profile. |
| Warning | 1 | Radar file ownership wrong for _ files |
| _Fixed | 1 | Radar file ownership corrected for _ files |
| Failure | 2 | This test has no failure result. |
| Critical | 3 | This test has no critical result. |
Each test that passes is not listed in the summary report, for ease of reading.
An example of the health-check output is shown below:
#========================#======#=========#====================================================================#==============# | Hostname / Category |Status Dell_KB | Warnings or Failures, unless tests Passed ; Product S.N. | #========================#======#=========#====================================================================#==============# | VxRM | _Fixed 302543 | tcserver: Radar file ownership corrected for 42 files .|
Cause
Files in the /mystic/radar tree should have user 'tcserver' and group 'pivotal' ownership. If not, this health-check can correct this or warn.
For example:
ls -la /mystic/radar/ total 20376 drwxr-xr-x. 14 tcserver pivotal 4096 Apr 2 15:32 . drwxr-xr-x. 21 tcserver pivotal 4096 Nov 27 15:05 .. drwxr-xr-x. 3 tcserver pivotal 4096 Nov 12 02:27 analysis drwxr-xr-x. 5 tcserver pivotal 4096 Nov 12 02:27 common drwxr-xr-x. 3 tcserver pivotal 4096 Nov 12 02:24 conf drwxr-xr-x. 2 tcserver pivotal 4096 Nov 12 02:24 docs drwxr-xr-x 2 tcserver pivotal 4096 Feb 19 2024 .drp drwxr-xr-x. 3 tcserver pivotal 4096 Nov 12 02:27 execution -rwxr-xr-x 1 tcserver pivotal 0 Nov 23 11:49 .gitkeep drwxr-xr-x. 2 tcserver pivotal 4096 Feb 4 00:23 logs drwxr-xr-x. 3 tcserver pivotal 4096 Nov 12 02:24 patch -rw-r--r-- 1 tcserver pivotal 539 Feb 19 2024 pipelines.yaml drwxr-xr-x. 80 tcserver pivotal 4096 Nov 12 02:27 plugins drwxr-xr-x 5 tcserver pivotal 4096 Feb 4 00:23 py311venv -rwxr-xr-x 1 tcserver pivotal 28093 Feb 4 00:23 radar -rwxr-xr-x 1 tcserver pivotal 20751370 Nov 23 11:49 Radar.tgz drwxr-xr-x. 5 tcserver pivotal 4096 Apr 2 00:23 report -rw-r--r-- 1 tcserver pivotal 13 Feb 19 2024 runtime.txt -rw-r--r-- 1 tcserver pivotal 1765 Feb 19 2024 sonar-project-ieo.properties -rw-r--r-- 1 tcserver pivotal 1153 Feb 19 2024 sonar.sh -rw-r--r-- 1 tcserver pivotal 11 Apr 2 00:23 .task_store -rw-r--r-- 1 tcserver pivotal 748 Feb 19 2024 unittest.sh drwxr-xr-x 5 tcserver pivotal 4096 Feb 4 00:23 venv
Resolution
Running VxVerify (from the root user), with auto-fix enabled (i.e. adding the -f or --fix argument), can automatically correct this issue. This is also enabled by default in some VxVerify upgrade test profiles.
Alternatively, using the following command can also fix the user and group ownership:
sudo chown -R tcserver:pivotal /mystic/radar/