If X11 support is available I would suggest running dsm as well. My site 
recently had a problem with a Windows client. The dsm command found and 
reported a bad options file line during initialization. The dsmc command 
started with no complaints and then behaved strangely.

Thomas Denier
Thomas Jefferson University

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Francisco Javier
Sent: Thursday, April 16, 2015 12:51 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Linux 6.4 client hangs on starting dsmc

try executing dsmc since command line, perhaps be a problem with some 
configuration in option files.

Regards


2015-04-16 11:38 GMT-05:00 Arbogast, Warren K <warbogas AT iu DOT edu>:

> A Linux client has been missing its scheduled backups.  The TSM client
> is at version s 6.4.0.0, and our TSM server is running 7.1.1.108 on a
> Redhat 6 OS,
>
> The client admin reports that it hangs immediately when dsmc is
> started, but the admin can telnet successfully from the client to to
> the TSM server over ports 1500 and 1542, so we have crossed ‘firewall
> problem’ off the list of possible causes.
>
> 'ssl yes’ and ‘ssl fipsmode yes’ are specified in dsm.sys, but the
> admin tried commenting out ‘sslfipsmode yes’ and running dsmc —with
> the same result.
>
> dsmerror.log is empty, and there are no recent messages in dsmwebcl.log.
>
> The admin reports that selinux is running, but that ’nothing has changed’
> in its configuration recently.  Since backups had been runining
> successfully till a week ago, certainly something has changed, but we
> can’t find it.
>
> Where else should we look for the cause of the immediate hang when
> dsmc is started?
>
> With many thanks,
> Keith Arbogast
> Indiana University
The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person named 
above. If you are not the intended recipient, you are hereby notified that any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or 
urgent health care matters.