#3231 Issue `closed`: I cant able to recover my ubuntu machine, its getting terminted¶

Labels: support / question, won't fix / can't fix / obsolete

Viswa8pk opened issue at 2024-05-22 09:22:¶

relax-and-recover 2.5 / Git
running rear recover (PID 2303)
Using log file: /var/log/rear/rear-uat-ipo.log
Running workflow recover within the ReaR rescue/recovery system
Starting required daemons for NFS: RPC portmapper (portmap or rpcbind) and rpc.statd if available.
Started RPC portmapper 'rpcbind'.
ERROR: RPC portmapper 'rpcbind' unavailable.
Some latest log messages since the last called script 050_stat_required_nfs_demons.sh:
2024-05-22 11:50 Incuding verify/NETFS/default/050_stat_required_nfs_daemons.sh
2024-05-22 11:50 Starting required daemons for NFS: RPC portmapper  (portmap or rpcbind) and rpc.statd if availabe.
/usr/share/rear/lib/_input-output-functions.sh: line 457: type: portmap: not found
2024-05-22 11:50 started RPC portmapper 'rpcbind'
Aborting due to an error, check /var/log/rear/rear-uat-ipo.log for details 
Existing rear recover (PID 2303) and its descendant proccess ....
Running exit tasks
you should also rm -rf /tmp/rear.exHgPalDgDMD6
Terminated

Rear-error

jsmeix commented at 2024-05-22 12:15:¶

https://raw.githubusercontent.com/rear/rear/master/.github/ISSUE_TEMPLATE.md

Viswa8pk commented at 2024-05-24 03:31:¶

how to resolve this issue, i got the errors portmapper, but its available in my client and server side.

jirib commented at 2024-08-02 09:25:¶

iiuc it might be related to failing rpcbind -s; is that the case? See /var/log/rear/rear-localhost.log after executing ReaR with rear -d -D rescue.

gdha commented at 2024-09-05 08:46:¶

@Viswa8pk try to start rpcbind manually when in recovery mode and tell us what happens?

[Export of Github issue for rear/rear.]