Unsolved
This post is more than 5 years old
3 Posts
0
1804
August 14th, 2018 00:00
File Archive Activity jobs failed after reaching its timeout
During the job, the following errors appeared:
PollUnpackAreaDelMsg|ERROR|Failed to Access database lock: RL_FT_UNPACK_DIR - 86040419|ExAsIndexPoll.cpp(2648)|S1MFE
GetTransactions|WARNING|Skipping \\172.27.170.2\sourceone\index01\DropDir unable to claim dropdir lock. Error: 0x86042560|ExAsIdxComp.cpp(2561)|S1MFE
the following lines are from SOFileArchiveJBC log appeared at the end of the allowed timeout (which is 10 hours)
CSOFileArchiveJBC::ProcessDirectoryFiles|ERROR-LOGD|System call failed. (0x86040100) Catastrophic failure (0x8000FFFF)
CSOFileArchiveJBC::Run|ERROR|Job Failed with Error Code: 0x8000FFFF
It was also showing the following warning for Index locations:
CExAsIndexPoll::DoLowWater|WARNING-LOGD|Disk space low: current = 15%, target > 20%,
RKatwal
2 Intern
•
600 Posts
0
August 26th, 2018 19:00
Greetings,
Based on what you mentioned there are two different components that are logging info:
"Failed to Access database lock: RL_FT_UNPACK_DIR" and line on the bottom about "Disk space low: current = 15%, target > 20%," are related to SourceOne Index service and its components. One is showing that it was unable to grab the lock to process transaction which usually gets dealt with in next retry because another server may have held the lock and that will get released later on. Second event is about location where indexes are kept. It is warming message to inform admins to start planning now that free space is below 20% of the file share allocated.
SOFileArchiveJBC log info is related to title of issue you reported however this is not enough information to get to root cause. You need to turn on verbosity of the SOFileArchiveJBS.exe and SOFileArchiveJBC.exe components to find out what was happening when issue occurred. Error mentioned above is very generic error code.
I would suggest you to engage DELL EMC SourceOne support team to get them to enable verbose logging (unless already enabled) and then look at logs when the failure occurs next time.
Thanks,
Rajan Katwal