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.

Sign up for GitHub

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

Jump to bottom

events: avoid zombie processes after reloading #4437

Open
zhangxyue opened this issue Dec 5, 2024 · 0 comments · May be fixed by #4436
Open

events: avoid zombie processes after reloading #4437

zhangxyue opened this issue Dec 5, 2024 · 0 comments · May be fixed by #4436

Comments

@zhangxyue
Copy link
Contributor

Description of problem:
when reloading glusterevnetsd, the original child process has become a zombie process.

The exact command to reproduce the issue:

The full output of the command that failed:

Expected results:

Mandatory info:
- The output of the gluster volume info command:

- The output of the gluster volume status command:

- The output of the gluster volume heal command:

**- Provide logs present on following locations of client and server nodes -
/var/log/glusterfs/

**- Is there any crash ? Provide the backtrace and coredump

Additional info:

- The operating system / glusterfs version:

Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration
@zhangxyue zhangxyue linked a pull request Dec 5, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

events: avoid zombie processes after reloading zhangxyue/glusterfs
1 participant
@zhangxyue