Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"File not found" after disk full #3530

Closed
jtyers opened this issue Mar 17, 2019 · 3 comments
Closed

"File not found" after disk full #3530

jtyers opened this issue Mar 17, 2019 · 3 comments

Comments

@jtyers
Copy link

jtyers commented Mar 17, 2019

Bug Report

I run concourse via the quick-start method under docker-compose, on a single machine. The machine ran out of disk space on its docker volume, and jobs started failing with no space left on device. I freed up space on the device and restarted concourse (via docker restart <concourse container id>).

Now, whenever I restart any job, I get:

initializing
file not found
errored

The job previously ran without this error, and the job has not been changed since it worked. I noticed that the job begins with a git step, which works without issue, and the next step is a run, which is where file not found occurs.

Steps to Reproduce

  • existing pipeline using git resource followed by run
  • fill space up on Docker host, until new jobs start failing with no space left on device
  • free up space and restart concourse
  • new jobs fail with file not found

Expected Results

Any corrupt state caused by the disk filling up should be corrected by concourse transparently so that workers/jobs can execute normally after recovering from this error.

Actual Results

New jobs fail with file not found.

Additional Context

  • Concourse 5.0.0

Version Info

  • Concourse version: 5.0.0
  • Deployment type Docker
  • Infrastructure/IaaS: Arch Linux rolling
  • Did this used to work? I hit a similar thing under 4.x; clearing the database and re-initialising concourse (adding users and pipelines from scratch) was the only way to clear out corrupt state and get things working again.
@marco-m
Copy link
Contributor

marco-m commented Mar 18, 2019

I freed up space on the device

This might be the problem. How exactly ?

@jtyers
Copy link
Author

jtyers commented Mar 18, 2019

Hmm, hopefully not. I ran docker volume prune while concourse was still running. Note that the "file not found" errors were occurring before I did this; the error message didn't change before/after I ran the prune.

@vito vito removed the triage label Apr 10, 2019
@stale
Copy link

stale bot commented Jul 16, 2019

Beep boop! This issue has been idle for long enough that it's time to check
in and see if it's still important.

If it is, what is blocking it? Would anyone be interested in submitting a
PR
or
continuing the discussion to help move things forward?

If no activity is observed within the next week, this issue will be
exterminated closed, in accordance with our stale issue
process
.

@stale stale bot added the wontfix label Jul 16, 2019
@stale stale bot closed this as completed Jul 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants