cloudfoundry/bosh

An errand run fails because of "no such file or directory" error

Closed this issue · 3 comments

wjun commented

Describe the bug
I noticed that after an errand completed, bosh will collect all logs under /var/vcap/sys/log/* of the worker vm the errand ran. Since some logs under /var/vcap/sys/log are subject to rotation controlled by the applications, sometimes, during bosh collects logs, some logs will be deleted by the applications at the same time, and we got "no such file or directory" error in "Finding and packing log files" task.

To Reproduce
Steps to reproduce the behavior (example):

  1. bosh run-errand --download-logs
  2. Notice all logs under /var/vcap/sys/log directory are downloaded as .tgz file
  3. Sometimes, this errand run task will fail because of "no such file or directory" error in "Finding and packing log files" sub task.

Expected behavior
During "Finding and packing log files", bosh should ignore non-existing file as some files are rotated by the application on the worker vm already.

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/175052006

The labels on this github issue will be updated when the story is started.

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.