ShyamRajamanickam
asked on
TSM Server not responding
Hi
when i tried to login in tsm server it opts for Userid alone and its not asking fro Password ..and hanged
when i checked for process its displaying mesaages
root 5191 1 99 Jul03 ? 21-17:17:03 [dsmserv <defunct>]
root 19199 19198 0 Jul15 ? 00:00:00 /bin/sh -c /usr/local/TSM-scripts/dsm serv_chk.s h > /dev/null 2>&1
root 19204 19199 0 Jul15 ? 00:00:00 /bin/bash /usr/local/TSM-scripts/dsm serv_chk.s h
root 6534 6532 0 Jul15 ? 00:00:00 /bin/sh -c /usr/local/TSM-scripts/dsm serv_chk.s h > /dev/null 2>&1
what is dsmserv <defunct > ...?
and how to check the Root cause ..pls help
when i tried to login in tsm server it opts for Userid alone and its not asking fro Password ..and hanged
when i checked for process its displaying mesaages
root 5191 1 99 Jul03 ? 21-17:17:03 [dsmserv <defunct>]
root 19199 19198 0 Jul15 ? 00:00:00 /bin/sh -c /usr/local/TSM-scripts/dsm
root 19204 19199 0 Jul15 ? 00:00:00 /bin/bash /usr/local/TSM-scripts/dsm
root 6534 6532 0 Jul15 ? 00:00:00 /bin/sh -c /usr/local/TSM-scripts/dsm
what is dsmserv <defunct > ...?
and how to check the Root cause ..pls help
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
It might not be an issue about TSM at all. Will you please check that your DNS servers lited in your /etc/resolv.conf are valid and accessible.
Also check the
uptime
and
sar -q
It might be an indication ofa problem. Then you can use
topas
and check for the process which keeps your system busy.
It is also possible that some of your filesystems are full (though system critical ones would present some error about it). Please check your volumes using:
df -k
Cheers,
K.
It might not be an issue about TSM at all. Will you please check that your DNS servers lited in your /etc/resolv.conf are valid and accessible.
Also check the
uptime
and
sar -q
It might be an indication ofa problem. Then you can use
topas
and check for the process which keeps your system busy.
It is also possible that some of your filesystems are full (though system critical ones would present some error about it). Please check your volumes using:
df -k
Cheers,
K.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
this looks quite like a TSM database or recovery log problem.
Could it be that your recovery log space got exhausted?
There is a server logfile somewhere, maybe in /opt/tivoli/tsm/server/bin
If you don't find the logfile, start the server from the command line so you can see its messages -
cd /opt/tivoli/tsm/server/bin
./dsmserv
A) Should you really find a "recovery log full" condition, do the following -
- Find a place in your filesystem where you can create a new logfile, size should be 256 MB to 1024 MB, depending on your server's load. This location will be used in the next commands ('[/path/to/file/filename]')
- issue
cd /opt/tivoli/tsm/server/bin
./dsmfmt -m log [/path/to/file/filename] [size in MB]
- when the above has finished, issue
cd /opt/tivoli/tsm/server/bin
./dsmserv extend log [/path/to/file/filename] [size in MB]
- when the above has finished, start your server as usual, and try to find the cause of the "log full" condition.
B) If it's not related to the recovery log, please post the messages dsmserv issues while starting, try to log in again and post the messages displayed during that attempt (if any), too.
wmp