[Bug 1208665] New: restic does not print information when doing backups
https://bugzilla.suse.com/show_bug.cgi?id=1208665 Bug ID: 1208665 Summary: restic does not print information when doing backups Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: azouhr@opensuse.org QA Contact: qa-bugs@suse.de CC: ada.lovelace@gmx.de Found By: Community User Blocker: --- When doing backups on s390x, restic only prompts for password, but does not print any more information, regardless of the verbosity. The backup seems to work though. This has been evaluated with restic-0.15.1-0.s390x.rpm. On x86_64, there is quite some additional information by default. The following commands can be used to reproduce:
restic init --repo /tmp/testrepo enter password for new repository: enter password again: created restic repository 49ad167248 at /tmp/testrepo
Please note that knowledge of your password is required to access the repository. Losing your password means that your data is irrecoverably lost.
restic -r /tmp/testrepo backup ~/ enter password for repository: echo $? 0
For those who do not have s390x available, you can reproduce on your local PC like this: zypper in qemu-s390x osc co openSUSE:Factory:zSystems restic cd openSUSE:Factory:zSystems/restic osc build --vm-type qemu --vm-memory=8192 standard s390x osc chroot --vm-type qemu --vm-memory=8192 --noinit standard s390x You will find the package at the usual places. It can be unpacked with rpm2cpio and cpio -id if you want to retrieve the binary. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1208665 https://bugzilla.suse.com/show_bug.cgi?id=1208665#c1 --- Comment #1 from Sarah Kriesch <ada.lovelace@gmx.de> --- The s390x support for restic exists since 2021: https://github.com/restic/restic/issues/2780 They do not have any open issue regarding that at the moment. I suggest, that I will open an issue upstream and forward it to IBM (within the Linux Distributions Working Group), if the upstream community does not know, how to handle it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1208665 Sarah Kriesch <ada.lovelace@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ihno@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1208665 https://bugzilla.suse.com/show_bug.cgi?id=1208665#c2 --- Comment #2 from Sarah Kriesch <ada.lovelace@gmx.de> --- My created upstream issue: https://github.com/restic/restic/issues/4223 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1208665 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |asarai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1208665 https://bugzilla.suse.com/show_bug.cgi?id=1208665#c3 --- Comment #3 from Sarah Kriesch <ada.lovelace@gmx.de> --- That behavior looks like what I'd expect if restic is run with the --quiet flag. Does setting TERM=dumb or RESTIC_PROGRESS_FPS=1 show some output? A stacktrace while the backup is running might also be useful. Please start a backup, then send a SIGQUIT to restic (e.g. via Ctrl+/). This will cause restic to print a stacktrace and exit immediately. This will leave a stale lock file behind which you can remove using restic unlock. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com