Avamar: An incorrect permission on the sudoers file causes an "Unknown Node" Alert To appear In the health check script output

• The health check script (proactive_check.pl) fails to determine the hardware type of a node: 

cat hc_results.txt

...
WARNING:  Node (0.2) Unknown node type based on disk size (5 TB), memory (32 GB) and disk partitions (3)
RESOLUTION: Thoroughly check hardware status, size of partitions, number of partitions and amount of memory

# --> Node Type                      *FAILED*
# --> Node Type                       1x4 gen4s-Util/Accel, gen4s-M1200, Unknown 5 TB<snip>

• Hardware commands fail on the affected node: 

avsysreport chassis-info

sudo: /etc/sudoers is mode 0551, should be 0440
sudo: no valid sudoers sources found, quitting 

The permissions on the /etc/sudoers file are incorrect.

1. Log in to the Avamar Utility Node as admin. 

2. Elevate to root, and load the ssh keys. See Avamar: How to Log in to an Avamar Server and Load Various Keys for more information.

3. Check the permissions of the /etc/sudoers file for all nodes: 

mapall --noerror --all+ --user=root 'ls -ahltr /etc/sudoers'

Expected output from a single-node grid: 

Using /usr/local/avamar/var/probe.xml
(0.0) ssh -q  -x  -o GSSAPIAuthentication=no root@10.10.10.246 'ls -ahltr /etc/sudoers'
-r--r----- 1 root root 9.9K Aug 25 22:53 /etc/sudoers

Expected output from a multinode grid:

Using /usr/local/avamar/var/probe.xml
(0.s) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.1 'ls -ahltr /etc/sudoers'
-r--r----- 1 root root 8.3K Aug 17  2023 /etc/sudoers
(0.0) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.2 'ls -ahltr /etc/sudoers'
-r--r----- 1 root root 9.8K Jun  1  2022 /etc/sudoers
(0.1) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.3 'ls -ahltr /etc/sudoers'
-r--r----- 1 root root 9.8K Jun  1  2022 /etc/sudoers
(0.2) ssh -q  -x  -o GSSAPIAuthentication=no root@192.168.255.4 'ls -ahltr /etc/sudoers'
-r--r----- 1 root root 9.8K Jun  1  2022 /etc/sudoers

4. For any node that reports incorrect permissions or ownership:

a. Connect to the node in question.

b. Modify the permissions or ownership as required:

chmod 440 /etc/sudoers
chown root:root /etc/sudoers

c. Verify the hardware commands respond appropriately:

avsysreport chassis-info

=== Chassis information
Host Name     : testavamar.company.com
Chassis Model : Gen4S M1200
Serial Number : FC6AV123456789
Part Number   : 100-580-643
BIOS Version  : SE5C600.86B.02.04.0003.102320141138

The health check script should now run without reporting the alert.

• Avamar: Potential issues caused by an incorrect sudoers configuration
• Avamar: Incorrect sudoers file on server causes AVI login error