Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
VMware backup proxy activation fails because of special characters in the hostname
VMware backup proxy activation fails because of special characters in the hostname
Updated over 8 months ago

This article applies to:

  • Product edition: Phoenix

Problem description

Activation of VMware backup proxy fails on CentOS if its hostname contains underscore, spaces, or special character.

Cause

Hostname contains underscore, spaces, or special characters.

Traceback


πŸ“ Note
​

[2018-05-17 0110:24,702] [INFO] Setting Hostname [Druva_Phoenix_test][2018-05-17 01:10:24,708] [ERROR] Underscore are not allowed in hostname[2018-05-17 01:10:24,708] [ERROR] Error <type 'exceptions.Exception'>:Host name contains underscore.. Traceback -Traceback (most recent call last):  File "__main__proxySetup__.py", line 483, in setup  File "__main__proxySetup__.py", line 246, in set_host_nameException: Host name contains underscore.[2018-05-17 01:10:24,708] [INFO] Stopping the Phoenix service...[2018-05-17 01:10:27,430] [INFO] Phoenix service stopped successfully


​
Or
​
​

[2018-05-17 01:38:55,382] [INFO] Pinging :backup-phoenix.druva.com[2018-05-17 01:38:57,746] [INFO] Phoenix server pinged successfully.[2018-05-17 01:38:57,746] [INFO] Setting Hostname [Druva Phoenix test][2018-05-17 01:38:57,752] [ERROR] Spaces are not allowed in hostname[2018-05-17 01:38:57,752] [ERROR] Error <type 'exceptions.Exception'>:Host name contains spaces.. Traceback -Traceback (most recent call last):  File "__main__proxySetup__.py", line 483, in setup  File "__main__proxySetup__.py", line 242, in set_host_nameException: Host name contains spaces. [2018-05-17 01:38:57,752] [INFO] Stopping the Phoenix service...

Resolution

Provide a hostname without spaces, underscore, or special characters.


Did this answer your question?