Quantcast
Channel: Symantec Connect
Viewing all articles
Browse latest Browse all 26913

VAULT failure error code 10

$
0
0
ソリューションが必要です

Hi Folks

vault is failing since past 3 days. it fails with error code 10. failure logs:

14:06:45.922 [25341] <16> vltrun@ImageInterface::next_image^1622: db_IMAGEreceive FAIL: 10 (allocation failed)
14:06:45.923 [25341] <16> vltrun@SelectImagesForDuplication^1622: Leaving with DMN=1 SC=10
14:06:45.923 [25341] <16> vltrun@VltSession::lock_and_operate^1622 OP_STEP=select FAILED
14:06:45.958 [25341] <16> vltrun@VltSession::lock_and_operate^1622 FAILed NB_EC=10 NB_MSG=allocation failed
14:06:45.959 [25341] <2> vltrun@VaultJobMonitor::_send_jobrundata^1622: SENT JobRunDataEx_t to JOBD at 1376762805
14:06:45.959 [25341] <2> vltrun@VaultJobMonitor::IncrementJobProgress^1622: SENT completion pct=3 to JOBD
14:06:45.959 [25341] <16> vltrun@VltSession::lock_and_operate^1622: Leaving with DMN=1 SC=10
14:06:45.966 [25341] <8> vltrun@VltSession::sessionStep()^1622: Session STEP COMPLETE
End Time                :2013.08.17 02:06:45 PM (1376762805)
Elapsed                 :12:5
14:06:45.966 [25341] <16> vltrun@VltSession::runSession^1622 Aborting session...
14:06:45.970 [25341] <16> vltrun@VltSession::runSession^1622 FAILed NB_EC=10 NB_MSG=allocation failed
14:06:45.984 [25341] <8> vltrun@VltSession::runSession^1622 Destructor called during stack unwinding
14:06:45.984 [25341] <16> vltrun@VltSession::runSession^1622: Leaving with DMN=1 SC=10
14:06:45.985 [25341] <2> vltrun@main^1622: End Time:            2013.08.14 09:06:45 PM (1376762805)     Elapsed: 15:56 (776)
 
14:06:45.985 [25341] <2> vltrun@main^1622: >>********************************************************************<<
14:06:45.993 [25341] <2> vltrun@main: cleanup vltrun
14:06:45.993 [25341] <2> vltrun@VaultLockProxy::release_all_locks^1622: UpdJobd=1
14:06:45.993 [25341] <2> vltrun@VaultLockProxy::raw_release_lock^1622: Type=NBVAULT.MAXJOBS Key= Limit=100
14:06:45.994 [25341] <4> vltrun@VaultLockProxy::raw_release_lock^1622: lock released. Key=MASTERSERVER.NBVAULT.MAXJOBS
14:06:45.994 [25341] <2> vltrun@VaultJobMonitor::_send_try_msg^1622: At 1376762805 sent TRY_MSG: VAULT_GLOBAL_LOCK_RELEASED 1376762805
 
14:06:45.994 [25341] <2> vltrun@cancel_keepalive_process^1622: Entering to cancel PID=25349, JOB_ID=3736561 with FD=13
14:06:45.994 [25341] <2> vltrun@cancel_keepalive_process^1622: Msg to Child: Exit now
 
14:06:45.994 [25341] <4> vltrun@cancel_keepalive_process^1622: write end of pipe closed
14:06:45.994 [25341] <2> vltrun@cancel_keepalive_process^1622: Harvesting child's exit status
14:06:46.018 [25341] <8> vltrun@cancel_keepalive_process^1622: Child exited with EC=0 SIG=0
14:06:46.018 [25341] <4> vltrun@main: Reporting Status=10 (allocation failed)
14:06:46.018 [25341] <16> vltrun@main Vault Session FAILED [PRFL=BC_eject_lib0 SID=1622 JID=3736561 EC=10]
14:06:46.044 [25341] <16> vltrun@main FAILed NB_EC=10 NB_MSG=allocation failed
14:06:46.044 [25341] <2> vltrun@main: EXIT STATUS 10
 
disk space is not a an issue. it more than 80G free.
 
please share your thoughts.

Viewing all articles
Browse latest Browse all 26913

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>