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

post provision kill process that may have started in chroot #174

Open
coryb opened this issue Feb 4, 2014 · 2 comments
Open

post provision kill process that may have started in chroot #174

coryb opened this issue Feb 4, 2014 · 2 comments

Comments

@coryb
Copy link
Contributor

coryb commented Feb 4, 2014

Sometimes packages start up process as they are installed. This will cause the umount to fail so we cannot take an ebs snapshot. We need to discover processes with open files or cwd inside the chroot.

Python psutil looks promising for this:
https://pypi.python.org/pypi/psutil
http://code.google.com/p/psutil/wiki/Documentation#Processes

We can iterate over all open processes, then call getcwd() and maybe get_open_files() to see if the paths overlap with our chroot.

-Cory

@tjbaker
Copy link
Contributor

tjbaker commented May 9, 2014

This issue is likely what I was trying to work around with commit 9ea0f6c
If this were to be solved the retry attempts could be clawed back as upping the retires doesn't solve the issue.

@stevenjack
Copy link

@coryb you ever have any luck with this? Ran into an issue with it today where it couldn't umount because php-fpm was running in the chroot.

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