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

Lodestar binary does not receive exit signal if used with systemd #7447

Closed
nflaig opened this issue Feb 11, 2025 · 3 comments · Fixed by #7453
Closed

Lodestar binary does not receive exit signal if used with systemd #7447

nflaig opened this issue Feb 11, 2025 · 3 comments · Fixed by #7453
Labels
meta-bug Issues that identify a bug and require a fix. meta-investigate Issues found that require further investigation and may not have a specific resolution/fix

Comments

@nflaig
Copy link
Member

nflaig commented Feb 11, 2025

There are two process which is likely the reason, I am not sure though how to fix this as it might be something that caxa is doing internally

devops   2156166  0.0  0.0 909672  9116 ?        Ssl  12:54   0:00 /usr/src/lodestar/packages/cli/bin/lodestar beacon --rcConfig /home/devops/beacon/rcconfig.yml
devops   2156172 60.6 53.0 185450204 8681388 ?   Sl   12:54  14:48 /tmp/caxa/applications/lodestar/evkh7n2qpo/0/node_modules/.bin/node --max-old-space-size=8192 /tmp/caxa/applications/lodestar/evkh7n2qpo/0/node_modules/.bin/lodestar beacon --rcConfig /home/devops/beacon/rcconfig.yml

Tried some stuff here unstable...nflaig/binary-exit-signal using exec but it seems to break the binary.

Something to note, the exit signal is properly forwarded to the Lodestar prcoess if executed in a terminal and shutting down the process via CTRL + C but does not seem to work with systemd.

Needs further investigation.

@nflaig nflaig added meta-bug Issues that identify a bug and require a fix. meta-investigate Issues found that require further investigation and may not have a specific resolution/fix labels Feb 11, 2025
@nflaig
Copy link
Member Author

nflaig commented Feb 11, 2025

based on #7378 (comment), using SIGINT does not solve the problem

@nflaig
Copy link
Member Author

nflaig commented Feb 11, 2025

the issue might be related to how caxa executes the binary, see leafac/caxa#77, we could create our own fork and apply the changes suggested in the PR

@nflaig
Copy link
Member Author

nflaig commented Feb 11, 2025

we already have forked the repo here https://github.com/ChainSafe/caxa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta-bug Issues that identify a bug and require a fix. meta-investigate Issues found that require further investigation and may not have a specific resolution/fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant