Avamar: Missing probe.xml causes error: no database type or no node resource database could be found
Summary: This article provides instructions on how to re-create the probe.xml file if it cannot be found in its original location.
Symptoms
Basic commands on the Avamar Utility Node, such as dpnctl status, are failing:
Example:
dpnctl status
ERROR: no database type or no node resource database could be found with search list /usr/local/avamar/var/probe.xml, stopped at /usr/local/avamar/bin/../lib/dpnutils/node_util.pm line 756.
The probe.xml file is not present:
ls -al /usr/local/avamar/var/probe.xml
ls: cannot access '/usr/local/avamar/var/probe.xml': No such file or directory
ls -al /usr/local/avamar/var/*probe.xml*
-rw-r--r-- 1 admin admin 1050 Jan 13 13:18 probe.xml.before.resite
-rw-r--r-- 1 admin admin 1050 Jan 13 09:47 x-probe.xml
-rw-r--r-- 1 admin admin 1059 Oct 13 13:21 probe.xml-bk-20241013
-rw-r--r-- 1 admin admin 1050 Mar 23 09:47 x-probe.xml
Cause
The file may have been renamed.
The file may have been removed In error.
A cancelled execution of the dpnnetutil command can also result in a missing probe.xml.
Resolution
1. Log in to the Avamar Utility Node as admin and load the keys per Avamar: How to Log in to an Avamar Server and Load Various Keys.
2. Generate a new probe.xml file by running the following command:
avmaint networkconfig --ava > /usr/local/avamar/var/new_probe.xml_`date -I`
3. Verify that the file exists:
ls -al /usr/local/avamar/var/new_probe.xml_`date -I`
ls -al /usr/local/avamar/var/new_probe.xml_`date -I` -rw------- 1 admin admin 526 Jan 23 20:21 /usr/local/avamar/var/new_probe.xml_2025-01-23
4. Copy the file as original probe.xml file:
cp -v /usr/local/avamar/var/new_probe.xml_`date -I` /usr/local/avamar/var/probe.xml
'/usr/local/avamar/var/new_probe.xml_2025-01-23' -> '/usr/local/avamar/var/probe.xml'
5. Verify that the file has the correct permissions and ownership:
ls -al /usr/local/avamar/var/probe.xml
-rw-r--r-- 1 admin admin 1050 Jan 13 13:18 probe.xml
If the file ownership is incorrect, run the following command:
chown admin:admin /usr/local/avamar/var/probe.xml
If the file permissions are incorrect, run the following command:
chmod 644 /usr/local/avamar/var/probe.xml