RE: rsync errors when using latest ftpsync
> -----Original Message-----
> From: Bastian Blank [mailto:firstname.lastname@example.org]
> Sent: Saturday, 14 October 2017 4:23 PM
> To: email@example.com
> Subject: Re: rsync errors when using latest ftpsync
> On Sat, Oct 14, 2017 at 02:48:22PM +1100, Steve (IWWD) wrote:
> > After testing further, it seems the issue was indeed related to the 'owner' permissions. Once I had recursively set both the 'owner' and 'group' to the ftpsync executing user, the update ran correctly and links were created fine.
> > The problem it seems is that rsync, whenever it creates a new file, it's setting the owner as 'root', but is setting the group as the executing user.
> > Could there be an issue with the rsync command or something I'm missing?
> It has to be your environmnent. ftpsync does not call rsync with the "preserve owner" option, as a user in a Unix-like environment is not allowed to change the owner anyway. And I doubt any of the existing large mirrors would list files as owned by root.
> So if a user creates a file or symlink and it's suddenly owner by a different one, something is really broken.
That's very strange indeed. Ftpsync is called from a cron job under the user 'debmirror' which is being properly set as the group.
The system it's running on is: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 GNU/Linux
Granted it's an aging version now, but I wouldn't have expected that to become an issue.
> > This is the log from the last execution:
> > Oct 14 12:00:01 debian ftpsync: Mirrorsync start Oct 14
> > 12:00:01 debian ftpsync: Running mirrorsync, update is
> > required, /mirrors/debian//Archive-Update-Required-debian.localdomain
> > exists
> You system thinks it is called debian.localdomain. So this system is not even completely setup yet. It neither have a complete name in /etc/hosts, nor does get it from DNS.
Sorry, ignore this, I replaced the actual domain with this before sending just as a reference only, the systems DNS is correctly configured.
> > What kind of filesystem do you use?
The file system on the mirror instance is ext4 but the actual files are being saved on an NFS drive linked to a FreeNAS server, that is using ZFS; it has been this way since the mirror was setup years ago.
> You did not write this. Please fix your mail client to do proper quoting.
My personal preference is not to use quoted messages, but I've prefixed this reply as requested.
> But Captain -- the engines can't take this much longer!