On 9/30/25 12:08 PM, Dennis Herbrich wrote:
On 2025-09-30 09:28, Óscar García Amor wrote:It is the last line of `build()`, `./build/telegraf config > telegraf.conf`. It is at this point that the execution stops completely if I build the package with `extra-x86_64-build`.Can you think of any reason why this might happen or how it could be fixed?I've reproduced the issue, and boiled it down to a likely interaction of systemd-nspawn and go's threading/process handling. systemd-nspawn is used by extra-x86_64-build implicitly to containerize the build. The call of `telegraf config` does output, but hangs on termination in an epoll_pwait/futex wait loop as described in [issue 55120](https://github.com/golang/go/issues/55120).
I only took a quick look at the problem and unjustly guessed that the telegraf binary was launching itself as "daemon" mode in my initial response [1] for some reason, but the above analyse feels way more accurate than my wild guess! 😄
Thanks for research and the detailed answer!The (somewhat sketchy) workaround I gave in my initial mail still stands though (while waiting for this systemd-nspawn + go process handling issue to be solved).
Good luck, anyone else! — Dennis
[1] https://lists.archlinux.org/archives/list/[email protected]/message/FCOSAFK6JL2BBWSOYKX5WFRKZKZH6DFN/
-- Regards, Robin Candau / Antiz
OpenPGP_0xFDC3040B92ACA748.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
