RE: [Veritas-bu] Can't kill an "Active" job...

2005-12-08 Thread WEAVER, Simon
Title: Message



If
they do not get killed, I ended up stopping the services, or rebooting. When the
server comes back, normally find the jobs are either suspended or
killed.
 
If
suspended, just kill them and it should be fine!
Normal
times I have seen this is where there is a comms failure between NBU and the end
client and NBU continue to retries
 
 
Simon
WeaverTechnical SupportWindows Domain Administrator 
EADS
AstriumTel: 02392-708598 
Email:
[EMAIL PROTECTED] 

  
  -Original Message-From: Aaron Mills
  [mailto:[EMAIL PROTECTED] Sent: 07 December 2005
  20:58To: veritas-bu@mailman.eng.auburn.eduSubject:
  [Veritas-bu] Can't kill an "Active" job...
  I have several jobs that are stuck in "active" mode
  but not doing anything. 
  JobID   Type  State
  Status 
  Policy   
  Schedule
  Client  Dest Media Svr
  Active PID
   9716 Backup
  Active   
  inbound  
  ftpif   
  foo.com   foo.com
      5376  9018 Backup
  Active   
  inbound  
  ftpif    foo.com
    foo.com
      19580  9845 Backup
  Queued 
  DBArchive   Oracle-Policy   
  bar.com  9844 Backup
  Queued 
  DBArchive   Oracle-Policy  bar.com
  
  I tried to kill the job with: 
  bpdbjobs -cancel 9716 
  to no avail. The FAQ-O-Matic says I need to restart
  NBU and manually delete the db files? Is this accurate or is there an easier
  way to clean these buggers up?
  Thanks. 
  Aaron Mills System Administrator Return Path,
  Inc. 303.642.4111 [EMAIL PROTECTED] http://www.returnpath.biz


This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.

EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England


RE: [Veritas-bu] Can't kill an "Active" job...

2005-12-07 Thread Mark . Donaldson
Title: Can't kill an "Active" job...



Try 
killing it via the GUI - that sometimes works for me when the command line 
doesn't.  Strange.
 
I've 
never had to delete the db files now that we're at the later versions of 
NB.  Just kiilling & restarting the daemons was 
enough.
 
You 
might try suspending them and then killing the then suspended jobs - this worked 
for me once, too.  Also strange.
 
-M

  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of Aaron 
  MillsSent: Wednesday, December 07, 2005 1:58 PMTo: 
  veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Can't kill 
  an "Active" job...
  I have several jobs that are stuck in "active" mode 
  but not doing anything. 
  JobID   Type  State 
  Status  
  Policy    
  Schedule 
  Client  Dest Media Svr 
  Active PID
   9716 Backup 
  Active    
  inbound   
  ftpif    
  foo.com   foo.com 
      5376  9018 Backup 
  Active    
  inbound   
  ftpif    foo.com 
    foo.com 
      19580  9845 Backup 
  Queued  
  DBArchive   Oracle-Policy    
  bar.com  9844 Backup 
  Queued  
  DBArchive   Oracle-Policy  bar.com 
  
  I tried to kill the job with: 
  bpdbjobs -cancel 9716 
  to no avail. The FAQ-O-Matic says I need to restart 
  NBU and manually delete the db files? Is this accurate or is there an easier 
  way to clean these buggers up?
  Thanks. 
  Aaron Mills System Administrator Return Path, 
  Inc. 303.642.4111 [EMAIL PROTECTED] http://www.returnpath.biz 



RE: [Veritas-bu] Can't kill an "Active" job...

2005-12-07 Thread Geyer, Gregory
Title: Can't kill an "Active" job...



You are not alone.  And sometimes they persist after a 
reboot (which means I move the /usr/openv/netbackup/db/jobs/bpjobd.act.db to a 
backup name prior to restarting NBU).
 
I used to have success killing the child bpsched PID 
(listed as "Active PID") but the last couple of times I tried that, it caused 
the primary bpsched process to restartdropping all active backups.  So 
I don't do that anymore and just wait for a bounce and tell ops to ignore the 
phantom jobs.
 
I don't know but I suspect if bpsched gets a breather it 
might clean this up, but my bpsched never gets a breather so I don't 
know.
 
G.


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Aaron 
MillsSent: Wednesday, December 07, 2005 1:58 PMTo: 
veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Can't kill an 
"Active" job...

I have several jobs that are stuck in "active" mode 
but not doing anything. 
JobID   Type  State 
Status  
Policy    
Schedule 
Client  Dest Media Svr 
Active PID
 9716 Backup 
Active    
inbound   
ftpif    
foo.com   foo.com 
    5376  9018 Backup 
Active    
inbound   
ftpif    foo.com 
  foo.com 
    19580  9845 Backup 
Queued  
DBArchive   Oracle-Policy    
bar.com  9844 Backup 
Queued  
DBArchive   Oracle-Policy  bar.com 
I tried to kill the job with: 
bpdbjobs -cancel 9716 
to no avail. The FAQ-O-Matic says I need to restart 
NBU and manually delete the db files? Is this accurate or is there an easier way 
to clean these buggers up?
Thanks. 
Aaron Mills System 
Administrator Return Path, Inc. 
303.642.4111 [EMAIL PROTECTED] http://www.returnpath.biz