While installing robot on Linux server we are getting the What is the installation file called? as [install_LINUX]

[gayathri Buddhi]

Hi All,
,
We are facing the new issue while installation robot on Linux server. In What is the installation file called? we are getting as [install_LINUX] instead of

LINUX_23_64. 

What could be the issue.

Below is the installation process we have done

root@xxxxxxx:/opt/UIM-ROBOT/LINUX_23_64# ./nimldr
=============================================
nimldr version 3.57 Dec 1 2014
Copyright(c) 2012, CA. All rights reserved.
=============================================

This program will help you install the Nimsoft infrastructure components (such as a robot or a secondary hub) on the current system.

You will be given a series of questions, default answers are in brackets.

Example: <Question>? ==>[default]

Pressing Enter directly will use the default value, otherwise you should
type in the requested information.

If express installation is specified, the default value will be used
automatically.

A log of the installation can be found in the file: nimldr.log

Hit Enter/Return key to continue.

1 - ens160 (IPv4): xxxxxxx

Select the number of the IP you would like to use for this robot from those listed above: 1

You selected IP #1: xxxxxxx

WARNING: The temporary files directory is removed after installation!

Where should nimldr store temporary files?
==>[/opt/nimsoft/tmp] /opt/UIMROBOT
Beginning Robot installation:

Is this a Cloud installation?
==>[no]

Do we have the installation file locally?
==>[no]

Is there a host running a Nimsoft Hub we can query for the installation file?
==>[yes]

What is the IP address of the host running a Nimsoft Hub?
==>[]xxxxxxxxx

Preparing to search for Archives:

What is the Nimsoft Domain called (*=search)?
==>[SpecCo_domain]

What is the Nimsoft Hub called (*=search)?
==>[SpecCo_PHub]

What is the installation file called?
==>[install_LINUX]

Searching for Archives:

We need to log in to NMS to query for available archives

Attempting to log in to NMS...
Enter Nimsoft username and password...
Username: administrator
Password:
1 /SpecCo_domain/SpecCo_PHub/xxxxxxxx/distsrv

Failed to find install_LINUX in Archive
root@xxxxxxx:/opt/UIM-ROBOT/LINUX_23_64#

Thanks,
Gayathri.

[Stephen Danseglio]

Is the Linux installation file  (install_linux_xxx file ) present in the archive of that hub?

If not, setup distrv forwarding forwarding for the install_LINUX_23_64.zip installer to the remote hub from the Primary hub.

How to Setup distsrv Package Forwarding in UIM?
https://knowledge.broadcom.com/external/article?articleId=34258

Alternatively you can copy the install file on to the remote server and follow the KB below for install using the install file locally.

I can't install a linux robot with nimldr (can't find the installation files)
https://knowledge.broadcom.com/external/article/7074/i-cant-install-a-linux-robot-with-nimldr.html

Steve

This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

[Garin Walsh]

Also in my experience, when it is looking for [install_LINUX] that means that you are trying to install on an unsupported OS version.

Do make sure you have the most recent nimldr and associated files to make sure. 

not that it's a sure thing but the date stamp on your nimldr output is 2014 which is kind of old.

[gayathri Buddhi]

Hi Garin,

We have followed your suggestion but downloading latest nimldr and tried for installing the robot. Now we are getting the error as

Error copying files, aborting
Cleaning up temporary files
Failed to install robot - exiting...
root@xxxxxxx:/opt/LINUX_23_64#

[Garin Walsh]

It's really helpful to have the whole command output otherwise you are making people guess at what might have caused this.

One thing you can try that's helpful is to run nimldr with the arguments "-d 5" which will cause detailed messaging to be written to a log file in the same directory.

Also try running the install taking all the defaults and making the minimum changes possible. It appears that you have copies sections of the tar file around for instance.

Instead just create a directory, cd into the directory, extract the nimsoft nimldr tar file, cd into the correct arch directory, if nimldr isn't executable, do a chmod 755 on it, then issue "./nimldr -d 5"

Take the defaults except where it's necessary to supply a value or the default doesn't apply.

[gayathri Buddhi]

Hi Grain,

Please find the whole commands. And please let me know if any.

root@XXXXX:/opt# cd LINUX_23_64
root@XXXXX:/opt/LINUX_23_64# ls -lrt
total 2156
-rwxrwxrwx 1 parfunc users 2201184 Aug 8 2019 nimldr
-rw-r--r-- 1 root root 1167 May 17 15:38 nimldr.log
root@XXXXX:/opt/LINUX_23_64# ./nimldr
=============================================
nimldr version 9.20 [Build 9.20.1747, Aug 8 2019]
Copyright(c) 1998-2019, CA. All rights reserved.
=============================================

This program will help you install the Nimsoft infrastructure components (such as a robot or a secondary hub) on the current system.

You will be given a series of questions, default answers are in brackets.

Example: <Question>? ==>[default]

Pressing Enter directly will use the default value, otherwise you should
type in the requested information.

If express installation is specified, the default value will be used
automatically.

A log of the installation can be found in the file: nimldr.log

Hit Enter/Return key to continue.

1 - ens160 (IPv4): XXXXXX

Select the number of the IP you would like to use for this robot from those listed above: 1

You selected IP #1: XXXXXX

WARNING: The temporary files directory is removed after installation!

Where should nimldr store temporary files?
==>[/opt/nimsoft/tmp] /opt/UIMROBOT
Beginning Robot installation:

Is this a Cloud installation?
==>[no]

Do we have the installation file locally?
==>[no]

Is there a host running a Nimsoft Hub we can query for the installation file?
==>[yes]

What is the IP address of the host running a Nimsoft Hub?
==>[] XXXXXX

Preparing to search for Archives:

What is the Nimsoft Domain called (*=search)?
==>[SpecCo_domain]

What is the Nimsoft Hub called (*=search)?
==>[SpecCo_NA_RHub01]

What is the installation file called?
==>[install_LINUX] install_LINUX_23_64

Searching for Archives:

We need to log in to NMS to query for available archives

Attempting to log in to NMS...
Enter Nimsoft username and password...
Username: administrator
Password:
1 /SpecCo_domain/SpecCo_NA_RHub01/sbyvmntuim08p/distsrv
Beginning download of install_LINUX_23_64
-
Done!

What are we installing? (1=Robot,2=Infrastructure)
==>[1] 1
Extracting files from archive /opt/UIMROBOT//install_LINUX_23_64.zip to temp directory /opt/UIMROBOT/

Where should NMS be installed?
==>[/opt/nimsoft] /opt/UIMROBOT

Automatically unregister Robot from Hub on termination?
==>[no]

Should this Robot run in passive mode?
==>[no]

What is this Nimsoft Domain called?
==>[SpecCo_domain]

Which Nimsoft Hub should this Robot connect to?
==>[SpecCo_NA_RHub01]

What is that Nimsoft Hub's IP address?
==>[XXXXXXXX]
Error copying files, aborting
Cleaning up temporary files
Failed to install robot - exiting...
root@XXXXXX:/opt/LINUX_23_64#

[Andrew Cooper]

2 things about this install process
First you are using the target directory /opt/nimrobot as the temporary directory
Where should nimldr store temporary files?
==>[/opt/nimsoft/tmp] /opt/UIMROBOT

As a matter of policy we have found it best on Unix systems (specifically Linux in our case) to do the install from the a temp location (eg /var/tmp/uim) and to specify a temp location (eg /var/tmp/uimtmp) outside the install location (eg /opt/nimsoft)

The other thing we do is have an install package which includes the tar file (so doesn't need to get from an archive) this way we know exactly which package (and version) is being used by the installer.

Regards, Andrew

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------

[Garin Walsh]

What I was getting at: don't change the defaults unless absolutely required - moving the temp files for instance could be all of your problem.

Also the installer can't figure out what the OS architecture is for your instance of Linux as indicated by.

What is the installation file called?
==>[install_LINUX] install_LINUX_23_64

Again, you are changing the default which means that the installer can't figure out the correct answer. Generally speaking, if the installer is disagreed with then your install will not work.

So, what OS are you trying to install on? And is it in the supported matrix?

And run nimldr with the "-d 5" flags so that you get a detailed log file.

[gayathri Buddhi]

Hi Garin, 

Please find the logfile that i have uploaded in which I have given the command "-d 5"

Thanks,
Gayathri.

Attachment(s)

esifflv01_nimldr_log.txt   46 KB 1 version

[Garin Walsh]

Don't override the temp file location. Or if you do, make sure that you use /opt/UIMROBOT/tmp and NOT the root directory of /opt/UIMROBOT.

It looks like your OS version is in the list of supported versions (https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/installing/product-compatibility/ca-uim-compatibility-matrix.html)which means that you might be dealing with a defect here between the installer and your Ubuntu version.

[Andrew Cooper]

Building on Gavin's reply if you must change the default temp folder ( /opt/nimsoft/tmp ) put it in a temp location such as /var/tmp and see if it installs but putting the temp fles in the install location is never a good idea (for any application).

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------

[gayathri Buddhi]

Hi Andrew,

Now we are getting the new error 

Attempting to log in to NMS...
Enter Nimsoft username and password...
Username: administrator
Password:
1 /SpecCo_domain/SpecCo_PHub/XXXXXXXX/distsrv
Beginning download of install_LINUX_23_64
\
Done!

What are we installing? (1=Robot,2=Infrastructure)
==>[1] 1
Extracting files from archive /opt/UIMRobot//install_LINUX_23_64.zip to temp directory /opt/UIMRobot/

Where should NMS be installed?
==>[/opt/nimsoft] /opt/UIMRobot

Automatically unregister Robot from Hub on termination?
==>[no]

Should this Robot run in passive mode?
==>[no]

What is this Nimsoft Domain called?
==>[SpecCo_domain]

Which Nimsoft Hub should this Robot connect to?
==>[SpecCo_PHub]

What is that Nimsoft Hub's IP address?
==>[1XXXXXXXXX]
Job for nimbus.service failed because the control process exited with error code. See "systemctl status nimbus.service" and "journalctl -xe" for details.
There was an error executing the command:
system("/opt/UIMRobot//bin/inst_init.sh");
The error code was: 256
Your installation may not be complete
Cleaning up temporary files
Finished Robot installation!
root@XXXXXXXX:/opt/LINUX_23_64# ./nimldr -d 5

[Andrew Cooper]

You are still using the install directory as the temp directory, it is trying to overwrite itself.  Make sure that the temp dorectory is different from the install/target directory.

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------

[James Christensen]

As advised do not use the installation directory as the designated temp directory. the nimldr install script cleans up the temp directory (deletes it). Therefore, you installed the robot and then deleted it before it ever got started.. If you want to use /opt/UIMrobot, then specify the temp directory as /opt/UIMRobot/tmp. 
Hopefully you got this sorted out and resolved. If not, let us know.

------------------------------
[Designation]
[City]
------------------------------