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

Zombie processes on some files (not sure of cause) #36

Open
brantfaircloth opened this issue May 22, 2015 · 3 comments
Open

Zombie processes on some files (not sure of cause) #36

brantfaircloth opened this issue May 22, 2015 · 3 comments

Comments

@brantfaircloth
Copy link

First time I've seen this - for some alignments, raxml 7.2.6 will enter a zombified state. I have no idea of the cause, and I can replicate this effect by using the SATé raxml binary locally with the input alignment and part.txt file from the tmp folder for a given alignment.

Strangely, running the binary version of raxml that comes with SATé, but passing the -p option (with a random seed) results in raxml processes that complete.

This does not happen for all or even most alignments - just an apparent special few.

Adding pull request momentarily w/ apparent fix.

@brantfaircloth
Copy link
Author

Even after making the change, I'm still getting some zombie processes (on both local machines w/ "real" drives and on the HPC - originally thought it might be NFS-related). Not sure if above is actually fixing anything or if problem is ephemeral (seems to be the latter). Simply killing and restarting some runs lets them complete... where they hung before.

@mtholder
Copy link
Member

hmm. And does sate just hang, or does it terminate and fail to clean up the raxml processes?
thanks for the pull request. I'll see if I can replicate this.

@brantfaircloth
Copy link
Author

it just hangs w/ raxml running at 100% but not (apparently) doing anything. re-running or using a different raxml can fix the problem w/ trees produced in 1-2 minutes for each iteration.

it's very, very weird. i'll shoot you a link via email with the problematic alignments (on re-run, these are sometimes not problematic...).

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

2 participants