Project

General

Profile

Bug #35859

foreman-proxy logrotate sends signal to all processes under foreman-proxy.service

Added by Adam Ruzicka about 2 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
RPMs
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Starting with smart_proxy_remote_execution_ssh-0.5.0, REX spawns ssh
processes inside foreman-proxy.service. On logrotate, the SIGUSR1 signal
is sent to all processes of the service, including the ssh ones, which
react to the signal by terminating.

On debian-based distributions we already target only the main process of the service, let's do the same on rpm-based distributions.

Associated revisions

Revision 077be388 (diff)
Added by Adam Ruzicka about 1 month ago

Fixes #35859 - Send signal only to main process of foreman-proxy on logrotate

Starting with smart_proxy_remote_execution_ssh-0.5.0, REX spawns ssh
processes inside foreman-proxy.service. On logrotate, the SIGUSR1 signal
was sent to all processes of the service, including the ssh ones, which
would react to the signal by terminating.

History

#1 Updated by Evgeni Golov about 1 month ago

  • Category set to RPMs
  • Project changed from Smart Proxy to Packaging

#2 Updated by The Foreman Bot about 1 month ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-packaging/pull/8835 added

#3 Updated by Adam Ruzicka about 1 month ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Evgeni Golov about 1 month ago

  • Fixed in Releases 3.6.0 added

#5 Updated by Ewoud Kohl van Wijngaarden about 1 month ago

  • Target version set to 3.5.0

#6 Updated by Ewoud Kohl van Wijngaarden about 1 month ago

  • Triaged changed from No to Yes
  • Fixed in Releases 3.5.0 added
  • Fixed in Releases deleted (3.6.0)

Also available in: Atom PDF