Rsync is managed by xinetd and by systemd at the same time

Bug #1805317 reported by Andrey Epifanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Roman Lubianyi

Bug Description

Version:
MOS9x

For some reason rsync is managed by 2 system at the same time:
- xinetd
- systemctl

when xinetd is able to bind 874 port, systemcl service failed to start and because of it fuel update failed.

Steps for reproduce:

1. systemctl stop rsyncd
2. service xinetd restart
3. systemctl start rsyncd

Changed in fuel:
milestone: none → 9.2-mu-10
assignee: nobody → MOS Maintenance (mos-maintenance)
importance: Undecided → High
status: New → Confirmed
Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Roman Lubianyi (rlubianyi)
status: Confirmed → In Progress
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to openstack/fuel-library (9.0/mitaka)

Fix proposed to branch: 9.0/mitaka
Change author: Roman Lubianyi <email address hidden>
Review: https://review.fuel-infra.org/39885

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to openstack/fuel-library (9.0/mitaka)

Reviewed: https://review.fuel-infra.org/39885
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka

Commit: fc15e4372ece37a002b0d6ea9636da056d975dbc
Author: Roman Lubianyi <email address hidden>
Date: Fri Nov 30 11:54:27 2018

Disable rsyncd systemd unit (alternatively managed by xinetd)

It was observed that both systemd and xinetd are trying to start rsyncd daemon.
In order to fix the issue, systemd rsyncd unit was disabled.

Change-Id: I520294c0f989440bacffe40a88958b692938f02a
Closes-Bug: #1805317

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to packages/centos7/rsync (9.0)

Reviewed: https://review.fuel-infra.org/39868
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0

Commit: bc973acadcc3793d4859e1b22bc85e9bd8ab80f4
Author: Roman Lubianyi <email address hidden>
Date: Thu Nov 29 08:56:37 2018

Disable rsyncd systemd unit (alternatively managed by xinetd)

It was observed that both systemd and xinetd are trying to start rsyncd daemon.
In order to fix the issue, systemd rsyncd unit was disabled.

Closes-Bug: #1805317

Change-Id: I2526e8dd9dd402c620445074a8aa9b6fb750189f

tags: added: customer-found sla1
Revision history for this message
Mikhail Samoylov (msamoylov) wrote :
Download full text (6.6 KiB)

Verified
[root@nailgun ~]# systemctl stop rsyncd
[root@nailgun ~]# service xinetd restart
Redirecting to /bin/systemctl restart xinetd.service
[root@nailgun ~]# systemctl start rsyncd
[root@nailgun ~]# echo $?
0
[root@nailgun ~]# systemctl status rsyncd
● rsyncd.service - fast remote file copy program daemon
   Loaded: loaded (/usr/lib/systemd/system/rsyncd.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/rsyncd.service.d
           └─restart.conf
   Active: activating (auto-restart) (Result: exit-code) since Thu 2019-01-24 14:46:14 UTC; 1s ago
  Process: 16762 ExecStart=/usr/bin/rsync --daemon --no-detach $OPTIONS (code=exited, status=10)
 Main PID: 16762 (code=exited, status=10)

Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: rsyncd.service changed dead -> running
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: Job rsyncd.service/start finished, result=done
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: Started fast remote file copy program daemon.
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: Child 16762 belongs to rsyncd.service
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: rsyncd.service: main process exited, code=exited, status=10/n/a
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: rsyncd.service changed running -> failed
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: Unit rsyncd.service entered failed state.
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: rsyncd.service failed.
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: rsyncd.service changed failed -> auto-restart
Jan 24 14:46:14 nailgun.test.domain.local systemd[1]: rsyncd.service: cgroup is empty
[root@nailgun ~]# systemctl status xinetd
● xinetd.service - Xinetd A Powerful Replacement For Inetd
   Loaded: loaded (/usr/lib/systemd/system/xinetd.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/xinetd.service.d
           └─restart.conf
   Active: active (running) since Thu 2019-01-24 14:45:58 UTC; 33s ago
  Process: 16670 ExecStart=/usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid $EXTRAOPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 16672 (xinetd)
   CGroup: /system.slice/xinetd.service
           └─16672 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid

Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: Trying to read xinetd.service's PID file /var/run/xinetd.pid in case it changed
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: inotify event for xinetd.service
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: Setting watch for xinetd.service's PID file /var/run/xinetd.pid
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: Trying to read xinetd.service's PID file /var/run/xinetd.pid in case it changed
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: inotify event for xinetd.service
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: Main PID loaded: 16672
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: Stopping watch for xinetd.service's PID file /var/run/xinetd.pid
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: xinetd.service changed start -> running
Jan 24 14:45:58 nailgun.test.domain.local systemd[1]: Job xinetd....

Read more...

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.