Second Run Fails

[jonmosco]

I'm very new to Puppet, so this might not be a direct issue with this module. After the 2nd attempt to run this for testing, I get the following error:

info: Retrieving plugin err: /File[C:/ProgramData/PuppetLabs/puppet/var/lib]: Failed to generate additional resources using 'eval_generate: getaddrinfo: The storage control blocks were destroyed.  err: /File[C:/ProgramData/PuppetLabs/puppet/var/lib]: Could not evaluate: getaddrinfo: The storage control blocks were destroyed. Could not retrieve file metadata for puppet://puppet.tstnt.tsthq.org/plugins: getaddrinfo: The storage control blocks were destroyed.  info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/concat_basedir.rb info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/custom_auth_conf.rb info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/facter_dot_d.rb info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/pe_version.rb info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/puppet_vardir.rb info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/root_home.rb info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/win_common_desktop_directory.rb err: Could not retrieve catalog from remote server: getaddrinfo: The storage control blocks were destroyed.  warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run err: Could not send report: getaddrinfo: The storage control blocks were destroyed. 

[rismoney]

i think this could be a dns issue. can you ping the puppet master from the node? you need a valid suffix in tcp/ip. puppet incorrectly IMHO uses the first nic dns suffix it finds to generate the nodes fqdn. it should should the system suffix...

when i wrote this, 2 days ago i did so in an environment where I maintain suffixes in a domain group policy. we probably do want the ability to put the suffix in.

can you readd the domain name into your nic property to see if it resolves the issue?

[jonmosco]

I can ping the puppet master from the node still. It seems as though the dns suffix is still present unless I am looking in the wrong location.

On Fri, Feb 8, 2013 at 2:16 PM, Rich Siegel notifications@github.comwrote:

i think this could be a dns issue. can you ping the puppet master from the node? you need a valid suffix in tcp/ip. puppet incorrectly IMHO uses the first nic dns suffix it finds to generate the nodes fqdn. it should should the system suffix...

when i wrote this, 2 days ago i did so in an environment where I maintain suffixes in a domain group policy. we probably do want the ability to put the suffix in.

can you readd the domain name into your nic property to see if it resolves the issue?

— Reply to this email directly or view it on GitHubhttps://github.com/rismoney/puppet-windowsnetwork/issues/1#issuecomment-13306398..

[rismoney]

check nic - properties / IP Protocol Version 4 (TCP/IPv4) / Properties / Advanced / DNS / "DNS suffix for this connection"

is this the only nic active on your pc?

[jonmosco]

The option for "append primary and connection specific DNS suffixes and the append parent suffixes" are both checked. Yes, this is the only interface on this, its a Server 2008R2 VM.

On Fri, Feb 8, 2013 at 2:36 PM, Rich Siegel notifications@github.comwrote:

check nic - properties / IP Protocol Version 4 (TCP/IPv4) / Properties / Advanced / DNS / "DNS suffix for this connection"

is this the only nic active on your pc?

— Reply to this email directly or view it on GitHubhttps://github.com/rismoney/puppet-windowsnetwork/issues/1#issuecomment-13307325..

[jonmosco]

I see the bottom to options for dns suffix are selected. On my other servers, only the first option for resiter this connections address in DNS is selected.

On Fri, Feb 8, 2013 at 2:39 PM, Jon Mosco jonny.mosco@gmail.com wrote:

The option for "append primary and connection specific DNS suffixes and the append parent suffixes" are both checked. Yes, this is the only interface on this, its a Server 2008R2 VM.

On Fri, Feb 8, 2013 at 2:36 PM, Rich Siegel notifications@github.comwrote:

check nic - properties / IP Protocol Version 4 (TCP/IPv4) / Properties / Advanced / DNS / "DNS suffix for this connection"

is this the only nic active on your pc?

— Reply to this email directly or view it on GitHubhttps://github.com/rismoney/puppet-windowsnetwork/issues/1#issuecomment-13307325..

[rismoney]

put your host domain name into this suffix textbox

[jonmosco]

Ok. If I uncheck that option, the puppet run will apply it. Also what is strange is it is no longer failing.

On Fri, Feb 8, 2013 at 2:41 PM, Jon Mosco jonny.mosco@gmail.com wrote:

I see the bottom to options for dns suffix are selected. On my other servers, only the first option for resiter this connections address in DNS is selected.

On Fri, Feb 8, 2013 at 2:39 PM, Jon Mosco jonny.mosco@gmail.com wrote:

The option for "append primary and connection specific DNS suffixes and the append parent suffixes" are both checked. Yes, this is the only interface on this, its a Server 2008R2 VM.

On Fri, Feb 8, 2013 at 2:36 PM, Rich Siegel notifications@github.comwrote:

check nic - properties / IP Protocol Version 4 (TCP/IPv4) / Properties / Advanced / DNS / "DNS suffix for this connection"

is this the only nic active on your pc?

— Reply to this email directly or view it on GitHubhttps://github.com/rismoney/puppet-windowsnetwork/issues/1#issuecomment-13307325..

[rismoney]

this is the actual issue - http://projects.puppetlabs.com/issues/12864

[rismoney]

i should put dns connection suffix into this, as i foresee this to be crop up a lot.

[jonmosco]

ahh, yes, I understand the issue now. The windows domain is different from the DNS domain. Thank you for all the help.

On Fri, Feb 8, 2013 at 2:47 PM, Rich Siegel notifications@github.comwrote:

i should put dns connection suffix into this, as i foresee this to be crop up a lot.

— Reply to this email directly or view it on GitHubhttps://github.com/rismoney/puppet-windowsnetwork/issues/1#issuecomment-13307828..

[jonmosco]

My apologies for my understanding of this issue, I am not a full time windows admin.

On Fri, Feb 8, 2013 at 2:49 PM, Jon Mosco jonny.mosco@gmail.com wrote:

ahh, yes, I understand the issue now. The windows domain is different from the DNS domain. Thank you for all the help.

On Fri, Feb 8, 2013 at 2:47 PM, Rich Siegel notifications@github.comwrote:

i should put dns connection suffix into this, as i foresee this to be crop up a lot.

— Reply to this email directly or view it on GitHubhttps://github.com/rismoney/puppet-windowsnetwork/issues/1#issuecomment-13307828..

[rismoney]

added suffix and dnshost domain https://github.com/rismoney/puppet-windowsnetwork/pull/2

[rismoney]

i know the suffix is the issue but i need to figure out a way to guard against the node going unreachable...

i may have a good repro....investigating

[rismoney]

closing. the backoff timer, address node going unreachable