# Jenkins build fails on (at least) Amazon Linux **URL:** \ **Category:** Beats\ **Created:** [March 29, 2018, 4:55pm UTC](https://discuss.elastic.co/t/jenkins-build-fails-on-at-least-amazon-linux/126126 "2018-03-29T16:55:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pillarsdotnet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pillarsdotnet/32/29369_2.png) [@pillarsdotnet](https://discuss.elastic.co/u/pillarsdotnet)\ **Post date:** [March 29, 2018, 4:55pm UTC](https://discuss.elastic.co/t/jenkins-build-fails-on-at-least-amazon-linux/126126/1 "2018-03-29T16:55:35Z")
On (at least) Amazon Linux, the [virtualenv](https://virtualenv.pypa.io/en/stable/) tool configures python with the following `sys.path` directories: - `''` - `'${PYTHON_ENV}/local/lib64/python2.7/site-packages'` - `'${PYTHON_ENV}/local/lib/python2.7/site-packages'` - `'${PYTHON_ENV}/lib64/python2.7'` - `'${PYTHON_ENV}/lib/python2.7'` - `'${PYTHON_ENV}/lib64/python2.7/site-packages'` - `'${PYTHON_ENV}/lib/python2.7/site-packages'` - `'${PYTHON_ENV}/lib64/python2.7/lib-dynload'` - `'${PYTHON_ENV}/local/lib/python2.7/dist-packages'` - `'${PYTHON_ENV}/local/lib/python2.7/dist-packages'` - `'${PYTHON_ENV}/lib/python2.7/dist-packages'` - `'/usr/lib64/python2.7'` - `'/usr/lib/python2.7'` However, running `pip install PyYAML` in that same `virtualenv` will install the `yaml` module into the `${PYTHON_ENV}/lib64/python2.7/dist-packages` directory, which is not on the search path. For now, I am working around the problem by creating `dist-packages.pth` files as follows: ```auto find ${PYTHON_ENV} -type d -name dist-packages -exec sh -c "echo dist-packages > {}.pth" ';' ``` I have created a [pull-request](https://github.com/elastic/beats/pull/6698) and [issue](https://github.com/elastic/beats/pull/6699). I will also be filing a bug-report against `virtualenv` as soon as I create a self-contained script illustrating the problem. ---
**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\ **Post date:** [March 30, 2018, 1:50pm UTC](https://discuss.elastic.co/t/jenkins-build-fails-on-at-least-amazon-linux/126126/2 "2018-03-30T13:50:39Z")
I think we should keep the discussion only on github, thanks 🙂 ---
**Author:** ![pillarsdotnet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pillarsdotnet/32/29369_2.png) [@pillarsdotnet](https://discuss.elastic.co/u/pillarsdotnet)\ **Post date:** [March 30, 2018, 5:47pm UTC](https://discuss.elastic.co/t/jenkins-build-fails-on-at-least-amazon-linux/126126/3 "2018-03-30T17:47:12Z")
When I opened a pull-request, github suggested that I read the [contributor guidelines](https://github.com/elastic/beats/blob/master/CONTRIBUTING.md), which start with: > Please post all questions and issues first on [Beats - Discuss the Elastic Stack](https://discuss.elastic.co/c/beats) before opening a Github Issue. The [Contributing to Beats](https://www.elastic.co/guide/en/beats/devguide/current/beats-contributing.html) document likewise starts with: > If you have a bugfix or new feature that you would like to contribute, please start by opening a topic on the [forums](https://discuss.elastic.co/c/beats). So I was just posting here by direction. Sorry if my interpretation of the guidelines caused offense. ---
**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\ **Post date:** [March 30, 2018, 6:21pm UTC](https://discuss.elastic.co/t/jenkins-build-fails-on-at-least-amazon-linux/126126/4 "2018-03-30T18:21:34Z")
Don't worry, everything is fine! Thanks for pushing it. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 27, 2018, 8:21pm UTC](https://discuss.elastic.co/t/jenkins-build-fails-on-at-least-amazon-linux/126126/5 "2018-04-27T20:21:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.