[Bug 1888685] Re: rsync fails after installing level 3.2.1
Launchpad Bug Tracker
1888685 at bugs.launchpad.net
Mon Aug 10 05:48:30 UTC 2020
This bug was fixed in the package rsync - 3.2.2-2ubuntu1
---------------
rsync (3.2.2-2ubuntu1) groovy; urgency=medium
* Merge with Debian unstable (LP: #1888685). Remaining changes:
- d/t/control, d/t/upstream-tests: Make autopkgtests cross-test-friendly
rsync (3.2.2-2) unstable; urgency=medium
* d/p/fix_bwlimit_0.patch: New upstream patch to fix bwlimit=0
(closes: #964587)
rsync (3.2.2-1) unstable; urgency=medium
* New upstream version 3.2.2
* d/rsync.install: Install rsync-no-vanished (closes: #353697)
-- Christian Ehrhardt <christian.ehrhardt at canonical.com> Mon, 03 Aug
2020 11:22:30 +0200
** Changed in: rsync (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1888685
Title:
rsync fails after installing level 3.2.1
Status in rsync package in Ubuntu:
Fix Released
Status in rsync package in Debian:
Fix Released
Bug description:
After installation of rsync.3.2.1 my attempt to sync fails with chroot
error. The rsyncd.log indicates that rsync can't find the directories
I want to sync.
2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873
2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known
2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159)
2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159)
2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2)
2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known
2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159)
2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159)
2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2)
2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known
2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159)
2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159)
2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2)
Dropping back to Ubuntu 20.04 and rsync works again. The rsync update
was install 7/18.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: rsync 3.2.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 23 10:28:17 2020
InstallationDate: Installed on 2020-07-06 (16 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions
More information about the foundations-bugs
mailing list