Unsolved
This post is more than 5 years old
21 Posts
0
5974
FLR for Vmware failing with error Can't connect to recover agent dial unix /var/run/vflragentd.sock: connect: no such file or directory]
Hello,
i've been facing this issue for days while trying to initiate File Level Recovery for Unix VM :
159373:nsrvproxy_flr: vProxy Log: 2017/06/30 12:39:33 ERROR: [@(#) Build number: 140] Could not mount VMDKs [[EMC-FLR-vproxy-1493818761] vm-3930-disk-key-2000.vmdk] onto VM 'unixvm' (vm-3930) filesystems: [Can't connect to recover agent dial unix /var/run/vflragentd.sock: connect: no such file or directory]
152793:nsrvproxy_flr: vProxy Log Ends =================================================
150017:nsrvproxy_flr: Saveset Mount was terminated...
Seems the flr recovery process is not able to start the service vflragent automatically.
If we check in /var/run, vflragent.sock is not present :
[root@unixvm bin]# ls/var/run | grep vflr
[root@unixvm bin]#
Identified the install path of vflagent and found the service vflragent was not running :
[root@unixvm bkp_client]# rpm -qpl ./emc-vProxy-FLRAgent-2.0.2-11_1.x86_64.rpm
warning: ./emc-vProxy-FLRAgent-2.0.2-11_1.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 9f298f87: NOKEY
/opt/emc/vproxyra/bin
/opt/emc/vproxyra/bin/postinstall.sh
/opt/emc/vproxyra/bin/preremove.sh
/opt/emc/vproxyra/bin/vflragent
/opt/emc/vproxyra/bin/vflragentc
/opt/emc/vproxyra/bin/vflragentd
/opt/emc/vproxyra/bin/vflragentd.bin
/opt/emc/vproxyra/bin/vflrcopy
/opt/emc/vproxyra/bin/vflrmount
/opt/emc/vproxyra/bin/vproxyra.env
/opt/emc/vproxyra/logs
[root@unixvm run]# cd /opt/emc/vproxyra/bin
[root@unixvm bin]# ./vflragent status
EMC vProxy FLR Agent is stopped
Manually Start the service:
[root@unixvm bin]# ./vflragent start
Starting EMC vProxy FLR Agent...
[root@unixvm bin]# ./vflragent status
EMC vProxy FLR Agent is running
And now the vflragent.sock is present in /var/run
[root@unixvm run]# ls /var/run | grep vflr
vflragentd.sock
As soon as the vflragent is running, the FLR process will works perfectly fine :
159373:nsrvproxy_flr_recover: vProxy Log: 2017/07/05 17:15:51 INFO: [@(#) Build number: 140] File copying completed.
159373:nsrvproxy_flr_recover: vProxy Log: 2017/07/05 17:15:51 TRACE: [@(#) Build number: 140] /opt/emc/vproxyra/bin/vflrcopy exiting with status code 0
152793:nsrvproxy_flr_recover: vProxy Log Ends =================================================
162217:nsrvproxy_flr_recover: FLR recover job completed successfully.
164970:nsrvproxy_flr_recover: Requested termination of the FLR mount session 66546.
I suppose this service should start automatically with a FLR request, have to figure out why not in my case. But this workaround will do the job for the moment.
Hope it could help you too
l.walid
26 Posts
0
July 7th, 2017 05:00
It seems to me that it's privileges issues, does the account you specify with flr wizard have rights to start the service ?
Julien_K
21 Posts
0
July 7th, 2017 05:00
This is not a permission issue, we're using a root account.
Manually start the vflragent service allows to proceeding with the FLR
l.walid
26 Posts
0
July 7th, 2017 05:00
Also please specify version of networker and vmware
l.walid
26 Posts
0
July 10th, 2017 06:00
Hi,
Please specify Networker version and vmware, how did you install the flr agent ? Manually or using the NMC Wizard (Networker 9.1 or later)
Can you also upload the full logs of the process, thank you
epaape
15 Posts
0
August 3rd, 2018 01:00
Hi,
i ran into the same issue today. Networker Version 9.2.1.4 and vProxy 2.1.1-41. flragent was not running. Was installed via NMC.
Is this fixed with a newer vProxy version?
Regards Eike
PrinceAijaz
38 Posts
0
August 3rd, 2018 02:00
Verify if vflragentd running on the target Linux VM .
ps –eaf |grep emc
If not running do the following on target VM .
On target Linux VM, run postinstall.sh which is located under the bin folder
This will manually start the vflragentd on the target client
Perform FLR to recover to a directory other than /tmp
PrinceAijaz
38 Posts
0
August 3rd, 2018 02:00
On target Linux VM, run postinstall.sh which is located under the bin folder
This will manually start the vflragentd on the target client .
Note that this is a feature of a Linux subsystem which is not managed or detectable by the vProxy or agent.
Julien_K
21 Posts
0
August 3rd, 2018 05:00
Hello,
What kind of error do you have with the vproxy ?
i have the same NW / vproxy version had no issue during the install.
thanks,
Julien
Le ven. 3 août 2018 à 12:49, EikePaape a
écrit :