Loading...
Loading...
Observed Symptoms The dpnctl start command fails with the error:" dpnctl: ERROR: unable to determine \"isclean\" status of Avamar server because no storage nodes responded " Traceback messages appear in the dpnctl output: admin@avamar:~/>: dpnctl start Identity added: /home/admin/.ssh/admin_key (/home/admin/.ssh/admin_key) - - - - - - - - - - - - - - - - - - - - Action: starting all Have you contacted Avamar Technical Support to ensure that this is the right thing to do?Answering y(es) proceeds with starting all; n(o) or q(uit) exitsy(es), n(o), q(uit/exit): y dpnctl: INFO: Checking that gsan was shut down cleanly... dpnctl: ERROR: unable to determine "isclean" status of gsan because no storage nodes responded dpnctl: ERROR: traceback on exit: main::gsan_is_clean (/usr/local/avamar/bin/dpnctl line 2118) main::gsan_restart (/usr/local/avamar/bin/dpnctl line 3338) main::dpn_up (/usr/local/avamar/bin/dpnctl line 5426) main::handle_top_level_command (/usr/local/avamar/bin/dpnctl line 6492 The restart.dpn comand fails as it failed to ping the node: Using /usr/local/avamar/var/probe.xml ping: socket: Operation not permitted ping: socket: Operation not permitted ping: socket: Operation not permitted ping: socket: Operation not permitted ping: socket: Operation not permitted node 0.0 [xx.xxx.xx.xx] not responsive, removing from list - xx.xxx.xx.xx did not respond to ICMP ping Ping commands return the output below (and nodes are reported as not responsive): admin@avamar:~/>: ping xx.xxx.xxx.xx ping: socket: Operation not permitted
The ping executable had incorrect file permissions, preventing it from creating raw sockets. This caused the “ ping: socket: Operation not permitted ” errors and the dpnctl failure to determine the Avamar server “ isclean ” status.
Log in to the Avamar Utility Node as admin. Elevate to root Verify the current permissions of the ping binary: root@avamar:/usr/bin/#: ls -al | grep ping -rwxr-xr-x 1 root root 60464 Dec 6 15:57 ping lrwxrwxrwx 1 root root 4 May 12 12:49 ping6 -> ping -rwxr-xr-x 1 root root 10632 Oct 15 2024 rmcp_ping -rwxr-xr-x 1 root root 18536 Dec 11 2023 snmpping If incorrect, change the ownership and set the set‑uid bit on the ping binary by running the following command (and verify): chmod 4755 /usr/bin/ping root@avamar:/usr/bin/#: ls -lah ping -rwsr-xr-x 1 root root 60K Dec 6 08:57 ping Retry the workflow using“Retry Current Task” If the problem persists, Create a Service Request with the Dell Avamar Technical Support team.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.