Avamar: The opstatus.dpn and mapall do not work as root

Summary: Various commands like opstatus.dpn or mapall do not work when run as root user. The same commands work fine as admin.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The commands return "command not found" error message. Examples: 
root@avamar:/etc/#: opstatus.dpn
bash: opstatus.dpn: command not found

root@avamar:/etc/#: mapall date
bash: mapall: command not found
This issue can also manifest itself during the upgrade as a workflow failure. 
2023-10-31 09:30:09 (-0700) 47186921601720 INFO: Report home message: 2023-10-31 09:30:09 -0700|avamar|19.4.0-116|AvamarUpgrade|19.7.0.82|/data01/avamar/repo/temp/AvamarUpgrade-19.7.0-82.avp_1698768559958/tmp|ValidateSystemIsUp|Validating System is Up (21 of 159)|ERROR: ValidateSystemIsUp::rescue in do  an unexpected problem occurred while determining gsan status: opstatus.dpn produced a shell error: /usr/local/avamar/var/run_command-tmpscript.45254.47186921601720: line 5: opstatus.dpn: command not found; exit status=127 - operation failed
2023-10-31 09:30:09 (-0700) 47186921601720 ERROR: an unexpected problem occurred while determining gsan status: opstatus.dpn produced a shell error: /usr/local/avamar/var/run_command-tmpscript.45254.47186921601720: line 5: opstatus.dpn: command not found; exit status=127 - operation failed
2023-10-31 09:30:09 (-0700) 47186921601720 INFO: post: an unexpected problem occurred while determining gsan status: opstatus.dpn produced a shell error: /usr/local/avamar/var/run_command-tmpscript.45254.47186921601720: line 5: opstatus.dpn: command not found; exit status=127 - operation failed
2023-10-31 09:30:09 (-0700) 47186932806380 INFO: >>> [make_temp_script] 222 very_current_user=root, as_user=root, ssh command is: (/bin/tar -zcvf /usr/local/avamar/var/avi/server_data/package_data/AvamarUpgrade-19.7.0-82.avp_1698768559958/workflow_log_1698769809332.tar.tgz -C /data01/avamar/repo/temp/AvamarUpgrade-19.7.0-82.avp_1698768559958/tmp workflow.log) >/usr/local/avamar/var/run_command-sysout.45254.47186932806380 2>&1
2023-10-31 09:30:09 (-0700) 47186921601720 INFO: - - - - - - - BEGIN(output) - - - - - - -
2023-10-31 09:30:09 (-0700) 47186921601720 INFO: workflow.log

The environment variable $PATH shows incorrect content where the Avamar paths are missing: 
root@avamar:/etc/#: echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/bin/selview:/usr/bin/syscfg:/usr/bin/sysinfo:/usr/bin/flashupdt

Cause

In Avamar 19.2 and higher, the underlying operating system (SLES 12 or higher) is based on systemd. The default configuration of the environment variables in a systemd system is performed using several configuration files in /etc/profile.d directory. It may happen that there is a leftover configuration file .bashrc from the previous OS version (or a file created manually) under /root directory. That file is run AFTER the /etc/profile.d scripts and overwrites the correct variables.

Resolution

1. Rename the file as the root user. 
mv /root/.bashrc /root/.bashrc_old
2. Exit the root shell 
exit
3. Re-enter the root shell 
su -
If the issue was causing the upgrade workflow to fail, resume the workflow.

Affected Products

Avamar Server
Article Properties
Article Number: 000219092
Article Type: Solution
Last Modified: 05 Aug 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.