Hi All

(Running TSM 3.7.3.8 on Solaris 2.7 box, the client in question is a
Solaris box with client level 3.7.2.0)

I have a funny problem. For the past two evenings, one of my Solaris
Clients has got half way through a backup and then, as far as I can see,
hung. Although the waiting time for the client is 0sec.

I stopped and started the client and then went to the Backup/Archive GUI to
check that certain files were being excluded. However, when I tried to
expand one of the dir trees, the GUI hung completely and I had to shut the
windows down manually. Even then, the Server thought that I still had a
session open and I had to issue the can session command to get rid of it.

For the past half hour or so, I can see the following process still running
even though the client is not running.

root 20665     1  0 08:25:38 ?        0:00 /usr/bin/dsmagent 10 0
-optfile=/usr/bin/dsm.opt
Why is it still there?
Why is it still there?

Also, I have checked in the dsmerror.log file for this client and can see
the following message for this morning.

03/14/02   09:04:20 Re-trying bind with any port after finding default port
number in-use.
03/14/02   09:04:20 Obtained new port number on which to listen.

Anyone ever seen anything like this before, and what may be going on? I'm
confused :)

I would really appreciate anyone's help on this as it seems a bit odd and
more than a little concerning.

Many thanks in advance

All the best

Farren Minns