Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #7500

Closed
Open
Created 10 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Photo upload gives 500 with no error log message if cannot save file

Closed

Photo upload gives 500 with no error log message if cannot save file

Created by: JamesHutchison

This is running GitLab 6.9.2

Summary: Gitlab does not provide a helpful error if it cannot save an uploaded photo due to permissions.

Steps to reproduce: Set the permissions of the uploads directory (i.e. gitlab/public/uploads) such that the process cannot write to it.

Expected Behavior: Gitlab should serve up a 500 error. The access log should indicate the 500 error, and the error log should provide a helpful error message.

Observed Behavior: Gitlab returns 500, the access log indicates the 500 error. The error log provides no message.

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: Razer6

      With error log, which log do you mean exactly? Have you looked to production.log

      By Administrator on 2014-08-14T20:18:46 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: marcpires

      This error is because of permisssions for the gitlab public/uploads/tmp directory. Check who owns this directory, for me I just changed the ownership to the git user

      By Administrator on 2014-08-19T19:48:13 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: JamesHutchison

      Honestly I can't explain the exact log because I didn't set up the install. We have an access log which shows the requests and an error log which shows errors. I'm guessing one is just stdout and the other stderror. I know for certain that at least some errors from gitlab make it to the error log because we had an earlier misconfiguration and could see the error. It could be that the lack of an error message is an artifact of our set-up, but it should be easy to test this to validate if the issue exists or not.

      By Administrator on 2014-08-21T08:26:12 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: marcpires

      Do you tried to set ownership of public/uploads/tmp directory to git:git ? In my installation this solved the issue

      By Administrator on 2014-08-25T16:20:30 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help