-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on recover: RPC portmapper 'rpcbind' unavailable on Debian 10 #2653
Comments
Add the following to your local.conf file:
|
This didn't change the error. All the same |
Relax-and-Recover 2.4 is rather old (from June 2018), cf. See the section "Testing current ReaR upstream GitHub master code" in In general we at ReaR upstream support (on a voluntary basis) This does not mean we reject all issues with older ReaR versions Therefore "Testing current ReaR upstream GitHub master code" |
Idk any of this but how can i block this on my wifi router?? Someone is stealing my data |
@alexgdi Try with commenting ISO_RECOVER_MODE=unattended and login as root and see what the status is on that point. |
Block port 111 on the router |
Stale issue message |
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"):
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):
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
totest "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
The text was updated successfully, but these errors were encountered: