ADSM-L

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

2013-11-05 23:39:53
Subject: Re: [ADSM-L] dsmc dumps core on Ubuntu 13.10 amd64
From: Tobias Karnat - adcon GmbH <Tobias.Karnat AT ADCON DOT DE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 6 Nov 2013 04:37:40 +0000
Hi,

have you tried to add the following in dsm.sys?

ENCRYPTIONType DES56

Mit freundlichem Gruß / With kind regards
 
Tobias Karnat
- Systemberater -
 
Tel:        +49(0)231 946164-29
Fax:        +49(0)231 946164-14
Mail:       karnat AT adcon DOT de
Web:        http://www.adcon.de
 
adcon Gesellschaft für EDV-Dienstleistung/Beratung mbH
An der Goymark 23, D-44263 Dortmund
 
GF: Dipl.-Inf. Norbert Keßlau Amtsgericht Dortmund - HRB 11759
 
-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
von Michael Prix
Gesendet: Dienstag, 5. November 2013 22:30
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: [ADSM-L] dsmc dumps core on Ubuntu 13.10 amd64

Hello,

observed this on OpenSUSE12.3 and Fedora19, both x86_64.
Traced it down to the version of libcrypt.so, which was in a working 
system version 2.15 (libcrypt-2.15.so) and on these systems 2.17 
(libcrypt-2.17.so).
Apparently, a change from glibc-2.15 to glibc-2.17 happened, but with 
LD_PRELOAD it was possible to put the working libcrypt.so at place.

So it might be tried by you to get from a former version on Ubuntu 
(12.04 LTS works fine), place it somewhere and preload it before 
starting dsmc

-- 
Mit freundlichen Grüßen / kind regards

Michael Prix

On 11/05/2013 09:19 PM, Stephan Rumpfhuber wrote:
> Hi,
>
> I have exactly the same problem. I have several systems running ubuntu
> 13.10 but not all were affected. It seems to be that this have something
> todo with the password file and the client crashes when it tries to read
> or write the file (this just a guess) . By changing the passwordaccess
> option to "prompt" instead of "generate" the problem doesn't occur anymore.
>
> Another work arround is to change the nodename. So on my system the
> nodenames "foo" and"bar" won't work but the nodename "foobar" works
> ...so pls dont ask me why I just can guess whats happening :-)
>
>
> Regards S.R.
>
>
>
>
> On 11/05/2013 06:31 PM, Christian Schmidt wrote:
>> 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.
>>