Cannot process initial configuration

[itssbh]

Hi,
I get stuck in the initial configuration:

Code: Select all

Determining if ip address xxx.xxx.xxx.xxx is already in user for device eth0...
[ERROR] Unable to resolve efa-project.org.
Check your connectivity...

This happens whether I set up full dns recursion or enter external or internal dns. Firewall is fully opened for efa at this time and I can successfully ping google's dns ip 8.8.8.8 at this point. How can I look further into this?

Thanks for any help.
Regards, Martin


EDIT:
Forgot to mention I work with a VMware Image.
I have just tried with version 3.0.0.8 and with that one it works fine. So this could be a bug in 3.0.0.9?

[shawniverson]

I am not seeing this behavior. Any other details?

[shawniverson]

Just to be sure, I'm re-downloading the vmware image and firing up...

[shawniverson]

Still not seeing the issue. What version of VMware are you using?

[ALA-IT]

Add to this, I am getting this as well, but on the Hyper-V Image.

Running Server 2012 R2 Standard with Hyper-V Role installed. Only role on server. Server is patched up to April 7th.
EFA version 3.0.0.9
Firewall is Dell/Sonicwall NSA 2600 and port 53 is open.

Go through the EFA-Init process and set all settings. When I type OK, it verifies IP then comes up with this:

[ERROR] Unable to resolve efa-project.org
Check your connectivity to the Internet and ensure that your DNS is functional.
Then try and run EFA-Init again.

I try both Recursive and assigning to internal DNS and no go.

[ALA-IT]

In troubleshooting, I reviewed both resolv.conf and ifcfg-eth0, and both do not have any DNS info. If I add DNS to either those areas and restart network service, I can then successfully resolve names. But if I run through the EFA-Init program, it removes those entries. Looks like the config script may not be writing the DNS info correctly.

[ALA-IT]

Modifying /etc/resolve.conf with DNS (nameserver=X.X.X.X), locking the file, restarting network service, and not using recursive DNS in the EFA-Init allowed me to continue. It is now successfully working.

[itssbh]

Sorry for the late response but I was out of office. I got this error on vSphere 5.5 U2. I could manage it by first installing version 3.0.0.8 and then update to v3.0.0.9. And I can exactly confirm the mentioned details of ALA-IT.

[shawniverson]

Is a DHCP server on your network handing out DNS or not?

EFA-Init depends on this.

[itssbh]

That's it. I tried to install EFA without handing out DNS-Servers.
But it worked with 3.0.0.8 within the same configuration. Anyway the update path went fine...
Thanks a lot for EFA!

[shawniverson]

https://github.com/E-F-A/v3/issues/268