Unsolved
This post is more than 5 years old
39 Posts
0
7823
February 22nd, 2011 23:00
Failed to resolve the IPv6 localhost address
Hi
I have a Networker server 7.6.1 with Red Hat ES5 as OS
Everything worked fine until tonight.
Networker didnt start any Backups tonight.
It was also imposible to start a Backup by hand. No reaction from Networker.
So i reboot the Networker server.
The Server reboot and came up normaly but Networker didnt start.
If i start Networker by hand (service networker start) i got this messages.
(pid 7051): Failed to resolve the IPv6 localhost address ::1. Please verify an entry for the IPv6 localhost address exists in your /etc/hosts file.
nsrd: Failed to resolve the IPv6 localhost address ::1. Please verify an entry for the IPv6 localhost address exists in your /etc/hosts file.
Then i made a entry in the host file.
::1 localhost loopback
Networker starts now but if i try to open the you i got the message after the Login screen "Connection refused"
Why is Networker using now IPv6 ? We use only IPv4.
Any Idee?
Thanks for your help.
Stivi
coganb
736 Posts
0
March 4th, 2011 04:00
Sorry - looks like nobody got to answering this one,
Do you still have the issue?
If so, have you tried checking in /etc/sysconfgi/network and /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever the interface is called)
and making sure ipv6 is disabled in there.
If it is, then it is likely that your new communication problems have nothing to do with ipv6 and you'll have to look elsewhere for the
cause of the problem (network connection, name resolution, services down somewhere etc.)
Let us know how it's going either way and someone will be sure to get back to you a bit quicker this time....
-Bobby
ble1
4 Operator
•
14.4K Posts
0
March 11th, 2011 17:00
I had few issues with RHEL5.5 since way to disable IPv6 there has changed compared to earlier releases and since IPv6 are created in such case NW checks for them (as it support IPv6 in all recent releases). What you did is wrong; you should not assign localhost name to ::1 if you use IPv4 or mixed IPv4 and IPv6. I would suggest to use rather:
or disable IPv6.
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.