Improper management of SURL status can lead to PutDone errors and locked SURLs

ExportXMLWordPrintable

      StoRM BackEnd PutDone timed out

      We had been reported that SRM PutDone timed out when putting to a specific path. So, we checked StoRM BE log and found these errors:

      17:01:41.590 - ERROR [qtp2046936610-277797] - None of the surls is success, failed or aborted, Unexpeced! SurlStatus =
[TSURLReturnStatus [surl=***SURL***, returnStatus=SRM_FAILURE: There is another PutDone in execution on this SURL.]]
17:01:41.590 - INFO [qtp2046936610-277797] - srmPutDone: user<***DN***> Request for [token:
f15d1572-0742-4b54-88d8-fed1c007821e] for [SURL: [***SURL***]] failed with [status: SRM_INTERNAL_ERROR: Request Failed,
no surl status recognized, retry.]

      There are some paths occurring same error.
      How do we resolve it ?

      Our StoRM version is 1.11.9.
      The result of srmping is bellow:

      VersionInfo : v2.2
      backend_type:StoRM
      backend_version:<FE:1.8.9><BE:1.11.9>
      backend_os_distribution:Scientific Linux release 5.11 (Boron)

      Affected Site: JP-KEK-CRC-02

            Assignee:
            Enrico Vianello
            Reporter:
            Enrico Vianello
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: