cancel
Showing results for 
Search instead for 
Did you mean: 

unable to collect pre eject information from the API robot(278)

-matt-
Level 4

Master/Media = AIX 5.3 NBU 7.1

Robot = TLH

Hi all,

I'm receiving the above error running the Vault process to eject tapes from the robot.

 

Activity Monitor shows the following;

 

01/05/2012 15:17:24 - vault waiting for global lock
01/05/2012 15:17:24 - vault global lock acquired
01/05/2012 15:17:24 - vault waiting for session ID lock
01/05/2012 15:17:24 - requesting resource uk01wrs6018.NBVAULT.MAXJOBS
01/05/2012 15:17:24 - granted resource uk01wrs6018.NBVAULT.MAXJOBS
01/05/2012 15:17:24 - requesting resource uk01wrs6018.VAULT_CREATE_SESSION_ID.LOCK_TLH(0)_uk1
01/05/2012 15:17:25 - vault session ID lock acquired
01/05/2012 15:17:25 - vault session ID lock released
01/05/2012 15:17:25 - granted resource uk01wrs6018.VAULT_CREATE_SESSION_ID.LOCK_TLH(0)_uk1
01/05/2012 15:18:35 - duplication skipped
01/05/2012 15:18:37 - vault waiting for assign slot lock
01/05/2012 15:18:37 - vault assign slot lock acquired
01/05/2012 15:18:37 - requesting resource uk01wrs6018.VAULT_ASSIGN_SLOT.LOCK_TLH(0)_uk1
01/05/2012 15:18:37 - granted resource uk01wrs6018.VAULT_ASSIGN_SLOT.LOCK_TLH(0)_uk1
01/05/2012 15:18:43 - vault assign slot lock released
01/05/2012 15:18:43 - begin Backup NB Catalog
01/05/2012 15:18:43 - starting catalog backup for policy: VltCat-Backup-0 schedule: VltCat-uk1-0-SCHED-0
01/05/2012 17:06:35 - catalog backup completed
01/05/2012 17:06:35 - end Backup NB Catalog; elapsed time: 01:47:52
01/05/2012 17:06:35 - vault waiting for assign slot lock
01/05/2012 17:06:35 - vault assign slot lock acquired
01/05/2012 17:06:35 - requesting resource uk01wrs6018.VAULT_ASSIGN_SLOT.LOCK_TLH(0)_uk1
01/05/2012 17:06:35 - granted resource uk01wrs6018.VAULT_ASSIGN_SLOT.LOCK_TLH(0)_uk1
01/05/2012 17:06:41 - vault assign slot lock released
01/05/2012 17:06:43 - before eject, waiting for media to be unmounted; sleeping for 360 seconds
01/05/2012 17:12:43 - starting eject operation
01/05/2012 17:12:43 - begin Eject/Report
01/05/2012 17:12:43 - connecting
01/05/2012 17:12:43 - connected; connect time: 00:00:00
01/05/2012 17:12:53 - suspend media for this session: failed to suspend 1 of 61 media at eject time
01/05/2012 17:12:54 - starting eject of 61 media
01/05/2012 17:50:24 - vault global lock released
unable to collect pre eject information from the API robot(278)

I've seen various posts advising to look out for Eject.txt files in /usr/openv/volmgr/misc and remove them, however, this file is not present in that directory.

There is a  file call tlhcd.lock with a timestamp of 30 April, which is the last time Vault ran successfully.

Does this need removing?

 

Many thanks,

Matt

1 ACCEPTED SOLUTION

Accepted Solutions

mph999
Level 6
Employee Accredited

Just copy it out of the way, and re-run the eject ...

Martin

View solution in original post

2 REPLIES 2

mph999
Level 6
Employee Accredited

Just copy it out of the way, and re-run the eject ...

Martin

-matt-
Level 4

Martin,


Thanks for your response.  I've renamed the .lock file and bounced the daemons.

Vault has completed successfully.


Cheers,

Matt