ADSM-L

Re: [ADSM-L] dsmc dumps core on Ubuntu 13.10 amd64

2013-11-06 06:14:33
Subject: Re: [ADSM-L] dsmc dumps core on Ubuntu 13.10 amd64
From: Malcolm Howe <malcolm.howe AT IT.OX.AC DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 6 Nov 2013 11:11:43 +0000
This sounds like a problem we've seen which is described in APAR IC92662

http://www-01.ibm.com/support/docview.wss?uid=swg1IC92662&myns=apar&mynp=DOCTYPEstatus&mync=E

We've had to rename about 20% of the nodes running Ubuntu 13.04 or higher and 
Fedora 18 or higher. A small change to the name usually works but it's trial 
and error - you can't tell what will be OK without trying it. 

Malcolm Howe
Oxford University IT Services

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Christian Schmidt
Sent: 05 November 2013 17:31
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] dsmc dumps core on Ubuntu 13.10 amd64

Hi all,

we're trying to get dsmc running on a latest Ubuntu amd64 system.
Converting the x86_64 rpm archives to deb packages and installing these worked 
fine. But whenever invoking dsmc we get the following messages:

 IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
  Client Version 6, Release 4, Level 1.0
  Client date/time: 05.11.2013 18:23:53
(c) Copyright by IBM Corporation and other(s) 1990, 2013. All Rights Reserved.

Node Name: [correct node name here]
Aborted (core dumped)

As you can see from the messages, we're running client release 6.4.1.0.

"ldd ` which dsmc`" reveals:

linux-vdso.so.1 =>  (0x00007fffa7ffe000)
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00002ad407068000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00002ad4072a1000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00002ad4074be000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00002ad4076c2000)
libgpfs.so => /opt/tivoli/tsm/client/api/bin64/libgpfs.so
(0x00002ad406e91000)
libdmapi.so => /opt/tivoli/tsm/client/api/bin64/libdmapi.so
(0x00002ad4079c6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00002ad407acd000) 
libgsk8ssl_64.so => /usr/lib/libgsk8ssl_64.so (0x00002ad407cd5000) 
libgsk8iccs_64.so => /usr/lib/libgsk8iccs_64.so (0x00002ad407f29000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00002ad40808a000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00002ad40838e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00002ad4085a4000)
/lib64/ld-linux-x86-64.so.2 (0x00002ad406e43000) libgsk8cms_64.so => 
/usr/lib/libgsk8cms_64.so (0x00002ad40896c000) libgsk8sys_64.so => 
/usr/lib/libgsk8sys_64.so (0x00002ad408d88000)

...so I think that all libraries are in place.

Trying a former client release resulted in the same problems.

Client 6.2.2.0 on a 32Bit Ubuntu Saucy (13.10) is working without any problems.

Can somebody give me some additional hints what to check? Has anybody succeeded 
in running dsmc von Ubuntu 13.10 amd64?

TIA!

Regards,
Christian
--
No signature available.