I see no answer to this so will try to answer (if you didn't solved it but
workaround).
How dsmcad works:
Client Acceptor Daemon is intended to be thinner than dsmc with small
memory footprint. Upon startup it starts to listen on ports for services
it manages (similar to what inetd daemon does for ftp, telnet, etc.). When
request is accepted on particular port dsmcad starts the corresponding
service.
By default it accepts connections only for Web client (on port 1581). If
set in dsm.sys/dsm.opt it will also manage the scheduler and *might*
listen to port 1501. The latter is controlled by the schedmode used - if
server-prompted the client (i.e. dsmcad) will listen to port 1501, if
client-polling the client will poll the server for schedules on port 1500
(1501 will not be used).
--> no dsmc sched process running, but dsmcad was still running
When schedules are controlled by CAD dsmc is never fired with "sched"
parameter. When schedule is run you will see normal "dsmc <objects>
<options>" launched by dsmcad. When there is no active schedule only
dsmcad will be active.
--> netstat shows a process listening on port 1581, nothing on 1500
Nether "dsmc sched" nor "dsmcad" will listen on port 1500. Using defaults
only server listens to this port. Scheduler in prompted mode will listen
on port 1501 and in polling mode will not listen on any port. The latter
is the behavior you see on the working client.
--> there is an attempt by the server to connect on 1501 ...
A real problem! I think the server still assumes the client is in prompted
mode and attempts to contact it (on port 1501) to start a schedule.
However the client is unable to contact the server (for some reason - the
root of the problem !!) and inform it now polling mode will be used.
Verify the configuration of the client and options/environment used to
start dsmcad. Is the client able to run schedules when "dsmc sched" is
used? If not there might be expired password problem. If yes I would bet
dsmc and dsmcad are started using different configuration files or
environment variables.
Zlatko Krastev
IT Consultant
Steve Harris <Steve_Harris AT HEALTH.QLD.GOV DOT AU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
31.10.2002 05:10
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Weird Managedservices problem
Hi All,
Here's a screwy one that's got me stumped
Server TSM 4.2.1.8 AIX 4.3.3
Client TSM 4.2.1.25 Solaris 2.7
We've been running TSM on this box for some time. Recently we changed
over to run managedservices schedule and webclient.
Backups have been running fine. Suddenly, 2002-10-27 the daily
incremental was running, but hung after processing / filesystem. There are
no NFS mounts on this box.
Nothing in dsmsched.log or dsmerror.log or dsmwebcl.log.
When I got to this there was no dsmc sched process running, but dsmcad was
still running.
Stopping and restarting dsmcad makes no difference.
If I take "schedule" out of the managedservices paramater in dsm.sys, I
can run dsmc sched and all works perfectly.
Put it back and restart dsmcad and schedules won't start.
dsmwebcl.log shows
31-10-2002 09:49:48 (dsmcad) Client Acceptor - Built Feb 25 2002 14:38:58
31-10-2002 09:49:48 (dsmcad) Version 4, Release 2, Level 1.28
31-10-2002 09:49:48 (dsmcad) (C) Copyright IBM Corporation, 1990, 2001,
All Rights Reserved.
31-10-2002 09:49:48 (dsmcad) Dsmcad is working in Webclient Schedule
mode.
31-10-2002 09:49:48 (dsmcad) ANS3000I HTTP communications available on
port 1581.
31-10-2002 09:49:48 (dsmcad) Command will be executed
in 1 minute.
Web client works fine.
TCPPort is specified as 1500, HTTPport is left to default
netstat shows a process listening on port 1581, nothing on 1500, and this
is the same as another machine which does work correctly.
Snooping the interface on the client that works, we see when dsmcad
starts, a connection is made from client to server from a high numbered
port to 1500 on the server. A scheduled backup then seems to connect to
this port
Snooping on the client that fails, there is an attempt by the server to
connect on 1501, but this is rejected as the client isn't listening on
1501.
Does anyone have any debugging ideas?
Thanks
Steve
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.
Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail. You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************
|
