This post is more than 5 years old
11 Posts
2
19900
December 20th, 2012 09:00
savefs: Failed to resolve the IPv6 localhost address ::1. Please verify an entry for the IPv6 localhost address exists in your /etc/hosts file.
We have an IBM AIX 6.1 server. The NetWorker 8.0 client was installed to this server and failed to work with this error:
savefs: Failed to resolve the IPv6 localhost address::1. Please verify an entry for the IPv6 localhost address exists in your /etc/hosts file.
First of all, an entry for the IPv6 localhost address ::1 exists in the AIX /etc/hosts file. Also, an entry for the AIX host exists in the NetWorker server (Windows) hosts file.
This is known issue and the only workaround suggested by the EMC community is to disable IPv6 on a client computer. I keep disabling IPv6 on my other Windows 2008 servers when they fail to run NetWorker because of IPv6. And, once I deleted IPv6 off my AIX server (ifconfig lo0 inet6 ::1/0 delete) the NetWorker started working fine. Apparently, there were other services running on the AIX depending on IPv6 and the services crashed (I learned about it hard way). I put IPv6 back (ifconfig lo0 inet6 ::1/0) - the services started working, but the NetWorker stopped working with the above mentioned error again.
How, please, how to tell the NetWorker 8.0 forget about IPv6?
0 events found
Juga_c278d5
11 Posts
0
December 27th, 2012 14:00
Michael, thank you very much for your time and support!
The problem solved. The continuous error told me that there was something wrong with IPv6 addresses resolution, and, since ::1 was declared in /etc/hosts, it looked like the AIX server did not look into the /etc/hosts for IPv6 name resolution.
For some unknown to me reason the /etc/netsvc.conf file contained hosts=local4,bind4 only, which prevented the server from local IPv6 name resolution.
After I edited /etc/netsvc.conf with hosts=local,bind - the NetWorker started working!
Thank you again!
coganb
736 Posts
0
December 21st, 2012 06:00
Hi,
I don't think you can have NetWorker specifically ignore ipv6 as it will use the same name resolution as other applications on the machine. I think you should more concentrate on trying to get NetWorker to work with ipv6 which it should do.
-Bobby
ble1
4 Operator
•
14.4K Posts
0
December 26th, 2012 13:00
I have few AIX clients and they work fine. We use in /etc/hosts something like:
127.0.0.1 localhost loopback
::1 localhost6.localdomain6 localhost6
Juga_c278d5
11 Posts
0
December 27th, 2012 11:00
Michael, you are right - the NetWorker installation surprisingly updated my /etc/hosts file.
However, the NetWorker server came out with the error anyway. After that I started to investigate and figured out that the only way to make NetWorker work is to disable IPv6 altogether, which is not a good plan in my case. Any other plans?
rochem1
23 Posts
0
December 27th, 2012 11:00
How about the clients that the savefs is being used to probe? Are they also properly updated?
Juga_c278d5
11 Posts
0
December 27th, 2012 11:00
Thanks Hrvoje. I have exactly like this. However, the NetWorker server (Windows 2008) still fails to resolve the IPv6.
rochem1
23 Posts
1
December 27th, 2012 13:00
Is the ::failure coming from the remote AIX client or the NW server
savefs -p -c -s -vvvv
Juga_c278d5
11 Posts
0
December 27th, 2012 13:00
The same... No more details.
Juga_c278d5
11 Posts
0
December 27th, 2012 13:00
Michael,
We have no more Unix clients - only that one AIX.
When I run savefs -p on it - it comes with the same error
savefs: Failed to resolve the IPv6 localhost address ::1. Please verify an entry for the IPv6 localhost address exists in your /etc/hosts file.
Again, I do have ::1 localhost in /etc/hosts !!!
BACKUP_S
4 Posts
0
December 23rd, 2013 21:00
Hi Booby,
I am getting same error for RHEL linux , in /etc/hosts file all ready entries where there , IPv6 is disabled on server .
I am not able to start client service's
[root@ ~]# /etc/init.d/networker start
nsrexecd: Failed to resolve the IPv6 localhost address ::1. Please verify an entry for the IPv6 localhost address exists in your /etc/hosts file.
[root@ ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost
::1 localhost6.localdomain6 localhost6
CAN you please let me know any solution
rochem1
23 Posts
0
December 24th, 2013 10:00
As indicated previously in this thread, disabling IPv6 should not be done. The failure you are experiencing stems from not being able to resolve the IPv6 loopback address. Although it is present in /etc/hosts, disabling IPv6 prevents the resolving of the loopback.
There is potential for many aspects of the OS to incorrectly perform by disabling IPv6. Maintain the support but do not configure it.
ble1
4 Operator
•
14.4K Posts
0
December 26th, 2013 05:00
Can you explain how disabling IPv6 prevents the resolving of the loopback? We by default have IPv6 disabled on RH5.x and we never had any issues with loopback (or IPv6 related incidents).
albano93
1 Message
0
May 22nd, 2015 02:00
Thx for the solution. That also worked for me
Anonymous User
30 Posts
0
February 19th, 2016 13:00
I have been running into this issue a lot. The windoze guys will not let me disable IPv6 as its an 'integral' part of the OS now. Gotta love MS.
Anyway I decided to add the IPv6 address as an alias in Globals 1 of 2.
So far all the ones I have done have worked.
This has to be the easiest way round this issue.