You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.6 / 2020-06-17
This also happens to Relax-and-Recover 2.4 / Git for RHEL 7.9
If your ReaR version is not the current version, explain why you can't upgrade:
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
NAME="Red Hat Enterprise Linux"
VERSION="8.6 (Ootpa)"
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
For details, please check it from https://github.com/iringor/rear.git
Description of the issue (ideally so that others can reproduce it):
I am getting this email notification everyday even if the mkbackup script is only running once a month.
From: (Cron Daemon) <root@server.company.com>
Sent: Thursday, April 4, 2024 1:30 AM
To: root@server.company.com
Subject: Cron <root@server> test -f /var/lib/rear/layout/disklayout.conf && /usr/sbin/rear checklayout || /usr/sbin/rear mkrescue
Proceed regardless that 'mkrescue' could be destructive with a 'iso' BACKUP_URL ?
(default 'No' timeout 300 seconds)
ERROR: The mkrescue workflow does not work for the BACKUP_URL scheme 'iso'
Some latest log messages since the last called script 040_check_backup_and_output_scheme.sh:
2024-04-04 01:30:24.256120130 Including prep/default/040_check_backup_and_output_scheme.sh
2024-04-04 01:30:24.314857703 UserInput: called in /usr/share/rear/prep/default/040_check_backup_and_output_scheme.sh line 30
2024-04-04 01:30:24.350941007 UserInput: No choices specified
2024-04-04 01:30:24.368811100 Proceed regardless that 'mkrescue' could be destructive with a 'iso' BACKUP_URL ?
2024-04-04 01:30:24.386439123 (default 'No' timeout 300 seconds)
2024-04-04 01:30:24.422376325 UserInput: 'read' timed out with non-zero exit code
2024-04-04 01:30:24.477753667 Aborting 'mkrescue' with a 'iso' BACKUP_URL by default Aborting due to an error, check /var/log/rear/rear-dvsdsas1.log for details
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
You can drag-drop log files into this editor to create an attachment
or paste verbatim text like command output or file content
by including it between a leading and a closing line of
three backticks like this:
verbatim content
The text was updated successfully, but these errors were encountered:
I think the issue is resolved. I was not aware that when installing rear, it automatically creates a cron for rear mkrescue that runs everyday at 1:30 AM and it looks like this is a default setting. I will comment out this cron for now and if there is no more recurring issue related to this in a week I will close this case. Thanks.
Hi Johannes,
Yes, it looks similar. But my issue is now fixed. I could not access https://relax-and-recover.org/ before when I started researching about ReaR. The site was blocked by our IT admin for some reason. I didn't find this in the man pages, but it is mentioned in https://relax-and-recover.org/usage/ that a cron job can be created (or automatically created?) to sync with the rescue image. It is actually a good tool, this "rear checklayout," to alert me if there is a need to create a new image. Thank you.
-Don Ringor
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.6 / 2020-06-17
This also happens to Relax-and-Recover 2.4 / Git for RHEL 7.9
If your ReaR version is not the current version, explain why you can't upgrade:
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
For details, please check it from https://github.com/iringor/rear.git
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
VMware
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
BIOS GRUB
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
local disk
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
I am getting this email notification everyday even if the mkbackup script is only running once a month.
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
You can drag-drop log files into this editor to create an attachment
or paste verbatim text like command output or file content
by including it between a leading and a closing line of
three backticks like this:
The text was updated successfully, but these errors were encountered: