From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [RFC pmg-api] pmgtunnel: do not set SIGCHLD handler
Date: Tue, 19 Aug 2025 12:13:02 +0200 [thread overview]
Message-ID: <540c6849-15b2-4ead-a598-51159dbcb108@proxmox.com> (raw)
In-Reply-To: <20250818180714.22846-1-s.ivanov@proxmox.com>
Gave this a quick spin on a PMG cluster. Tried to reproduce the initial
issue via editing /etc/hosts and didn't run into any errors with this
patch. Downgraded to the initial version to cross-check and the error
started to appear.
Terminated the SSH process of pmgtunnel several times and checked if the
postgres tunnel in /run/pmgtunnel gets cleaned up.
Consider this:
Tested-by: Stefan Hanreich <s.hanreich@proxmox.com>
On 8/18/25 8:07 PM, Stoiko Ivanov wrote:
> Drop the SIGCHLD handling in pmgtunnel, as it's not necessary and
> parts deeper in our code-base (e.g. PVE::Tools::run_command) rely on
> signals not being handled by the callers.
>
> In the case of pmgtunnel the signalhander (finish_children) simply
> wait(2)'s for all children (no matter if it's a ssh-tunnel process, or
> e.g. `ip link` being called to get network information), and clears
> the ssh-forwarded postgres socket, schedules a (delayed) restart, and
> logs an exit message for the ssh-tunnels.
>
> all those tasks can happen a synchronously in the main loop in run as
> well (especially the cleaning of the postgres socket is done directly
> before running ssh anyways).
>
> from a quick look through our perl codebase it seems that this is the
> only service setting a similar SIGCHLD handler (thus the change in
> reading/parsing /etc/network/interfaces did not cause issues anywhere
> else).
>
> Suggested-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> Sending as RFC, as such changes to code that has not been touched in 7+
> years might cause regressions, which my testing would not catch.
> Let this run in my cluster after blocking access between the nodes via
> netfilter rules - the exiting and logging was the same.
>
> src/PMG/Service/pmgtunnel.pm | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/src/PMG/Service/pmgtunnel.pm b/src/PMG/Service/pmgtunnel.pm
> index 7b9fa28..062e764 100644
> --- a/src/PMG/Service/pmgtunnel.pm
> +++ b/src/PMG/Service/pmgtunnel.pm
> @@ -173,17 +173,12 @@ sub hup {
> sub run {
> my ($self) = @_;
>
> - local $SIG{CHLD} = \&finish_children;
> -
> for (;;) { # forever
>
> $next_update = time() + $updatetime;
>
> eval {
> - # reset SIGCHLD handler as ClusterConfig::new uses run_command (for reading ip link)
> - $SIG{CHLD} = 'DEFAULT';
> my $cinfo = PMG::ClusterConfig->new(); # reload
> - $SIG{CHLD} = \&finish_children;
> $self->purge_tunnels($cinfo);
> $self->start_tunnels($cinfo);
> };
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
prev parent reply other threads:[~2025-08-19 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 18:07 Stoiko Ivanov
2025-08-19 10:13 ` Stefan Hanreich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=540c6849-15b2-4ead-a598-51159dbcb108@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox