Good tip! FYI... Noticed that I was getting the following error... I had
been getting this error since installing the new server code a few months
ago (went from 3.7.3.6 to 4.1.4.5):
02/25/02 22:00:04 ANS9281E Space management kernel extension is downlevel
from the user program.
Since the problem with the scheduler quitting had only been occuring during
the past week, I didn't immediatly associate this error with the scheduler
quitting but sure enough, the times did coincide. I had been getting this
error on and off since installing new server code months ago. Why the
problem (scheduler stopping) didn't pop up for months is a mystery. In any
case, I we don't run HSM so I just went to the /dev directory and removed a
file/device called "fsn" which is associated with this HSM stuff and the
problem of the scheduler stopping went away. This is strange because I had
deleted references to HSM in my rc.* files, had no HSM file systems nor
were any HSM processes running. I did not have any HSM licenses actuated
either... strange but the problem is now fixed.... Thanks to all who
responded!
George Lesho
AFC Enterprises
David Longo <David.Longo AT HEALTH-FIRST DOT ORG>@VM.MARIST.EDU> on 02/26/2002
10:30:08 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: George Lesho/Partners/AFC)
Fax to:
Subject: Re: TSM scheduler dies
Look in your dsmsched.log and dsmerror.log on this client and see if there
are any messages indicating problem. I have one AIX client that
occaisionally has a memory problem and that shows up in logs.
David Longo
>>> GLesho AT AFCE DOT COM 02/26/02 11:10AM >>>
I have server AIX 433 running TSM 4.1.4.5 & 4.1.3 client. The TSM scheduler
runs out of /usr/tivoli/tsm/client/ba/bin. Over the past week, the TSM
scheduler just quits.
example of scheduler process while running:
afcops2: /usr/local/bin # ps -aef | grep sched
root 11502 31266 1 14:46:24 pts/0 0:00 grep sched
root 22444 1 0 14:33:33 - 0:00 dsmc sched
---------- I start the scheduler on system reboot via an entry in my
inittab:
inittab:
adsmschd:a2:once:/etc/rc.adsmc >/dev/null 2>&1 #Start ADSM Sched
---------- The inittab entry runs a script rc.adsmc:
#-------------------------------------------------------------------------------
#-------------------------------------------------------------------------------
# Title : ADSM automatic dsmc scheduler startup
# Date : 09/08/1999
#
# Written by B/Johnson
#
# Function : To enable the CLIENT SCHEDULER DAEMON to be
# restarted automatically on reboot
#
# Actions : put the following line into /etc/inittab
#
# 1) adsm::once:/etc/rc.adsmc > /dev/null 2>&1 #ADSM Scheduler
#-------------------------------------------------------------------------------
#
#set -x
BASEDIR=/usr/tivoli/tsm/client/ba/bin
if [ -x ${BASEDIR}/dsmc ]
then
echo "...Starting ADSM CLIENT SCHEDULER DAEMON..."
cd ${BASEDIR}
nohup dsmc sched 2>&1 > /dev/null &
echo "...ADSM CLIENT SCHEDULER DAEMON STARTED..."
echo "...Sending output to /dev/null..."
else
echo "...Cannot start ADSM Client Scheduler..."
echo "...${BASEDIR}/dsmc does not exist..."
fi
exit 0
___________________Yesterday, I wrote a script to check the scheduler on
the hour (script runs via crontab) and
restart the scheduler, if
necessary... here is script:
#!/bin/ksh
#check to make sure TSM scheduler running
cd /usr/local/bin
SCHED=$(ps -aef | grep -v grep | grep -v tsmsched.scr | grep sched)
echo "${SCHED}" | while read -r SCHEDULER_RUNNING
do
case "${SCHEDULER_RUNNING}" in
"")
echo "TSM Scheduler not running at `date`" >>
/tmp/tsmscheduler.log
echo "The TSM Scheduler was restarted at `date`" >>
/tmp/tsmscheduler.log
telinit a
echo "TSM Scheduler was restarted at `date`" | mail -s "TSM
Scheduler quit!" "lesho AT satx DOT net"
;;
*)
echo "TSM Scheduler running at `date`" >>
/tmp/tsmscheduler.log
;;
esac
done
______________here is a copy of the log generated by the above script:
TSM Scheduler running at Mon Feb 25 15:00:01 CST 2002
TSM Scheduler running at Mon Feb 25 16:00:00 CST 2002
TSM Scheduler running at Mon Feb 25 17:00:00 CST 2002
TSM Scheduler running at Mon Feb 25 18:00:01 CST 2002
TSM Scheduler not running at Mon Feb 25 19:00:00 CST 2002
The TSM Scheduler was restarted at Mon Feb 25 19:00:00 CST 2002
TSM Scheduler not running at Mon Feb 25 20:00:00 CST 2002
The TSM Scheduler was restarted at Mon Feb 25 20:00:00 CST 2002
TSM Scheduler not running at Mon Feb 25 21:00:00 CST 2002
The TSM Scheduler was restarted at Mon Feb 25 21:00:00 CST 2002
TSM Scheduler not running at Mon Feb 25 22:00:00 CST 2002
The TSM Scheduler was restarted at Mon Feb 25 22:00:00 CST 2002
TSM Scheduler not running at Mon Feb 25 23:00:00 CST 2002
The TSM Scheduler was restarted at Mon Feb 25 23:00:00 CST 2002
TSM Scheduler not running at Tue Feb 26 00:00:00 CST 2002
The TSM Scheduler was restarted at Tue Feb 26 00:00:00 CST 2002
TSM Scheduler not running at Tue Feb 26 01:00:00 CST 2002
The TSM Scheduler was restarted at Tue Feb 26 01:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 02:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 03:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 04:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 05:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 06:00:01 CST 2002
TSM Scheduler running at Tue Feb 26 07:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 08:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 09:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 10:00:00 CST 2002
TSM Scheduler running at Tue Feb 26 10:00:00 CST 2002
////////////////Any hints as to why the scheduler is now stopping for no
apparent reason... the rc.adsmc script had run without
a hitch since 1999... Thanks -
George Lesho
AFC Enterprises
"MMS <health-first.org>" made the following
annotations on 02/26/02 11:43:03
------------------------------------------------------------------------------
This message is for the named person's use only. It may contain
This message is for the named person's use only. It may contain
confidential, proprietary, or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify
the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. Health First reserves the right to monitor all e-mail
communications through its networks. Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of a particular
entity; and (2) the sender is authorized by the entity to give such views
or opinions.
=============================================================================
|
