Scribd
Upload
13 views3 pages

VDP Error Nospace

The vSphere Data Protection appliance fails to connect to vCenter Server due to full disk space, resulting in various error messages. To resolve this, users must free up disk space by deleting unnecessary files, particularly log files, and then restart the appliance or the dpnctl services. The document provides detailed steps for checking disk usage and managing files to alleviate the issue.

Uploaded by

toner22489
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views3 pages

VDP Error Nospace

The vSphere Data Protection appliance fails to connect to vCenter Server due to full disk space, resulting in various error messages. To resolve this, users must free up disk space by deleting unnecessary files, particularly log files, and then restart the appliance or the dpnctl services. The document provides detailed steps for checking disk usage and managing files to alleviate the issue.

Uploaded by

toner22489
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Page 1 of 3

Knowledge Base

Connecting the vSphere Data Protection appliance to vCenter Server fails with the error: N

Symptoms

• vSphere Data Protection (VDP) appliance fails to connect to vCenter Server


• Manually starting the dpnctl services fails
• When you reboot the VDP appliance, you see the error:

No space left on device

• In the vdr-server.log file, located at /usr/local/avamar/var/vdr/server_logs/, you see entries similar

2012-12-21 18:13:00,965 WARN [Timer_vc]-vi.VCenterEventProcessor: resetVIAccess f


java.rmi.RemoteException - VI SDK invoke exception:java.net.SocketException: Netwo
2012-12-21 18:13:00,972 INFO [Timer_vc]-httpclient.HttpMethodDirector: I/O except
when processing request: Network is unreachable
2012-12-21 18:13:00,973 INFO [Timer_vc]-httpclient.HttpMethodDirector: Retrying
2012-12-21 18:13:00,973 INFO [Timer_vc]-httpclient.HttpMethodDirector: I/O except
when processing request: Network is unreachable
2012-12-21 18:13:00,973 INFO [Timer_vc]-httpclient.HttpMethodDirector: Retrying
2012-12-21 18:13:00,973 INFO [Timer_vc]-httpclient.HttpMethodDirector: I/O except
when processing request: Network is unreachable
2012-12-21 18:13:00,973 INFO [Timer_vc]-httpclient.HttpMethodDirector: Retrying
2012-12-21 18:13:00,974 INFO [Timer_vc]-http.HTTPSender: Unable to sendViaPost to
[https://vcenter.vmware.com:9443/services/mcService?wsdl]
java.net.ConnectException: Network is unreachable

• In the dpnctl.log file, located at /usr/local/avamar/var/log/, you see entries similar to:

dpnctl: ERROR: problem closing run-self aux script "/tmp/dpnctl-run-self.11800"


dpnctl: ERROR: traceback on exit:
dpnctl_util::abend (/usr/local/avamar/bin/../lib/dpnutils/dpnctl_identity.pm line
dpnctl_identity::__ANON__ (/usr/local/avamar/bin/../lib/dpnutils/dpnctl_identity.p
dpnctl_identity::re_exec_with_ssh_context (/usr/local/avamar/bin/../lib/dpnutils/d
dpnctl_identity::set_identity (/usr/local/avamar/bin/dpnctl line 5720)
main::set_up_run_context (/usr/local/avamar/bin/dpnctl line 5580)
main::dpn_status (/usr/local/avamar/bin/dpnctl line 6286)
main::handle_top_level_command (/usr/local/avamar/bin/dpnctl line 6423)

Cause

This issue occurs because the disk space in the VDP appliance is full.
Page 2 of 3

Resolution

To resolve this issue, you must free up disk space in the VDP appliance.

To free up space in the VDP appliance:

1. Log in to the VDP appliance using SSH with root credentials.


2. Stop dpnctl services. Run this command as the root user:

dpnctl stop all

This command stops:


◦ hfscheck
◦ MCS
◦ gsan
◦ axionfs

3. Run this command to view the free space left on the appliance:

df -h

You see output similar to:

Filesystem Size Used Avail Use% Mounted on


/dev/sda2 7.9G 7.9G 0 100% /
devtmpfs 1.9G 136K 1.9G 1% /dev
tmpfs 1.9G 0 1.9G 0% /dev/shm
/dev/sda1 130M 38M 86M 31% /boot
dev/sda7 1.5G 304M 1.1G 22% /var
/dev/sda9 77G 2.1G 71G 3% /space
/dev/sdb1 256G 6.7G 250G 3% /data01
/dev/sdc1 256G 1.7G 255G 1% /data02
/dev/sdd1 256G 1.7G 255G 1% /data03

This sample output indicates that the appliance does not have any free space on /dev/sda2, which is mounted on /

4. To change the directory to /usr/local/avamarclient/ and display any large files, run the command:

cd /usr/local/avamarclient/ && du –h

You see output similar to:

root@vcloud-backup:/usr/local/avamarclient/#: du -h
24K ./man
8.3M ./bin/logs
7.4M ./bin/MountPoint
218M ./bin
4.0K ./var-proxy-7/vmware/temp
8.0K ./var-proxy-7/vmware
1017M ./var-proxy-7
4.0K ./etc/scripts
4.0K ./etc/avtar
120K ./etc
4.0K ./var-proxy-5/vmware/temp
8.0K ./var-proxy-5/vmware/VMFiles/1
8.0K ./var-proxy-5/vmware/VMFiles/4
8.0K ./var-proxy-5/vmware/VMFiles/2
8.0K ./var-proxy-5/vmware/VMFiles/3
36K ./var-proxy-5/vmware/VMFiles
44K ./var-proxy-5/vmware
1.2G ./var-proxy-5
4.0K ./var-proxy-4/vmware/temp
Page 3 of 3

8.0K ./var-proxy-4/vmware
984M ./var-proxy-4

This example output indicates that var-proxy-4 is consuming around 1GB of file space. The var-proxy
avagent_*.log files are located in /usr/local/avamarclient/var-proxy-*/.

2. Move or delete any files that are utilizing the disk space.

Note: Ensure that you do not delete any configuration or data files. Log files are the safest to delete.
3. Power cycle the appliance to restart the dpnctl services and connect to vCenter Server.

Note: Alternatively, you can start the dpnctl services by running one of these commands as the root user:

dpnctl start all


dpnctl start all -- verbose

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature (http://www.vmware.com/conta
Permalink to: Connecting the vSphere Data Protection appliance to vCenter Server fails with the error: No space left on device (http://kb.vmware.com/k
Read our blog (http://blogs.vmware.com/kb/) Watch KBTV (http://blogs.vmware.com/kbtv/) Follow us (http://www.twitter.com/vmwarekb)
request.html)

1 (javascript:void( rate(1,this) ))
2 (javascript:void( rate(2,this) ))
3 (javascript:void( rate(3,this) ))
4 (javascript:void( rate(4,this) ))
5 (javascript:void( rate(5,this) ))
11 Ratings
Actions
Bookmark Document (javascript:addBookmark(actionBoxUtil.docURL, actionBoxUtil.docTitle);)
Copy URL (javascript:ClipBoard())
Email Document (javascript:emailDoc(actionBoxUtil.extId, actionBoxUtil.sliceId, actionBoxUtil.docTitle, actionBoxUtil.cpplayer, actionBoxUtil.bbid))
Print Document (javascript:window.print())
Subscribe to Document (/selfservice/microsites/microsite.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2042185&format=rss)

(http://www.addthis.com/bookmark.php?v=250&username=xa-4b5f42f36e60a29e)

KB: 2042185

Updated: Sep 5, 2013


Categories:
Troubleshooting
Languages:
English

Product(s):
VMware vSphere Data Protection

Product Version(s):
VMware vSphere Data Protection 5.1.x

You might also like