Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-23092

Error fetching from DFS: error message is incorrect

    Details

    • Sprint:
      Castor Core S2

      Description

      Under certain circumstances it is possible that fetching cache files from DFS will fail.
      While this is an expected situation (caused by network/NFS issues, for example), the generated error message is some cases is incoherent:

      eZDFSFileHandlerMySQLiBackend::_fetch:

      Size (73672) of written data for file 'var/.../cache/user-info/2/9/7/0/231/user-data-2970231.cache23757-978305412tmp.php' does not match expected size 73672
      

      The problem is that the local file size is checked against the dfs file size, and the error message displays the local file size and metadata size.

      Steps to reproduce:

      This has occurred in live environment and appears to be impractical to reproduce on a test env.
      It is possible/likely that either the dfs file size or metadata changes while the _fetch() method is being executed.

      Other info:

      Ref: https://github.com/ezsystems/ezpublish-legacy/blob/master/kernel/private/classes/clusterfilehandlers/dfsbackends/mysqli.php#L718

      Suggested course of action would be to either fix the error message, or
      reload the dfs filesize / metadata size if both mismatch.

        Issue Links

          Activity

          Show
          Joao Inacio (Inactive) added a comment - Possible fix: https://github.com/ezsystems/ezpublish-legacy/pull/1014
          Hide
          Yannick Roger (Inactive) added a comment -

          This could be fixed by EZP-21825

          Show
          Yannick Roger (Inactive) added a comment - This could be fixed by EZP-21825
          Hide
          Joao Inacio (Inactive) added a comment -

          @Yannick: AFAICT these are completely different/separate issues, despite the resolution affecting pretty much the same function/code.

          Show
          Joao Inacio (Inactive) added a comment - @Yannick: AFAICT these are completely different/separate issues, despite the resolution affecting pretty much the same function/code.
          Hide
          Yannick Roger (Inactive) added a comment -

          This issue is fixed applying both EZP-21825 and EZP-23254.

          Show
          Yannick Roger (Inactive) added a comment - This issue is fixed applying both EZP-21825 and EZP-23254 .

            People

            • Assignee:
              Unassigned
              Reporter:
              Joao Inacio (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile