Looking at the taped logs it appears that the problem is when the tape daemon is trying to unload a tape. We can see in the logs where it fails to unload the tape within the number the nbAttempts is set to. For whatever reason the logic in CTA appears to be to stop the tape daemon. At CERN that is probably not an issue as you only have one drive/server. At RAL and other sites we have multiple drives/server, so just stopping the daemon when the other drive is working fine is not what we want. So -
- Is there a way to change the variable nbAttempts=10 to a greater value, or is this hard coded?
- Is there a way to configure the cta-taped so that it keeps running after configuring the drive unmounted drive down? Oddly we see the tape daemon fail to load a tape after 10 attempts, but the daemon carries on running!
snippet of log -
2023-02-01T16:40:47.658328+00:00 cta-ts01 cta-taped: LVL=“ERROR” PID=“6565” TID=“8021” MSG=“Exception in TapeReadSingleThread-TapeCleaning when unmounting/unloading the tape. Putting the drive down.” thread=“TapeRead” tapeDrive=“asterix_ts1160_09” tapeVid=“CT2835” mountId=“520863” exceptionMessage=“Failed to dismount tape: vid=CT2835 slot=smc9: Failed to dismount tape in SCSI tape-library: vid=CT2835 librarySlot=smc9: Received error from rmcd after several fast retries: nbAttempts=10 rmcErrorStream=smc_dismount: SR017 - find_cartridge CT2835 failed : Not Ready to Ready Transition”
2023-02-01T16:40:47.660287+00:00 cta-ts01 cta-taped: LVL=“INFO” PID=“6563” TID=“6563” MSG=“In DriveHandler::processEvent(): changing session state” tapeDrive=“asterix_ts1160_09” PreviousState=“Unmounting” PreviousType=“Retrieve” NewState=“Fatal” NewType=“Retrieve”
2023-02-01T16:40:47.660587+00:00 cta-ts01 cta-taped: LVL=“CRIT” PID=“6563” TID=“6563” MSG="In DriveHandler::processFatal(): shutting down after fatal failure." tapeDrive=“asterix_ts1160_09” PreviousState=“Unmounting” PreviousType=“Retrieve” NewState=“Fatal” NewType=“Retrieve”