Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-17436

Unexpected 404 http response during PUT when no more inodes on data storage

    Details

    • Type: Bug
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: 6.2.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      docker.bintray.io/jfrog/artifactory-pro:6.2.0

      postgres:9.6.10

      nginx reverse proxy

      data storage on NFS

      Description

      We encountered 404 responses during uploads to Artifactory when we ran out of inodes on the data storage disk (still plenty of disk space).

      2018-08-30 05:58:04,729 [http-nio-8081-exec-5097] [WARN ] (o.a.w.s.RepoFilter :224) - Sending HTTP error code 404: /opt/jfrog/artifactory/data/filestore/_pre/dbRecord7299180929978574457.bin (No space left on device)

      A 404 error indicates that a resource could not be found, but during a PUT request a client wouldn't expect that type of response. 413 might be a better fit for this kind of problems.

      The hint in the log "(No space left on device)" is also not true since it was the inodes that ran out. I don't know if it's possible to detect the difference though.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              stefanga Stefan Gangefors
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: