Project

General

Profile

tickets #108494

[carsten@c-otto.de: [ftpsync-opensuse-ftp@ftp] ERROR: rsync errors]

Added by otto@informatik.rwth-aachen.de 11 months ago. Updated 10 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Mirrors
Target version:
-
Start date:
2022-03-17
Due date:
% Done:

80%

Estimated time:

Description

Hi,

there seems to be some issue with the RPM file mentioned below. I keep
getting errors rsyncing against stage, and the file name makes me think
some rsync on your side of things tries to write the file again and
again.

Could you please check on stage.opensuse.org?

Thanks
Carsten

----- Forwarded message from carsten@c-otto.de -----

Date: Thu, 17 Mar 2022 09:31:34 +0100 (CET)
From: carsten@c-otto.de
To: datafetch@ftp.halifax.rwth-aachen.de
Subject: [ftpsync-opensuse-ftp@ftp] ERROR: rsync errors

rsync: send_files failed to open "/opensuse/update/leap/15.3/sle/src/.rust1.58-1.58.0-150300.7.3.1.src.rpm.ZMUDCR" (in opensuse-full-with-factory-dvd5): Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1819) [generator=3.2.3]

Mar 17 09:30:01 ftp ftpsync-opensuse-ftp[6745]: Mirrorsync start
Mar 17 09:30:01 ftp ftpsync-opensuse-ftp[6745]: Running mirrorsync, update is required, /pub/opensuse//Archive-Update-Required-ftp.halifax.rwth-aachen.de exists
Mar 17 09:30:01 ftp ftpsync-opensuse-ftp[6745]: Running stage2: rsync --quiet --log-file /home/datafetch/log/rsync-ftpsync-opensuse.log --filter=exclude_/Archive-Update-in-Progress-ftp.halifax.rwth-aachen.de --filter=protect_/Archive-Update-in-Progress-ftp.halifax.rwth-aachen.de --filter=exclude_/Archive-Update-Required-ftp.halifax.rwth-aachen.de --filter=protect_/Archive-Update-Required-ftp.halifax.rwth-aachen.de --filter=exclude_/project/trace/ftp.halifax.rwth-aachen.de --filter=protect_/project/trace/ftp.halifax.rwth-aachen.de --filter=exclude_/project/trace/ftp.halifax.rwth-aachen.de-stage1 --filter=protect_/project/trace/ftp.halifax.rwth-aachen.de-stage1 --filter=exclude_/project/trace/hierarchy --filter=protect/project/trace/hierarchy --filter=exclude/project/trace/traces --filter=protect/project/trace/traces --filter=include/project/ --filter=protect_/project/ --filter=include_/project/trace/ --filter=protect_/project/trace/ --filter=include_/project/trace/* --bwlimit=
0 -prltvHSB8192 --safe-links --chmod=D755,F644 --stats --no-human-readable --no-inc-recursive --exclude repositories/ --exclude=.~tmp~/ stage.opensuse.org::opensuse-full-with-factory-dvd5/opensuse/ /pub/opensuse/ --max-delete=40000 --delay-updates --delete --filter protect_debug/ --filter protect_source/
Mar 17 09:31:34 ftp ftpsync-opensuse-ftp[6745]: Back from rsync with returncode 23
Mar 17 09:31:34 ftp ftpsync-opensuse-ftp[6745]: Mirrorsync done with errors
Mar 17 09:31:34 ftp ftpsync-opensuse-ftp[6745]: bytes: 86165481 93

----- End forwarded message -----

--
Dr. Carsten Otto
http://verify.rwth-aachen.de/otto/

signature.asc (195 Bytes) signature.asc otto@informatik.rwth-aachen.de, 2022-03-17 08:51
signature.asc (195 Bytes) signature.asc otto@informatik.rwth-aachen.de, 2022-03-22 16:50
signature.asc (195 Bytes) signature.asc otto@informatik.rwth-aachen.de, 2022-03-22 17:44

History

#1 Updated by cboltz 11 months ago

  • Category set to Mirrors
  • Assignee set to pjessen

#2 Updated by pjessen 10 months ago

  • Status changed from New to Feedback
  • Private changed from Yes to No

otto@informatik.rwth-aachen.de wrote:

rsync: send_files failed to open "/opensuse/update/leap/15.3/sle/src/.rust1.58-1.58.0-150300.7.3.1.src.rpm.ZMUDCR" (in opensuse-full-with-factory-dvd5): Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1819) [generator=3.2.3]

Hi Carsten

That file is surely some temp file, maybe created during rsync - it is certainly gone now. The rpm rust1.58-1.58.0-150300.7.3.1.src.rpm is quite large, 2Gb. Are you still seeing this issue?

Thanks
Per

#3 Updated by pjessen 10 months ago

pjessen wrote:

That file is surely some temp file, maybe created during rsync

Confirm, that is the target file created by rsync, i.e. ".filename.NNNNNN".

#4 Updated by otto@informatik.rwth-aachen.de 10 months ago

Hi Per,

On Tue, Mar 22, 2022 at 02:56:59PM +0000, redmine@opensuse.org wrote:

That file is surely some temp file, maybe created during rsync - it is
certainly gone now. The rpm rust1.58-1.58.0-150300.7.3.1.src.rpm is
quite large, 2Gb. Are you still seeing this issue?

No, the error disappeared after a while. It took you several days to
respond, though. Is there some better way to talk about mirroring issues
with stage.opensuse.org?

Thanks,

Carsten

Dr. Carsten Otto
http://verify.rwth-aachen.de/otto/

#5 Updated by pjessen 10 months ago

  • Status changed from Feedback to In Progress
  • % Done changed from 0 to 80

otto@informatik.rwth-aachen.de wrote:

Hi Per,

On Tue, Mar 22, 2022 at 02:56:59PM +0000, redmine@opensuse.org wrote:

That file is surely some temp file, maybe created during rsync - it is
certainly gone now. The rpm rust1.58-1.58.0-150300.7.3.1.src.rpm is
quite large, 2Gb. Are you still seeing this issue?

No, the error disappeared after a while. It took you several days to
respond, though. Is there some better way to talk about mirroring issues
with stage.opensuse.org?

I would say reporting issues to admin-at-o-o is the best approach - depending on the severity of the issue, you will also usually have a quick answer. This time, well - I've been out with Covid since Thursday :-(

I'm wondering if it might be a good idea to exclude that file pattern from rsync modules in general ".filename.NNNNNN".

#6 Updated by otto@informatik.rwth-aachen.de 10 months ago

On Tue, Mar 22, 2022 at 05:39:21PM +0000, redmine@opensuse.org wrote:

I would say reporting issues to admin-at-o-o is the best approach -
depending on the severity of the issue, you will also usually have a
quick answer. This time, well - I've been out with Covid since
Thursday :-(

Ouch, get (and stay) well soon! This certainly wasn't a high priority
issue.

I'm wondering if it might be a good idea to exclude that file pattern from rsync modules in general ".filename.NNNNNN".

Yes, that would be great. My rsync script (based on what Debian uses for
their mirroring) automatically excludes .~tmp~, which, I think, is the
directory used when running "rsync --delay-updates". I don't know if
that's feasible for your setup, though.

Bye,

Carsten

Dr. Carsten Otto
http://verify.rwth-aachen.de/otto/

Also available in: Atom PDF