Hi all,

it seems to have no negative impact, but I was wondering if anyone has 
seen this message in their 10.1 installation logs when upgrading from 9.x 
to 10.1 (in my case, from 9.4 to 10.1):

Backing up catalog and models to db_20160726,1.SSdb
Could not open CAPKI shared library, errno is 0, errmsg is ld.so.1: 
SSdbsave: Schwerer Fehler: 
/opt/CA/SharedComponents/CAPKI/CAPKI5/SunOS/sparc/64/lib/libcapki.so: 
Öffnen fehlgeschlagen: Datei oder Verzeichnis nicht gefunden

(The German parts of the error messages simply state that the specified 
file cannot be found. In fact, the error message occurs not only once, but 
also when the installer calls dbtool right after the backup above, once 
again after a while, and finally at the end when another SSdb backup 
occurs.)

What has gotten me thinking is that lipcapki.so is not present at the time 
the installer calls SSdbsave and dbtool, but after the installation 
process is successfully (according to the installer window) finished. 
This, in fact, is pretty clear since the CAPKI package is installed by the 
very same installer _after_ it claims the necessity for the library above:

------------------- snip -------------------

root@*******:/opt/spectrum/Install-Tools/LOGS/10.1.0.0.237_20160726 > grep 
-i capki postinst.07.02
Could not open CAPKI shared library, errno is 0, errmsg is ld.so.1: 
SSdbsave: Schwerer Fehler: 
/opt/CA/SharedComponents/CAPKI/CAPKI5/SunOS/sparc/64/lib/libcapki.so: 
Öffnen fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
Could not open CAPKI shared library, errno is 0, errmsg is ld.so.1: 
dbtool: Schwerer Fehler: 
/opt/CA/SharedComponents/CAPKI/CAPKI5/SunOS/sparc/64/lib/libcapki.so: 
Öffnen fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
Could not open CAPKI shared library, errno is 0, errmsg is ld.so.1: 
dbtool: Schwerer Fehler: 
/opt/CA/SharedComponents/CAPKI/CAPKI5/SunOS/sparc/64/lib/libcapki.so: 
Öffnen fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
Could not open CAPKI shared library, errno is 0, errmsg is ld.so.1: 
SSdbsave: Schwerer Fehler: 
/opt/CA/SharedComponents/CAPKI/CAPKI5/SunOS/sparc/64/lib/libcapki.so: 
Öffnen fehlgeschlagen: Datei oder Verzeichnis nicht gefunden
Starting post-installation Install module 
Install-Tools/IPOST/capki_install.pl
[CAPKI] -----------Starting Discovery-----------
[CAPKI] Found global installation of CAPKI in 
/opt/CA/SharedComponents/CAPKI.
[CAPKI] Found & Opened .installdb
[CAPKI] CurrentVersion 5.0.1
[CAPKI] Existing installations will be displayed as
[CAPKI] caller Installed Version
[CAPKI] SPECTRUM 5.0.1
[CAPKI] -----------Discovery Complete-----------
Setting CAPKIHOME = /opt/CA/SharedComponents/CAPKI
Ending post-installation Install module 
Install-Tools/IPOST/capki_install.pl

------------------- snip -------------------

Also, the SSdb backup file db_20160726,1.SSdb is created and can be found 
in the file system, so obviously the CAPKI call seems to have not been 
necessary in the first place.

I am confused - I have not found anything on this neither in the docs nor 
on support.ca.com. Might I have a problem that maybe shows after a while 
and not instantly after the installation? Or should I forget about it?

Freundliche Grüße

Christian Fieres

Mainova AG
Sachgebiet Netz- und Infrastruktur (M3-ST4)
Teamleiter Service Operation Center
Solmsstraße 38
60623 Frankfurt am Main

Telefon 069 213 23617
Mobil 0170 5601563
Telefax 069 213 9623617
E-Mail [email protected]
Internet http://www.mainova.de


Mainova Aktiengesellschaft - Solmsstraße 38 - D-60623 Frankfurt am Main
Vorsitzender des Aufsichtsrates: Bürgermeister Uwe Becker
Vorstand: Dr. Constantin H. Alsheimer (Vorsitzender), Norbert Breidenbach, 
Lothar Herbst
Sitz der Aktiengesellschaft: Frankfurt am Main - Amtsgericht Frankfurt HRB 7173 
- USt-IdNr. DE 114184034


Mainova steht für besten Service, faire Verträge und top Preise für Ihre 
Energie - mit Auszeichnung!
Mehr Infos unter: http://www.mainova.de/auszeichnung

---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to