-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Heartbeat] Zombie-ish processes created under agent #32363
Comments
Pinging @elastic/uptime (Team:Uptime) |
For my own understanding, Is the issue here
Playwright server process does handle these signals Running Synthetics with |
…32393) Fixes #32363 by instructing the linux kernel to automatically kill node subprocesses if their parents die. In testing it appears chromium always dies as well, although I'm not entirely sure why. Either chrome sets the right flags itself, or the death signal propagates. Either way, in testing this works very solidly. We don't have sufficient automated test infrastructure to write a good automated test here, so this will have to reply on manual testing.
May have found a problem on Mac. See #32393 (comment). Just wanted to check if I missed anything on my tests, otherwise I'll open a separate issue for this. |
…32393) Fixes #32363 by instructing the linux kernel to automatically kill node subprocesses if their parents die. In testing it appears chromium always dies as well, although I'm not entirely sure why. Either chrome sets the right flags itself, or the death signal propagates. Either way, in testing this works very solidly. We don't have sufficient automated test infrastructure to write a good automated test here, so this will have to reply on manual testing.
When running under elastic agent heartbeat sometimes receives a signal causing it to restart, leaving orphaned node processes from browser runs (they wind up re-parented to
tini
in our container). We should use either golang'sprctl
capability or some other strategy to ensure they are properly reaped.The text was updated successfully, but these errors were encountered: