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

rsync failure left with "[rsync] <defunct>" zombie processes #46

Closed
fachen2015 opened this issue Sep 22, 2024 · 4 comments
Closed

rsync failure left with "[rsync] <defunct>" zombie processes #46

fachen2015 opened this issue Sep 22, 2024 · 4 comments

Comments

@fachen2015
Copy link

Hi I use rsync4j-core 3.2.3-7 (processoutput4j 0.0.7) in my project, but encountered this issue. whenever rsync failed (error 11), it would leave a zombie process not properly cleaned up. I double checked the output/err stream processor and could not find any issues there.

Any thoughts on this?
Thanks

image

@fracpete
Copy link
Owner

I haven't encountered an error code 11 before (Error in file I/O - full list of exit codes).

According to this blog post, an error code 11 can often be caused by a full disk:
https://bobcares.com/blog/rsync-error-code-11/

@fachen2015
Copy link
Author

it's indeed full-disk. this is for a remote fs where striping is used, so a back-off retry would succeed later. However the initial failure would leave a zombie process not properly cleaned up. oneline resources all mention that zombie was caused by not draining out/err stream from the child process, but I do provide the processor for both streams, so wonder if any potential issues in the lib itself.

@fracpete
Copy link
Owner

You could try upgrading processoutput4j, as I made a small change today to account for flushing stdout/stderr of a failed process. You may have to upgrade your rsync4j version to the latest one, though.

@fracpete
Copy link
Owner

due to no further feedback, assuming to be fixed (f2613d5)

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