TSM client not starting at system boot on Suse Linux

[markb333]

I've a problem with a Suse client not starting the TSM client processes from the inittab file, I've tried various combinations but nothing seems to work. These are the current entries,



# Start TSM client

tsmcad:nce:/usr/bin/dsmcad > /dev/null 2>&1 # TSM Client Acceptor Daemon

tsmsched:nce:/usr/bin/dsmc sched > /dev/null 2>&1 # TSM scheduler



I've checked the syntax and paths and all appear fine, I can start the client manually just not at boot time.



This is driving me nuts so any help would be great.

 

[Harry_Redl]

Hi,



this works for me



tsm::respawn:/opt/tivoli/tsm/client/ba/bin/dsmc sched >/dev/null 2>&1



look for dsmsched.log and dsmerror.log as well as /var/log/messages ... any clue there?



Hope it helps



Harry

 

[markb333]

Thanks for the info Harry,



I've made the changes but still no joy, I'm seeing the following in /var/log/messages



Sep 27 15:34:45 image1 init: Re-reading inittab

Sep 27 15:34:45 image1 dsmc: ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs or a related

file: /dsmerror.log. errno = 13, Permission denied



I tried changing the permissions and running init q to re-read the inittab but the processes still don't start and there are no more entries in /var/log/messages



It works fine on my AIX boxes, I'm new to Linux but as the client pdf is the same doc for both I thought this would be straightforward.



Thanks,



Mark.

 

[cheffern]

Hi Mark -



I think your issue might be that you are trying to write the error log to / -

Is this how you do it on AIX, and it works?



Have you considered using a script to run the scheduler instead on Linux?

This would force the environment and you could redirect the error log to a more suitable location.



It would look like this:



vi /etc/rc.dsmc



#!/bin/ksh

#

#Used to start the TSM Client scheduler in the background

#



LC_ALL=en_US; export LC_ALL



DSM_DIR=/opt/tivoli/tsm/client/ba/bin; export DSM_DIR

DSM_CONFIG=$DSM_DIR/dsm.opt; export DSM_CONFIG

DSM_LOG=/opt/tivoli/tsm/client/ba/log; export DSM_LOG



start_sched()

{



/opt/tivoli/tsm/client/ba/bin/dsmc sched > /dev/null 2>&1 &



}



trap start_sched 0



exit



~



Then in your inittab it would be:



# TSM start entry

tsmsched:2:wait:/etc/rc.dsmc # TSM Client Scheduler

tsmcad:nce:/usr/bin/dsmcad > /dev/null 2>&1 # TSM Client Acceptor Daemon



or (if you prefer)



# TSM start entry

tsmsched:2:respawn:/etc/rc.dsmc # TSM Client Scheduler

tsmcad:nce:/usr/bin/dsmcad > /dev/null 2>&1 # TSM Client Acceptor Daemon



Once you set the password in the foreground, this method would work just the same as what you normally use.



For our Linux boxes - this works (RedHat & Suse)

Good Luck -

-Chef.