search for: rearing

Every now and then I get an alert like this one. I have no clue what this "rear" subsystem is, or why madam would be trying to write to its log file. Can anyone enlighten me? thanks in advance! ------------------------- SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless. ***** Plugin restorecon (93.9 confidence) suggests

I don't understand what this means, I found it in root's email this morning: To log into the recovery system via ssh set up /root/.ssh/authorized_keys or specify SSH_ROOT_PASSWORD WARNING: /usr/lib/grub/x86_64-efi/moddep.lst not found, grub2-mkimage will likely fail. Please install the grub2-efi-x64-modules package to fix this. ERROR: Error occurred during grub2-mkimage of BOOTX64.efi

Hi all! I don't religiously follow everything that pops up in the selinux alerts, but now and then I go back and look at some of them. (I'm on an up to date Centos-7). Today I noted an error that seems to occur during a weekly raid check, from /etc/cron.d. the selinux alert is: SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless.

I'd agree with you John. I'm trying to get away from Amanda's unpredictability and go back to using scripts to drive dump (for ext2/3/4) and xfsdump (for xfs). Is there any easy way to tell rear to include xfsdump and dump capability? If the commands are there then its trivial to restore data. What I've done in the past is before the nightly backup write a small file to the

CentOS Errata and Bugfix Advisory 2019:2475 Upstream details at : https://access.redhat.com/errata/RHBA-2019:2475 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b91b489b63c529df80ddd6358f27c09a9921a016bc160a0601cc3628eaa95342 rear-1.17.2-8.el6_10.i686.rpm x86_64:

Hi! I'm getting these frequently. several times I've done the steps listed there to suppress the messages, but I keep getting them. Anyone got a good idea how to deal with this? Thanks in advance! ---------------------------- SELinux is preventing mdadm from 'read, open' accesses on the file /var/log/rear/rear-fcshome.log.lockless. ***** Plugin restorecon (99.5 confidence)

CentOS Errata and Bugfix Advisory 2017:0090 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0090.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ae747914fe9f29dfa149793a47c4eafa900cd1fca69120b32eeba2b8398a1c27 rear-1.17.2-7.el7_3.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2017:1316 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1316.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8b3831f700576199b652a5573233754e30a6a161b3de65a7b666cda0d022ee57 rear-1.17.2-9.el7_3.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2017:2937 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2937 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 024be5510699ff2696ac06e63ebfe8147bd76abd7235834986752b4d81584873 rear-2.00-3.el7_4.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2018:0168 Upstream details at : https://access.redhat.com/errata/RHBA-2018:0168 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0e16bbcadc843b56a882374fdea3021125e041d6d791be83bf34895fc126385b rear-2.00-4.el7_4.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2018:0419 Upstream details at : https://access.redhat.com/errata/RHBA-2018:0419 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 30a83520f2cd54903fbea41f84c74d206aa5ff468d8d09fd85d3c1cb9ae0b402 rear-2.00-5.el7_4.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:0498 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0498 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 460b753777046b5da6c8839289eb11607f48b9624a78b1a5df33e07ef97b21ad rear-2.4-4.el7_6.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:1876 Upstream details at : https://access.redhat.com/errata/RHBA-2019:1876 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e0b00ed45de32d7cec4c24f9b0832206b495b7a132edaf5c9213e08ac437943a rear-2.4-5.el7_6.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:2603 Upstream details at : https://access.redhat.com/errata/RHBA-2019:2603 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3d2ffc86df0d4e4645a73e97f6ed4efcdc6d859cfa8a2ac003bf7bcd2fd1fe57 rear-2.4-9.el7_7.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2019:3069 Upstream details at : https://access.redhat.com/errata/RHBA-2019:3069 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c4700ea98f087e2852e04889b61cb7b227769e0e88b84e13f76eb10e376dacab rear-2.4-10.el7_7.x86_64.rpm Source:

On 25/01/15 18:07, Stefan Kania wrote: > Or you try this: > http://relax-and-recover.org/ > With Rear it ist possible to do a P2V migration. Hello Stefan Oh wow, amazing piece of software... the YouTube video sold it to me. REAR could be very useful. List - I'll take all your comments under my wing, and return with a full report. Many thanks. :) Paul Littlefield

I've got a CentOS 5 server that I want to migrate over into a virtualized instance. The problem is I need to minimize downtime so was trying to figure out a way to "live" clone the original. Initially, I thought I could do this via exporting an iSCSI target from the virtual host, create a MD raid 1 array on the C5 server, wait for it to sync, then shutdown the physical server and

...dataframe of bird nest check observations, in which I know the date of the first check, the date of the second check (both currently in Julian date format), the status of the nest at the second check (alive or failed), and the date that the nest hatched (i.e. changed from Incubation stages to Brood-rearing stage). Many nests have more than one record, as there were several nest checks throughout the duration of the nesting attempt. What I want to do is assign a nest Stage variable, either Incubation or Brood-rearing. It's very easy to do so when the second nest check was before the hatch date (i...

On 04. mars 2018 03:03, Fred Smith wrote: > Every now and then I get an alert like this one. I have no clue what this > "rear" subsystem is, or why madam would be trying to write to its log > file. ReaR is Relax-and-Recover tool: http://relax-and-recover.org/ It creates a bootable CD/DVD with all backup content to restore your system. > If you want to fix the label. >

CentOS Errata and Bugfix Advisory 2018:2458 Upstream details at : https://access.redhat.com/errata/RHBA-2018:2458 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6f703578ac65e4aad512f78328bdf01c0aeb932b299fe92562678d079622fa92 rear-2.00-7.el7_5.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ }