#2653 Issue `closed`: Error on recover: RPC portmapper 'rpcbind' unavailable on Debian 10¶

Labels: support / question, no-issue-activity

alexgdi opened issue at 2021-07-10 20:01:¶

Relax-and-Recover (ReaR) Issue Template¶

Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):

ReaR version ("/usr/sbin/rear -V"): Relax-and-Recover 2.4 / Git
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"): Debian 10
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

OUTPUT=ISO  
OUTPUT_URL=nfs://10.0.0.2/srv/nfs  
BACKUP=NETFS  
BACKUP_URL=nfs://10.0.0.2/srv/nfs  
USE_DHCLIENT=  
USE_STATIC_NETWORKING=y  
NETWORKING_PREPARATION_COMMANDS=( 'ip addr add 10.0.0.1/24 dev ens34' 'ip link set dev ens34 up' 'return' )  
ISO_DEFAULT="automatic"  
ISO_RECOVER_MODE=unattended

Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM 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 and 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,SIZE,MOUNTPOINT" or "lsblk" as makeshift):

loop0                7:0    0 99.4M  1 loop /snap/core/11316
loop1                7:1    0 42.2M  1 loop /snap/certbot/1201
loop2                7:2    0 61.7M  1 loop /snap/core20/1026
loop3                7:3    0 42.4M  1 loop /snap/certbot/1280
sda                  8:0    0   10G  0 disk
├─sda1               8:1    0  487M  0 part /boot
├─sda2               8:2    0    1K  0 part
└─sda5               8:5    0  9.5G  0 part
  ├─gw1--vg-root   254:0    0  8.6G  0 lvm  /
  └─gw1--vg-swap_1 254:1    0  976M  0 lvm  [SWAP]
sr0                 11:0    1   70M  0 rom

Description of the issue (ideally so that others can reproduce it):

Hello! When I try to restore, I get an error RPC unaviable. The problem is similar to #2487 .

ERROR: RPC portmapper 'rpcbind' unavailable

I use only NFSv4 and i don't need compatibility with NFSv3.

I get an error when trying to run rpcinfo -p in the recovery environment.

rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused

If I edit in /usr/share/rear/verify/NETFS/default/050_start_required_nfs_daemons.sh to

test "ok" = $ attempt || LogPrint "RPC portmapper '$ portmapper_program' unavailable."

Then everything works.

I also tried the rear 2.6 package and it didn't help. I am getting another error related to NFS.

You have a very cool product, Thank you!

Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
rear-gw1_recover.log
rear-gw1_backup.log

gdha commented at 2021-07-11 07:56:¶

Add the following to your local.conf file:

PROGS=( "${PROGS[@]}" showmount mount.nfs umount.nfs )
MODULES=( "${MODULES[@]}" nfs )
PRE_RECOVERY_SCRIPT="systemctl start rpcbind.target"

alexgdi commented at 2021-07-11 14:18:¶

This didn't change the error. All the same

jsmeix commented at 2021-07-12 11:22:¶

Relax-and-Recover 2.4 is rather old (from June 2018), cf.
https://github.com/rear/rear/blob/master/doc/rear-release-notes.txt
so you may try out if things perhaps work with our current master code.

See the section "Testing current ReaR upstream GitHub master code" in
https://en.opensuse.org/SDB:Disaster_Recovery

In general we at ReaR upstream support (on a voluntary basis)
only the newest ReaR upstream version or
preferably the ReaR upstream GitHub master code.

This does not mean we reject all issues with older ReaR versions
but we only spend time with older ReaR versions when it is obvious
that the issue also exists in current ReaR upstream GitHub master code
because we fix only the ReaR upstream GitHub master code.

Therefore "Testing current ReaR upstream GitHub master code"
would help us at ReaR upstream most and at the same time
it should help you most because when you are used to use
our current upstream master code you get all our fixes directly.

Fukit204 commented at 2021-08-05 04:59:¶

Idk any of this but how can i block this on my wifi router?? Someone is stealing my data

gdha commented at 2021-08-05 06:47:¶

@alexgdi Try with commenting ISO_RECOVER_MODE=unattended and login as root and see what the status is on that point.
Does rpcinfo -p working? Is portmap executable available? Try to start it manual first.