[Veritas-bu] Jobs not starting...
2002-10-01 10:46:20
Subject: |
[Veritas-bu] Jobs not starting... |
From: |
kmarx AT trigon DOT com (Marx, Keath) |
Date: |
Tue, 1 Oct 2002 10:46:20 -0400 |
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C26959.4E67329A
Content-Type: text/plain;
charset="iso-8859-1"
Actually my notify scripts call another app I wrote so they don't do much.
Turns out someone put a temp key in that has expired.
-----Original Message-----
From: Niehaus, Michael T. [mailto:MTNiehaus AT MarathonOil DOT com]
Sent: Tuesday, October 01, 2002 10:15 AM
To: Marx, Keath; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Jobs not starting...
Do you have anything in your notify scripts? We see this sometimes when the
notify/email scripts generate error dialogs - the jobs just hang until
someone acknowledges the dialogs, which will never happen. Execute the
following command on the server to see the process tree:
tlist -t
This should show you the relationship between the "bpsched" processes (one
of those at the bottom of the tree should have a process ID that corresponds
to the process ID of the hung job - with any luck you will see a child
process as well). The lowest process ID "bpsched" is probably the task
doing the actual scheduling. Restarting the "NetBackup Request Manager"
service should get it back running again. Still, killing "bpsched" tasks
should be a last resort, as it is probably just treating the symptom and not
the problem.
-Michael
-----Original Message-----
From: Marx, Keath [mailto:kmarx AT trigon DOT com]
Sent: Tuesday, October 01, 2002 8:46 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Jobs not starting...
We have NBU 4.5 with 45._1 installed on win2k backing up 2k clients. All of
the daily tasks are schedule not frequency based.
The last change I made before the jobs started failing was to create a task
to perform cummulative inc backups of a local directory. I ran that task
and since then nothing had run. I rebooted and my normal cummulative tasks
that run during the day kicked off. One ran to 100% then hung. I kicked
off some daily tasks and again 1 ran to 100% then hung.
Task manager shows multiple copies of bpsched running. If I kill the
bpsched with the lowest process ID all the rest go away but nothing changes.
If I kill the bpsched with the highest process ID it goes away but the
others stay and nothing happens. If I kill ALL the bpsched nothing new
happens.
Not out of disk space on any drive. An automated Duplicate ran this morning
without error. As mentioned nothing was changed on the server.
TIA
Keath Marx
------_=_NextPart_001_01C26959.4E67329A
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=987313814-01102002>Actually my notify scripts call another app I wrote so
they don't do much. Turns out someone put a temp key in that has
expired.</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV align=left class=OutlookMessageHeader dir=ltr lang=en-us><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Niehaus,
Michael
T. [mailto:MTNiehaus AT MarathonOil DOT com] <BR><B>Sent:</B> Tuesday,
October 01,
2002 10:15 AM<BR><B>To:</B> Marx, Keath;
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu]
Jobs not
starting...<BR><BR></FONT></DIV>
<DIV><SPAN class=330131114-01102002><FONT color=#0000ff face=Arial size=2>Do
you have anything in your notify scripts? We see this sometimes when
the
notify/email scripts generate error dialogs - the jobs just hang until
someone
acknowledges the dialogs, which will never happen. Execute the
following
command on the server to see the process tree:</FONT></SPAN></DIV>
<DIV><SPAN class=330131114-01102002><FONT color=#0000ff face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=330131114-01102002><FONT color=#0000ff face=Arial
size=2>tlist -t</FONT></SPAN></DIV>
<DIV><SPAN class=330131114-01102002><FONT color=#0000ff face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=330131114-01102002><FONT color=#0000ff face=Arial
size=2>This
should show you the relationship between the "bpsched" processes (one of
those
at the bottom of the tree should have a process ID that corresponds to the
process ID of the hung job - with any luck you will see a child process as
well). The lowest process ID "bpsched" is probably the task doing the
actual scheduling. Restarting the "NetBackup Request Manager" service
should get it back running again. Still, killing "bpsched" tasks should
be a last resort, as it is probably just treating the symptom and not the
problem.</FONT></SPAN></DIV>
<DIV><SPAN class=330131114-01102002><FONT color=#0000ff face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=330131114-01102002><FONT color=#0000ff face=Arial
size=2>-Michael</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Marx, Keath
[mailto:kmarx AT trigon DOT com]<BR><B>Sent:</B> Tuesday, October 01, 2002
8:46
AM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT
edu<BR><B>Subject:</B>
[Veritas-bu] Jobs not starting...<BR><BR></FONT></DIV>
<P><FONT face=Arial size=2>We have NBU 4.5 with 45._1 installed on win2k
backing up 2k clients. All of the daily tasks are schedule not
frequency based. </FONT></P>
<P><FONT face=Arial size=2>The last change I made before the jobs started
failing was to create a task to perform cummulative inc backups of a local
directory. I ran that task and since then nothing had run. I
rebooted and my normal cummulative tasks that run during the day kicked
off. One ran to 100% then hung. I kicked off some daily tasks
and again 1 ran to 100% then hung. </FONT></P>
<P><FONT face=Arial size=2>Task manager shows multiple copies of bpsched
running. If I kill the bpsched with the lowest process ID all the
rest
go away but nothing changes. If I kill the bpsched with the highest
process ID it goes away but the others stay and nothing happens. If I
kill ALL the bpsched nothing new happens.</FONT></P>
<P><FONT face=Arial size=2>Not out of disk space on any drive. An
automated Duplicate ran this morning without error. As mentioned
nothing was changed on the server.</FONT></P>
<P><FONT face=Arial size=2>TIA</FONT> <BR><FONT face=Arial size=2>Keath
Marx</FONT> </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C26959.4E67329A--
|
|
|