CA SDM 17.1 Installation On Linux (SUSE)

[ROBINSON MORALES]

Hello team.
Has anyone installed CA SDM 14.x or 17.x on Linux SUSE?
We're having a trouble (Install.log file is attached)

 

- We're running installation with "srvcdesk" user which has rights to execute SUDO commands.

- Installation path is "/opt/ca" (a file system with 50 GB is mounted on it), but when installing the wizard tries to create/use directories "/opt/CA/SC" and "/opt/CA/SharedComponents".  Is mandatory install SDM on "/opt/CA"?

How could we change "/opt/CA/SC" for "/opt/ca/SC" ?

- Any recommendations to have into account before installing?

 

Regards,

Robin

Attachment(s)

Install.log.zip   13 KB 1 version

[Raghu Rudraraju]

2018/12/07 15.13.56.233 INFO [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [InstallSDMRemoteMDB] The MDB Common path will be set as: /opt/CA/SC/Mdb
2018/12/07 15.13.56.488 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] Setup MDB returns code 127
2018/12/07 15.13.56.491 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] MDB RC : 127
2018/12/07 15.13.56.491 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] MDB Error: Unexpected error. Check logs at /opt/CA/ServiceDeskManager/temp/mdb_oracle.
2018/12/07 15.13.56.491 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [SetupMDB] Check mdb logs at /opt/CA/ServiceDeskManager/temp/mdb_oracle.
2018/12/07 15.13.56.491 ERROR [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [InstallSDMRemoteMDB] SetupMDB returns code 127
2018/12/07 15.13.56.492 DEBUG [DeployThread: Installing CA Service Desk Manager Database Schema remotely] [ProgressPage] ProgressPage - Task Changed Installing CA Service Desk Manager Database Schema remotely
2018/12/07 15.13.56.492 INFO [Thread-791] [ProgressUpdateInstallSDMRemoteMDB] Waiting for mdbstatus.log to be available. retry 1 of 50

 

Can you check the install_mdb.log here in : /opt/CA/ServiceDeskManager/temp/mdb_oracle ?

 

There was a problem there and that's why the main install stopped.

 

thx

_R

[Michael Mueller]

I installed SDM on suse several times.
I suggest to install as root user on all Linux flavors.
Also pdm_configure should be run as root as well.
But pdm_init always as the privileged SDM user.
Regards
....Michael

[Michael Mueller]

How about creating a symbolic link from /opt/CA to /opt/ca ?

[ROBINSON MORALES]

Hi Michael.

When installing CA SDM with the roor account all the files under "/opt/CA/..." will be owned by "root" user or "srvcdesk" user?

This is because if we install with root user, when runing/starting CA SDM, its deamons will start owned by root user which linux admin staff wants to avoid as best practice.

 

Regards,

Robin

[Raghu Rudraraju]

Robin,

Did you get a chance to check the install_mdb.log here in : /opt/CA/ServiceDeskManager/temp/mdb_oracle ?

 

thx

_R

[ROBINSON MORALES]

Hello Ragu.

Unfortunatelly that log file does not exits any more, a VM's snapshot was restored.

On the other hand, we have check all DB requirements, and connection to oracle instance (where MDBADMIN schema will be deployed) is ok.

 

Then when launching the install wizard (we have tried several times) this error appeards:

 

============================

2018/12/14 17.55.23.622 INFO [DeployThread: Installing CA Service Desk Manager] [ActiveProcessHolder] Exit Monitor. Process ID (PID): 20373
2018/12/14 17.55.23.622 INFO [DeployThread: Installing CA Service Desk Manager] [ProcessUtilities] Process /opt/CA/medios/products/SDM/casd.lnx/Disk1/InstData/VM/install.bin completed with exit code 255
2018/12/14 17.55.23.623 INFO [DeployThread: Installing CA Service Desk Manager] [SDMUtils] Checking Installation status from /opt/CA/ServiceDeskManager/site/install.properties file.
2018/12/14 17.55.23.623 DEBUG [DeployThread: Installing CA Service Desk Manager] [CommonUtil] Loading the properties /opt/CA/ServiceDeskManager/site/install.properties
2018/12/14 17.55.23.624 ERROR [DeployThread: Installing CA Service Desk Manager] [CommonUtil] Unknown exception while loading the configuration file /opt/CA/ServiceDeskManager/site/install.properties
java.io.FileNotFoundException: /opt/CA/ServiceDeskManager/site/install.properties (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileInputStream.<init>(FileInputStream.java:93)
at com.ca.smsi.installcore.util.CommonUtil.loadProperties(CommonUtil.java:161)
at com.ca.smsi.installcore.util.SDMUtils.getInstallationStatus(SDMUtils.java:351)
at com.ca.smsi.installui.tasks.InstallSDM.run(InstallSDM.java:233)
at com.ca.smsi.wizard.task.Task.start(Task.java:239)
at com.ca.smsi.installcore.DeployThread.run(DeployThread.java:1117)
2018/12/14 17.55.23.626 INFO [DeployThread: Installing CA Service Desk Manager] [SDMUtils] >>>>> sdi.install.exitcode : ()
2018/12/14 17.55.23.626 INFO [DeployThread: Installing CA Service Desk Manager] [SDMUtils] >>>>> sdi.install.result : ()
2018/12/14 17.55.23.626 DEBUG [DeployThread: Installing CA Service Desk Manager] [InstallSDM] SDM Installation returned with exitCode: -1

 

============================

 

The file "install.properties" does not reside at "/opt/CA/ServiceDeskManager/site/" directory when the wizard tries to load/use it.  

Any ideas/options?

 

Regards,

Robin

 

[Raghu Rudraraju]

Robin,

 

My suggestion based on the above is to raise up a support case on this and have one of us work with you directly, maybe a webex.

 

install.properties would surface up only after installation.  Usually its in the /tmp folder until the install is complete.

 

_R

[Michael Mueller]

Hi Robin.

 

Yes, files in /opt/CA will belong to root.

But files in /opt/CAisd ... all the SDM related files will belong to the privileged user. The configuration Task changes the owner of all these files.

If you start SDM as the privileged user all processes are running in the context of this user, and not in the context of the root user. There are two exceptions: $NX_ROOT/bin/pdm_ver and $NX_ROOT/bin/bopauth_nxd. These two will still be owned by the root user and will run as root, because they have their sticky bit set.

pdm_ver is used to deploy SDM configuartion files from a source host to a target host, if configured. bopauth_nxd is used for user authentication.

However, as Raghu already suggsted, contacting support, might be the best choice.

 

Regards

...........Michael

[ROBINSON MORALES]

Hello Team.

Working with CA Support finally we could install CA Service Desk 17.1 on SUSE Linux as well as CUM1 and CUM2 (Advance Availability). I would like to share some points to have into account:

- Installation media files must be copied locally into each SDM Server. Do not mount them, copy the content to a folder.

- "srvcdesk" user must be created locally on each SDM server with Admin rigths (can execute sudo su -).

- "/" directory must have al least 5 GB available, 10 GB recomended.

- Installation directory must be "/opt/CA/ServiceDesk", and it is a good a idea to create this directory before running the installation, and be aware that must be "CA" and "ServiceDesk" (case sensitive).

- "/tmp" directory must have at least 5 GB available.

- For SUSE Linux there is a known error about "Localization Resources", CA Support gave us an "applyptf.linux" file to be replaced into the ApplyPTF directory inside media files (was replaced also into the CUM1 and CUM2 patch files).

- Finally, installation must be executed with the ROOT user.

 

Regards,

Robin MORALES P.

[Michael Mueller]

Great stuff, Robin!

Some good news: Just want to let you know , that the 17.2 installation/upgrade from 17.1 with the pre release phase 4 image on SuSE went through , without any specific handling of the included applyptf.linux. So, you dont have to copy the DVD content to your harddrive anymore.  So, this annoying procedure seems to be history in some weeks

Regards

.....Michael

[ROBINSON MORALES]

Thanks in advance Michael. That would be helpful.

 

Best regards,

Robin.