Skip to main content
Answer

commvault agent installation error

  • June 2, 2022
  • 8 replies
  • 5883 views

Forum|alt.badge.img+5

Hi All,

 

I had uninstalled the commvault agent on the AIX client, however when I am trying to install the agent back its failing with error “Failed to install File System Core Package, could not determine processor/OS type of client.” Help please.

From the logs:

24980 635c  06/02 13:47:22 7545295 GetRemoteProcessorType() - SSH port is set to [], key file path is [], use passphrase [false]
24980 635c  06/02 13:47:23 7545295 GetRemoteProcessorType() - Login check succeeded on remote machine [172.17.64.134].
24980 635c  06/02 13:47:26 7545295 GetRemoteProcessorType() - Unix installation temp directory is set to [/opt/simpana/seed].
24980 635c  06/02 13:47:26 7545295 GetRemoteProcessorType() - Couldn't create the temp diretory [/opt/simpana/seed] for installation on the remote machine.
24980 635c  06/02 13:47:26 7545295 [GetClientOSType]() - Failed to compute the binary set name of client [172.17.64.134].
24980 635c  06/02 13:47:26 7545295 [GetClientOSType]() - Override software cache is set to CS cache, Setting error status for client [66]
24980 635c  06/02 13:47:26 7545295 [fnCSUpdateDBJMStatusNew]() - Client status [ QINSTALL_ERROR_CPU_TYPE] set successfully in JMQinetixUpdateStatus Table  for client [ 66] [  ]
24980 2380  06/02 13:47:26 7545295 [CheckAndDownloadRequiredMedia]() - Download is not required.

Best answer by Shahzeb

Had to manually install the agent locally.

8 replies

Forum|alt.badge.img+13

Hi @Shahzeb 

 

Whats the version of commvault client as the directory is pointing to /opt/simpana and not to /opt/commvault

 

Could you verify if the previous uninstall cleared on the directory's 

 

connect to the AIX server as root

 

ps -eaf | grep -i commvault

ps -eaf | grep -i simpana

commvault list

(If there are any process still running the above 2 commands will show)

Also verify if the following directories are still existing 

/etc/CommVaultRegistry, /opt/commvault, /var/log/commvault, /opt/simpana or /var/log/simpana 

 

Could you also confirm if you are using root account for the push install

 

Regards,

Gowri Shankar

 

 

 

 


Forum|alt.badge.img+5
  • Author
  • Byte
  • June 2, 2022

Hi Gowri,

The commvault version is 11.24, /opt/simpana is the separate filesystem created for backup files.

we are using service account with sudo access to push install and had confirmed no commvault folder or process was running.


Forum|alt.badge.img+5
  • Author
  • Byte
  • June 2, 2022

@Gowri Shankar do we need to ‘reconfigure’ client post uninstallation to install back?


Forum|alt.badge.img+13

Hi @Shahzeb,

 

No need to reconfigure the client

Got it /opt/simpana is a mount path 

could you paste the output of

ls -l /opt | grep -i simpana

ls -l /opt/simapna

 

 

 


Forum|alt.badge.img+5
  • Author
  • Byte
  • Answer
  • June 7, 2022

Had to manually install the agent locally.


Mike Struening
Vaulter
Forum|alt.badge.img+23

Thanks for sharing your solution, @Shahzeb !


Forum|alt.badge.img+3
  • Byte
  • September 1, 2025

I had the same error on a windows 2025 server. I had installed the agents as restore only. After uninstalling and attempting to reinstall the File System and File System core agents it displayed “Failed to install File System Core Package, could not determine processor/OS type of client.” 
Actions ,
1. Removed the Commvault folder and registry keys - attempt to install with a push install failed withe same error, Also not asked for username or password during the install attempt either as the session cached my credentials  
2. Rebooted the VM - attempted the install again, got the same message
3. Closed my console session, logged in and  attempted it again which worked  with no errors. 
The message Install Software successful appeared in the client status after 10 mins, but the progress remained at 0 %. When I tried to suspend the install job it completed. 


  


Forum|alt.badge.img+3
  • Byte
  • September 1, 2025

when I installed the File System agent as restore only it released the client license. I had to reconfigure the client