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

Please add patch for nginx-http-upload-module #61

Closed
aloismayr opened this issue Oct 5, 2017 · 4 comments
Closed

Please add patch for nginx-http-upload-module #61

aloismayr opened this issue Oct 5, 2017 · 4 comments

Comments

@aloismayr
Copy link

Issue

The patch for the http-upload-module of nginx seems not to be included in the shipped nginx binary. Please review nginx-upload-module commit aba1e3f

Context

Wrong initialization of upload path cause segmentation faults. We can observe this behavior when Dynatrace agent instruments the nginx.

Steps to Reproduce

Add Dynatrace agent to cloud_controller VM, restart nginx, cf push an app.

Expected result

App pushed to CF successfully

Current result

Nginx causes segmentation faults.

Possible Fix

vkholodkov/nginx-upload-module@aba1e3f

Latest commit from 2.2 branch

@cf-gitbot
Copy link

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

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

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

@anniesing
Copy link

Hi @aloismayr,

Thanks for reaching out. What version of CAPI are you using? We see the nginx fix on our current branch, but need to know which version needs patching in your case.

Thanks,

@aloismayr
Copy link
Author

Hi @anniesing, @elenasharma

At least the Pivotal ERT version 1.11.7 - 1.12.2 are affected. According to Pivotal's release notes the capi release versions are: 1.28.0 and 1.40.0.

Please note that the official source download package of the release 2.2.0 (tag) does not contain the fix, but the branch 2.2.

Thanks! - Alois

@aloismayr
Copy link
Author

Thanks @anniesing & @elenasharma !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants