Commvault Simpana 9 Linux push deployment failure

Wanted to post about a very common Linux push deployment failure, infact I do believe this is applicable to other Unix platforms, so be sure to check this common thing against other Unix platforms.

An attempt to push Simpana 9 Linux File System iDA (and/or other iDA’s) will result in a failure like below, I’ll name the logs the information is obtained from so end readers can follow along.

[DistributeSoftware.log]

3000 ea4 04/09 19:29:18 27 CCvPatchesUpdateDBClient::InstallUnixSeed STDERR[]
3000 ea4 04/09 19:29:18 27 CCvPatchesUpdateDBClient::InstallUnixSeed STDOUT[*** UNIX SEEDING SETUP_ERROR 2042 detected and returned. ***
]

3000 9f8 04/09 19:29:28 27 ****** Now Check status of all clients ******
3000 9f8 04/09 19:29:28 27 Check status started for client [192.168.11.24][-1]
3000 9f8 04/09 19:29:58 27 Clients Failed:
3000 9f8 04/09 19:29:58 27 Client [-1] [192.168.11.24] [QINSTALL_BASE_PACKAGE_FAILED]
3000 9f8 04/09 19:29:58 27 *******************************************

3000 9f8 04/09 19:29:58 27 Job Failed.
3000 9f8 04/09 19:29:58 27 COMPLETE CALLED (JOB Status::FAIL), Job ID = 27

The most common cause for this failure is the client has a hosts file that is configured like so;

[/etc/hosts] – Bad version

127.0.0.1 localhost ldebx86-1.lab.libobk.so ldebx86-1

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Essentially your clients primary hostname and FQDN has been associated to a localhost entry. Modify the hosts file so that these hostname entries are defined against your primary interface that the machine has, as shown below;

[/etc/hosts] – Good version

127.0.0.1 localhost
192.168.11.24 ldebx86-1.lab.libobk.so ldebx86-1

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

This would have to be one of the most common issues for a push deployment.

If you attempted an interactive installation on this client when the hosts file was in the bad state, you would get the failure below during interactive install which will clearly indicate the problem.

Simpana 9.0.0 (BUILD84) Linux glibc2.11
——————————————————————————-
Physical Machine Host Name

We found one network interface available on your machine. We will associate it
with the physical machine being installed, and it will also be used by the
CommServe to connect to the physical machine. Note that you will be able to
additionally customize Datapipe Interface Pairs used for the backup data
traffic later in the Simpana Java GUI.

Please check the interface name below, and make corrections if necessary:

Physical Machine Host Name: ldebx86-1.lab.libobk.so

*** We found that /etc/hosts file associates name you provided
*** (ldebx86-1.lab.libobk.so) with loopback address.
*** Please check the /etc/hosts file and make corrections if necessary to
*** remove this association, or provide a new Host Name.

Press <ENTER> to try again …

If this post assists you, please leave comments.

One thought on “Commvault Simpana 9 Linux push deployment failure”

  1. Thanks. That worked a treat !

    Also something else I need to tidy up on my template VM (remove template host and ip from hosts file).

    Cheers
    Ian

Leave a Reply

Your email address will not be published. Required fields are marked *