Hey @Bloopa,
Couple of things to check.
- Can you try set permissions to 777 or 755 on the installation files / directory?
- Can you check if libxcrypt.x86_64 and libnsl.x86_64 are installed. This issue sometimes occurs if those packages are missing on the host.
Thank you @Damian AndreÂ
on the folder I had copied I ran the following commands :
chown -R root:root /packagefolder
chmod -R 755 /packagefolder
Â
Do you know why I can’t see the mediaAgent checkbox ? I am using latest COmmvault Version 11.22
p] File System Core
b] File System
b] CommCell COnsole
b] Oracle
b] DB2
b] Developer SDK - Python
b] Index Gateway
Â
Â
I have tried try to rebuild the package,
v11 Download Manager with Feature Release 22
download packages to install on different computer
select Unix and Linux-x64-x86 checkboxes
select PackagesÂ
choose download location C:DownloadPkg
select Unix Packages
ServerÂ
/x] MediaAgent
File SystemÂ
x] File System Core
x] File SystemÂ
Latest Maintenance release
After that, I have transfered the package on the linux media agent and executed it.
I think I have missed something.
Hope you would have checked it already, if not I would suggest to verify your existing CentOS version with its respective required glibc version..
https://documentation.commvault.com/commvault/v11/article?p=2822.htm
Â
Â
Thanks @Anuj
COmmvault recommend Red Hat Enterprise Linux/CentOS 8.x with glibc 2.17.x
and I have :
OS : CentOS Linux release 8.3.2011
Â
glib versionÂ
Nom      : glibc
Version    : 2.28
Publication  : 127.el8
Architecture : i686
Taille    : 3.4 M
Source    : glibc-2.28-127.el8.src.rpm
Dépôt     : baseos
Â
it’ s a Vmware workstation lab. Can it be a Commvault limitation for example if the VM does not have sufficient memory ?
vm spec
SSD, 4 vcpu, 8 GB memory
Â
Hi,
Before you install the Commvault software on Centos 8 with glibc 2.28.x , you must manually install the libxcrypt.x86_64 and libnsl.x86_64 packages on the computer.
Â
yum install libxcrypt libnsl
Â
Regards,
Steve
Hi,
Before you install the Commvault software on Centos 8 with glibc 2.28.x , you must manually install the libxcrypt.x86_64 and libnsl.x86_64 packages on the computer.
Â
yum install libxcrypt libnsl
Â
Regards,
Steve
Â
Thanks Steve,
Here is the ouptutÂ
ptesteur@localhost ~]$ sudo yum install libxcrypt libnsl
bsudo] Mot de passe de testeur :Â
Dernière vérification de l’expiration des métadonnées effectuée il y a 4:11:15 le mer. 24 févr. 2021 09:01:22 CET.
package libxcrypt-4.1.1-4.el8.x86_64 is already installed
package libnsl-2.28-127.el8.x86_64 is already installed
Dépendances résolues.
Â
and when I run ./cvpkgadd can’t select MediaAgent
Â
A] File System Core
i] File System
>] CommCell COnsole
o] Oracle
<] DB2
c] Developer SDK - Python
e] Index Gateway
it’ s a Vmware workstation lab. Can it be a Commvault limitation for example if the VM does not have sufficient memory ?
vm spec
SSD, 4 vcpu, 8 GB memory
Â
Hi Bloopa, You need at least 16GB on your vm
it’ s a Vmware workstation lab. Can it be a Commvault limitation for example if the VM does not have sufficient memory ?
vm spec
SSD, 4 vcpu, 8 GB memory
Â
Hi Bloopa, You need at least 16GB on your vm
Hi @Anuj I remember that with previous version of Commvault I was able to Install a full lab with limited resources. Is it limited from the new version ? Is there any chance to use my LAB with minimum resources ?
Â
Â
Â
it’ s a Vmware workstation lab. Can it be a Commvault limitation for example if the VM does not have sufficient memory ?
vm spec
SSD, 4 vcpu, 8 GB memory
Â
Hi Bloopa, You need at least 16GB on your vm
Hi @Anuj I remember that with previous version of Commvault I was able to Install a full lab with limited resources. Is it limited from the new version ? Is there any chance to use my LAB with minimum resources ?
Â
Â
Â
Typically we don’t limit options available based on system resources, so I don’t think its that. I’m not sure why the MA is not appearing without looking at installer logs, but here is a workaround you can try. Just install FS or FS core, and then from the Commvault UI (command center or commcell console), deploy the Media agent from there. It will push the install through the existing FS agent so you won't need to open any additional ports (ssh etc).
it’ s a Vmware workstation lab. Can it be a Commvault limitation for example if the VM does not have sufficient memory ?
vm spec
SSD, 4 vcpu, 8 GB memory
Â
Hi Bloopa, You need at least 16GB on your vm
Hi @Anuj I remember that with previous version of Commvault I was able to Install a full lab with limited resources. Is it limited from the new version ? Is there any chance to use my LAB with minimum resources ?
Â
Â
Â
Typically we don’t limit options available based on system resources, so I don’t think its that. I’m not sure why the MA is not appearing without looking at installer logs, but here is a workaround you can try. Just install FS or FS core, and then from the Commvault UI (command center or commcell console), deploy the Media agent from there. It will push the install through the existing FS agent so you won't need to open any additional ports (ssh etc).
Hi Damian and all guys,
Â
Thanks for your answer.
Â
I have found what was the issue
just after my fresh CentOs installation I don't specify a hostname, I use the default one localhost.localdomain
when I launch the cvpkgadd I had thisÂ
x] 192.168.153.13 Â Â Â localhost.localdomain
l] 192.168.122.1 Â Â Â localhost.localdomain
and after, this
if I click next I have only those options :
n] File System Core
>] File System
<] CommCell COnsole
>] Oracle
n] DB2
]] Developer SDK - Python
v] Index Gateway
After changing the hostname on my centos to the real one ma01.lab.local
here is what I have
>x] 192.168.153.13 Â Â Â ma01.lab.local
3] 192.168.122.1 Â Â Â ma01.lab.local
2] File System Core
<] File System
m] MediaAgent
] Storage Accelerator
r] CommCell Console
r] Documentum
C] Oracle
] SAP for Oracle
c] SAP for Hana
r] Cassandra
f] SAP for MaxDB
1/5
I don’t understand why but that's what matters.
Hello,
Â
Definitively it was a user privileges issue and not an interface issue.
launching the ./cvpkgadd with root user are via sudo works and the media Agent package appears now.
Â