Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error starting Software Update Manager (SUM) Can't retrieve C library version

Hi,

I am trying to update my SAP Solution Manager 7.1 SP04 to SP11 on a Debain squeeze. I did create a stack.xml and downloaded SUM SP10 (SUM10SP10_4-20006543.SAR)
unpacked location is /usr/sap/S01/SUM
I tried to run ./STARTUP with user s01adm but I got the following error:

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/S01/SUM/sdt/log/SDTServer.log]/-->

<!--PATTERN[SDTServer.log]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

May 6, 2014 3:23:52 PM [Info]: *************************************************

May 6, 2014 3:23:52 PM [Info]: Starting SL Controller listening on port 4241 ...

May 6, 2014 3:23:52 PM [Info]: Starting StorageService ...

May 6, 2014 3:23:52 PM [Info]: Initializing SecurityManager ...

May 6, 2014 3:23:54 PM [Info]: Server certificate fingerprint is 3E 76 23 18 C1 74 AC B9 5D E4 CC 88 BF FE 3A 08

May 6, 2014 3:23:54 PM [Info]: Configuring HTTPManager ...

May 6, 2014 3:23:54 PM [Info]: Starting WebstartService ...

May 6, 2014 3:23:54 PM [Info]: Starting RoleService ...

May 6, 2014 3:23:54 PM [Info]: Starting AlertService ...

May 6, 2014 3:23:54 PM [Info]: Starting NotesService ...

May 6, 2014 3:23:54 PM [Info]: Starting ProcessService ...

May 6, 2014 3:23:54 PM [Info]: Starting MIDService ...

May 6, 2014 3:23:54 PM [Info]: Starting FileService ...

May 6, 2014 3:23:54 PM [Info]: LogService switched off.

May 6, 2014 3:23:54 PM [Info]: Starting MailService ...

May 6, 2014 3:23:54 PM [Info]: Starting services ...

May 6, 2014 3:23:54 PM [Info]: Starting service "UseCaseService" ...

May 6, 2014 3:23:55 PM [Info]: Starting MIDService ...

May 6, 2014 3:23:59 PM [Error]: Can't retrieve C library version.

May 6, 2014 3:23:59 PM [Error]: Error while initializing service context.

May 6, 2014 3:23:59 PM [Error]: Can't initilize sdt service provider

May 6, 2014 3:23:59 PM [Error]: Creation of use case executor failed.

May 6, 2014 3:23:59 PM [Fatal]: Error during controller startup.

May 6, 2014 3:23:59 PM [Fatal]: SL Controller exiting.

This is what /usr/sap/S01/SUM/sdt/trc/DETECT.TRC reports:

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/S01/SUM/sdt/trc/DETECT.TRC]/-->

<!--PATTERN[DETECT.TRC]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

May 6, 2014 3:23:56 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path

May 6, 2014 3:23:57 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path

May 6, 2014 3:23:57 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path

May 6, 2014 3:23:58 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path

May 6, 2014 3:23:59 PM [Error]:            com.sap.sdt.tools.sysinfo.unx.UnixDetermineOSInfo.setupUNIX(UnixDetermineOSInfo.java:131) [Thread[main,5,main]]: Can't retrieve C library version.

May 6, 2014 3:23:59 PM [Error]:                                                         com.sap.sdt.server.core.admin.SDTServerAdmin [Thread[main,5,main]]: com.sap.sdt.tools.sysinfo.DetermineOSException: Can't retrieve C library version.

  at com.sap.sdt.tools.sysinfo.unx.UnixDetermineOSInfo.setupUNIX(UnixDetermineOSInfo.java:131)

  at com.sap.sdt.tools.sysinfo.unx.UnixDetermineOSInfo.<init>(UnixDetermineOSInfo.java:64)

  at com.sap.sdt.tools.sysinfo.unx.UnixOSInfoFactory.getOSInfo(UnixOSInfoFactory.java:29)

  at com.sap.sdt.j2ee.services.OSInfoServiceRetriever.retrieveOSInfo(OSInfoServiceRetriever.java:47)

  at com.sap.sdt.j2ee.services.SDTServiceProvider.detectOSInformation(SDTServiceProvider.java:587)

  at com.sap.sdt.j2ee.services.SDTServiceProvider.initServiceContext(SDTServiceProvider.java:414)

  at com.sap.sdt.j2ee.services.SDTServiceProvider.initialize(SDTServiceProvider.java:180)

  at com.sap.sdt.executor.service.ServiceAndBeanProviderFactory.getServiceAndBeanProvider(ServiceAndBeanProviderFactory.java:120)

  at com.sap.sdt.executor.usecase.UseCaseExecutionInitializer.getServiceBeanProviderWrapper(UseCaseExecutionInitializer.java:268)

  at com.sap.sdt.executor.usecase.UseCaseExecutionInitializer.initialize(UseCaseExecutionInitializer.java:155)

  at com.sap.sdt.executor.factory.UseCaseExecutorFactory.createUseCaseExecutor(UseCaseExecutorFactory.java:56)

  at com.sap.sdt.dsu.service.UseCaseService.createUseCaseExecutor(UseCaseService.java:1014)

  at com.sap.sdt.dsu.service.UseCaseService.initDetectUseCaseExecutor(UseCaseService.java:1027)

  at com.sap.sdt.dsu.service.UseCaseService.init(UseCaseService.java:166)

  at com.sap.sdt.server.core.services.Service.start(Service.java:94)

  at com.sap.sdt.server.core.admin.SDTServerAdmin.startServices(SDTServerAdmin.java:1155)

  at com.sap.sdt.server.core.admin.SDTServerAdmin.start(SDTServerAdmin.java:367)

  at com.sap.sdt.server.core.admin.SDTServerAdmin.runServer(SDTServerAdmin.java:847)

  at com.sap.sdt.server.core.admin.SDTServerAdmin.start(SDTServerAdmin.java:217)

  at com.sap.sdt.server.core.admin.SDTServerAdmin.main(SDTServerAdmin.java:126)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at com.sap.sdt.bootstrap.BootStrap.start(BootStrap.java:169)

  at com.sap.sdt.bootstrap.Startup.start(Startup.java:140)

  at com.sap.sdt.bootstrap.Startup.main(Startup.java:356)

May 6, 2014 3:23:59 PM [Error]:                 com.sap.sdt.j2ee.services.SDTServiceProvider.initialize(SDTServiceProvider.java:184) [Thread[main,5,main]]: Error while initializing service context.

May 6, 2014 3:23:59 PM [Error]: com.sap.sdt.executor.service.ServiceAndBeanProviderFactory.getServiceAndBeanProvider(ServiceAndBeanProviderFactory.java:125) [Thread[main,5,main]]: Can't initilize sdt service provider

May 6, 2014 3:23:59 PM [Error]:           com.sap.sdt.dsu.service.UseCaseService.initDetectUseCaseExecutor(UseCaseService.java:1031) [Thread[main,5,main]]: Creation of use case executor failed.

May 6, 2014 3:23:59 PM [Fatal]:                 com.sap.sdt.server.core.admin.SDTServerAdmin.startServices(SDTServerAdmin.java:1165) [Thread[main,5,main]]: Error during controller startup.

May 6, 2014 3:23:59 PM [Fatal]:                 com.sap.sdt.server.core.admin.SDTServerAdmin.startServices(SDTServerAdmin.java:1166) [Thread[main,5,main]]: SL Controller exiting.


Any idea what could be wrong?


Thanks,

Sven

Tags:
Former Member
Former Member replied

SUM checks the libc version by parsing the output of 'ldd --version'.

The java code looks like this:

String[] parsedOutput = getCommandOutput("ldd", new ValueIF[] { new StringValue("--version") }).split("libc\\) ");

   if (parsedOutput.length > 1) {

   this.cLibraryVersion = parsedOutput[1];

  } else {

   throw new DetermineOSException("msg.tools.sysInfo.0078");

  }

With newer releases of libc, the output of ldd --version no longer contains a string matching the pattern "libc\\) ", so this fails.

A rather quick-and-dirty workaround:

- rename the ldd executable to ldd.exe

- create the following shell script named ldd in /usr/bin:

#!/bin/sh

if [ $1 == "--version" ] ; then

  echo "libc) 2.17"

else

  /usr/bin/ldd.exe $@

fi

As SUM ignores the PATH variable it is not possible to place the modified ldd into some other directory.

br,

Sebastian

3 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question