Article ID: 122021, created on Jun 13, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux 4.7
  • Virtuozzo hypervisor

Symptoms

When you run pbackup with -c %config% option similar output is printed:

# pbackup -c /etc/entreprise.vzbackup.conf -a -p
You are using a deprecated utility that will be dropped in the next major
release. Please use prlctl backup instead.

ssh: Could not resolve hostname -c: Name or service not known
2014-06-11T18:27:54+0200 pbackup(808593): Error: Can't get full host name for node -c
2014-06-11T18:27:54+0200 pbackup(808593): Error: Backup for node -c will not be created, skipped
ssh: Could not resolve hostname /etc/entreprise.vzbackup.conf: Name or service not known
2014-06-11T18:27:54+0200 pbackup(808593): Error: Can't get full host name for node /etc/entreprise.vzbackup.conf
2014-06-11T18:27:54+0200 pbackup(808593): Error: Backup for node /etc/entreprise.vzbackup.conf will not be created, skipped
ssh: Could not resolve hostname -a: Name or service not known
2014-06-11T18:27:54+0200 pbackup(808593): Error: Can't get full host name for node -a
2014-06-11T18:27:54+0200 pbackup(808593): Error: Backup for node -a will not be created, skipped
ssh: Could not resolve hostname -p: Name or service not known
2014-06-11T18:27:54+0200 pbackup(808593): Error: Can't get full host name for node -p
2014-06-11T18:27:54+0200 pbackup(808593): Error: Backup for node -p will not be created, skipped
2014-06-11T18:27:54+0200 pbackup(808593): Nodes list is empty

Cause

Error takes place because option "-c" and the path to configuration file are treated as a list of nodes.

The issue has been recognized as a product bug #PSBM-27470.

Resolution

The fix is included in Parallels Cloud Server 6.0 Update 8 (6.0.8-2536).

Search Words

Could not resolve hostname -c: Name or service not known

Name or service not known

Could not resolve hostname

Nodes list is empty

Can't get full host name for node -c

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 0dd5b9380c7d4884d77587f3eb0fa8ef 0c05f0c76fec3dd785e9feafce1099a9 c62e8726973f80975db0531f1ed5c6a2

Email subscription for changes to this article
Save as PDF