Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2072
  • Last Modified:

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/dsmserv_chk.sh  > /dev/null 2>&1
root     19204 19199  0 Jul15 ?        00:00:00 /bin/bash /usr/local/TSM-scripts/dsmserv_chk.sh
root      6534  6532  0 Jul15 ?        00:00:00 /bin/sh -c /usr/local/TSM-scripts/dsmserv_chk.sh  > /dev/null 2>&1
 what is dsmserv <defunct > ...?
and how to check the Root cause ..pls help
0
ShyamRajamanickam
Asked:
ShyamRajamanickam
2 Solutions
 
fosiul01Commented:
have a look this one  about what is defunct process

http://www.webmasterworld.com/forum40/1032.htm

its a zombie process, its actually finished but due to some child it still live

you need to kill that process

then start the process gain
0
 
woolmilkporcCommented:
Hi,
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  or wherever you directed it to. Try to find it, there should be messages in it pointing to the cause of the problem. LOGSEG871 or ANS1316E mean "recovery log full".
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    # or wherever your server installation lives
./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    # or wherever your server installation lives
./dsmfmt -m log [/path/to/file/filename] [size in MB]  
 - when the above has finished, issue

cd /opt/tivoli/tsm/server/bin    # or wherever your server installation lives
./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
0
 
Kerem ERSOYPresidentCommented:
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.




0
 
ShyamRajamanickamAuthor Commented:
I rebooted the server and started again the error is resolved .

Thanks all for the support
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now