Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-12-02 Thread Arvind P R
Hello,

I am a new user.
My pupet is running on CentOS and I am facing the same issue on my windows 
2012 box.
Can you please tell me where I should be running this?

on the puppetmaster server or agent?

I didnt make the changes to the windows.rb file but I still face the same 
issue.

[root@puppet-server-new ~]# find / -name windows.rb
/opt/puppet/libexec/mcollective/mcollective/util/puppet_agent_mgr/v3/windows.rb
/opt/puppet/libexec/mcollective/mcollective/util/puppet_agent_mgr/v2/windows.rb
/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util/windows.rb
/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/file/windows.rb
/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/service/windows.rb
/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/exec/windows.rb
/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/windows.rb
/opt/puppet/lib/ruby/site_ruby/1.9.1/facter/util/ip/windows.rb
/opt/puppet/share/puppet/modules/reboot/lib/puppet/provider/reboot/windows.rb
/opt/puppet/share/puppet/modules/pe_common/lib/facter/windows.rb
/opt/puppet/share/puppet/modules/pe_mcollective/files/plugins/util/puppet_agent_mgr/v3/windows.rb
/opt/puppet/share/puppet/modules/pe_mcollective/files/plugins/util/puppet_agent_mgr/v2/windows.rb
/opt/puppet/share/vendor/ruby/1.9.1/gems/sass-3.2.9/vendor/listen/lib/listen/adapters/windows.rb
/root/facter-1.7.3/lib/facter/util/ip/windows.rb
/var/opt/lib/pe-puppet/lib/puppet/provider/reboot/windows.rb
/var/opt/lib/pe-puppet/lib/facter/windows.rb
/usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb

I see a bunch of windows.rb files.

I made the changes to the below one on puppetmaster box.
[root@puppet-server-new ~]# vi 
/usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb


Still the same issue on Windows 2012 Hyper-V box running MSCS
C:\Users\administrator.A1000puppet agent -t
Info: Retrieving plugin
Error: Could not retrieve local facts: undefined method `gsub' for 
nil:NilClass
Error: Failed to apply catalog: Could not retrieve local facts: undefined 
method
 `gsub' for nil:NilClass


On Friday, October 4, 2013 12:17:38 AM UTC+5:30, Rob Reynolds wrote:

 This verifies for us that this is a gating issue. 

 Would you feel comfortable helping us verify that we've fixed this issue 
 for you?


 https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47




 On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep der...@gmail.comjavascript:
  wrote:

 Yes, thats all i got from *facter --trace --debug*


 On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds 
 r...@puppetlabs.comjavascript:
  wrote:

 Was this the entire log (minus anything you feel sensitive)?


 On Thu, Oct 3, 2013 at 1:15 PM, cko der...@gmail.com javascript:wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run 

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use? 


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian - 

 I'm doing the final verification of our fix, and was hoping that I 
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds 
 r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix 
 where we look to see that the network adapter itself is also enabled. 
 This 
 is laid out in the ticket that I noted earlier.
  

 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in question 
 the dag ip.

 My guess is the logic for adapters should be modded for when 
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless 
 you understand ramifications.

 --
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to puppet-users...@googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
  
 -- 
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to puppet-users...@googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*
  
  -- 
 You received this 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-12-02 Thread Rob Reynolds
On Mon, Dec 2, 2013 at 12:31 PM, Arvind P R iin...@gmail.com wrote:

 Hello,

 I am a new user.
 My pupet is running on CentOS and I am facing the same issue on my windows
 2012 box.
 Can you please tell me where I should be running this?

 on the puppetmaster server or agent?

 I didnt make the changes to the windows.rb file but I still face the same
 issue.

 [root@puppet-server-new ~]# find / -name windows.rb

 /opt/puppet/libexec/mcollective/mcollective/util/puppet_agent_mgr/v3/windows.rb

 /opt/puppet/libexec/mcollective/mcollective/util/puppet_agent_mgr/v2/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/file/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/service/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/exec/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/facter/util/ip/windows.rb

 /opt/puppet/share/puppet/modules/reboot/lib/puppet/provider/reboot/windows.rb
 /opt/puppet/share/puppet/modules/pe_common/lib/facter/windows.rb

 /opt/puppet/share/puppet/modules/pe_mcollective/files/plugins/util/puppet_agent_mgr/v3/windows.rb

 /opt/puppet/share/puppet/modules/pe_mcollective/files/plugins/util/puppet_agent_mgr/v2/windows.rb

 /opt/puppet/share/vendor/ruby/1.9.1/gems/sass-3.2.9/vendor/listen/lib/listen/adapters/windows.rb
 /root/facter-1.7.3/lib/facter/util/ip/windows.rb
 /var/opt/lib/pe-puppet/lib/puppet/provider/reboot/windows.rb
 /var/opt/lib/pe-puppet/lib/facter/windows.rb
 /usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb

 I see a bunch of windows.rb files.

 I made the changes to the below one on puppetmaster box.
 [root@puppet-server-new ~]# vi
 /usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb


 Still the same issue on Windows 2012 Hyper-V box running MSCS
 C:\Users\administrator.A1000puppet agent -t
 Info: Retrieving plugin
 Error: Could not retrieve local facts: undefined method `gsub' for
 nil:NilClass
 Error: Failed to apply catalog: Could not retrieve local facts: undefined
 method
  `gsub' for nil:NilClass


Can you run facter --trace --debug as well and report what you are seeing?




 On Friday, October 4, 2013 12:17:38 AM UTC+5:30, Rob Reynolds wrote:

 This verifies for us that this is a gating issue.

 Would you feel comfortable helping us verify that we've fixed this issue
 for you?

 https://github.com/ferventcoder/facter/blob/
 874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/
 windows.rb#L46-L47




 On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep der...@gmail.com wrote:

 Yes, thats all i got from *facter --trace --debug*


 On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds r...@puppetlabs.comwrote:

 Was this the entire log (minus anything you feel sensitive)?


 On Thu, Oct 3, 2013 at 1:15 PM, cko der...@gmail.com wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian -

 I'm doing the final verification of our fix, and was hoping that I
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds 
 r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix
 where we look to see that the network adapter itself is also enabled. 
 This
 is laid out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in
 question the dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless
 you understand ramifications.

 --
 You received this message because you are subscribed to the
 Google Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 --
 Ethan Brown
 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-12-02 Thread Arvind P R
Thanks for your prompt answer.

I ran this on the windows (Hyper-V) node which  is running MSCS cluster.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\administrator.A1000facter --trace --debug
←[0;32mNot an EC2 host←[0m
C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/facter/util/ip.r
b:39:in `alphafy': undefined method `gsub' for nil:NilClass (NoMethodError)
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/interfaces.rb:35:in `block (2 levels) in top (required)'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/interfaces.rb:34:in `each'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/interfaces.rb:34:in `block in top (required)'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/interfaces.rb:29:in `each'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/interfaces.rb:29:in `top (required)'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/loader.rb:95:in `load'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/loader.rb:95:in `load_file'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/loader.rb:46:in `block (2 levels) in load_all'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/loader.rb:41:in `each'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/loader.rb:41:in `block in load_all'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/loader.rb:38:in `each'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/loader.rb:38:in `load_all'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/util/collection.rb:114:in `load_all'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter.rb:118:in `block (2 levels) in singletonclass'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/lib/fac
ter/application.rb:45:in `run'
from C:/Program Files (x86)/Puppet Labs/Puppet 
Enterprise/facter/bin/fac
ter:16:in `main'


Thanks,
Arvind

On Tuesday, December 3, 2013 1:17:29 AM UTC+5:30, Rob Reynolds wrote:




 On Mon, Dec 2, 2013 at 12:31 PM, Arvind P R iin...@gmail.comjavascript:
  wrote:

 Hello,

 I am a new user.
 My pupet is running on CentOS and I am facing the same issue on my 
 windows 2012 box.
 Can you please tell me where I should be running this?

 on the puppetmaster server or agent?

 I didnt make the changes to the windows.rb file but I still face the same 
 issue.

 [root@puppet-server-new ~]# find / -name windows.rb

 /opt/puppet/libexec/mcollective/mcollective/util/puppet_agent_mgr/v3/windows.rb

 /opt/puppet/libexec/mcollective/mcollective/util/puppet_agent_mgr/v2/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/file/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/service/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/exec/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/facter/util/ip/windows.rb

 /opt/puppet/share/puppet/modules/reboot/lib/puppet/provider/reboot/windows.rb
 /opt/puppet/share/puppet/modules/pe_common/lib/facter/windows.rb

 /opt/puppet/share/puppet/modules/pe_mcollective/files/plugins/util/puppet_agent_mgr/v3/windows.rb

 /opt/puppet/share/puppet/modules/pe_mcollective/files/plugins/util/puppet_agent_mgr/v2/windows.rb

 /opt/puppet/share/vendor/ruby/1.9.1/gems/sass-3.2.9/vendor/listen/lib/listen/adapters/windows.rb
 /root/facter-1.7.3/lib/facter/util/ip/windows.rb
 /var/opt/lib/pe-puppet/lib/puppet/provider/reboot/windows.rb
 /var/opt/lib/pe-puppet/lib/facter/windows.rb
 /usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb

 I see a bunch of windows.rb files.

 I made the changes to the below one on puppetmaster box.
 [root@puppet-server-new ~]# vi 
 /usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb


 Still the same issue on Windows 2012 Hyper-V box running MSCS
 C:\Users\administrator.A1000puppet agent -t
 Info: Retrieving plugin
 Error: Could not retrieve local facts: undefined method `gsub' for 
 nil:NilClass
 Error: Failed to apply catalog: Could not retrieve local facts: undefined 
 method
  `gsub' for nil:NilClass


 Can you run facter --trace --debug as well and report what you are seeing?
  



 On Friday, October 4, 2013 12:17:38 AM UTC+5:30, Rob Reynolds wrote:

 This verifies for us that this is a gating issue. 

 Would you feel comfortable helping us verify that we've fixed this issue 
 for you?

 https://github.com/ferventcoder/facter/blob/
 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-12-02 Thread Rob Reynolds
This change would need to get applied to the node (the agent box).
Apologies I missed where you said you made the change to the puppet master
and not the node.

Most likely that will be at C:\Program Files (x86)\Puppet
Labs\Puppet\facter\lib\facter\util\ip\windows.rb (your path may be slightly
different).


On Mon, Dec 2, 2013 at 1:51 PM, Arvind P R iin...@gmail.com wrote:

 Thanks for your prompt answer.

 I ran this on the windows (Hyper-V) node which  is running MSCS cluster.
 Microsoft Windows [Version 6.3.9600]
 (c) 2013 Microsoft Corporation. All rights reserved.

 C:\Users\administrator.A1000facter --trace --debug
 ←[0;32mNot an EC2 host←[0m
 C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/facter/util/ip.r
 b:39:in `alphafy': undefined method `gsub' for nil:NilClass (NoMethodError)
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/interfaces.rb:35:in `block (2 levels) in top (required)'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/interfaces.rb:34:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/interfaces.rb:34:in `block in top (required)'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/interfaces.rb:29:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/interfaces.rb:29:in `top (required)'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/loader.rb:95:in `load'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/loader.rb:95:in `load_file'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/loader.rb:46:in `block (2 levels) in load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/loader.rb:41:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/loader.rb:41:in `block in load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/loader.rb:38:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/loader.rb:38:in `load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/util/collection.rb:114:in `load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter.rb:118:in `block (2 levels) in singletonclass'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/lib/fac
 ter/application.rb:45:in `run'
 from C:/Program Files (x86)/Puppet Labs/Puppet
 Enterprise/facter/bin/fac
 ter:16:in `main'


 Thanks,
 Arvind

 On Tuesday, December 3, 2013 1:17:29 AM UTC+5:30, Rob Reynolds wrote:




 On Mon, Dec 2, 2013 at 12:31 PM, Arvind P R iin...@gmail.com wrote:

 Hello,

 I am a new user.
 My pupet is running on CentOS and I am facing the same issue on my
 windows 2012 box.
 Can you please tell me where I should be running this?

 on the puppetmaster server or agent?

 I didnt make the changes to the windows.rb file but I still face the
 same issue.

 [root@puppet-server-new ~]# find / -name windows.rb
 /opt/puppet/libexec/mcollective/mcollective/util/
 puppet_agent_mgr/v3/windows.rb
 /opt/puppet/libexec/mcollective/mcollective/util/
 puppet_agent_mgr/v2/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/file/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/service/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/exec/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/facter/util/ip/windows.rb
 /opt/puppet/share/puppet/modules/reboot/lib/puppet/
 provider/reboot/windows.rb
 /opt/puppet/share/puppet/modules/pe_common/lib/facter/windows.rb
 /opt/puppet/share/puppet/modules/pe_mcollective/files/
 plugins/util/puppet_agent_mgr/v3/windows.rb
 /opt/puppet/share/puppet/modules/pe_mcollective/files/
 plugins/util/puppet_agent_mgr/v2/windows.rb
 /opt/puppet/share/vendor/ruby/1.9.1/gems/sass-3.2.9/vendor/
 listen/lib/listen/adapters/windows.rb
 /root/facter-1.7.3/lib/facter/util/ip/windows.rb
 /var/opt/lib/pe-puppet/lib/puppet/provider/reboot/windows.rb
 /var/opt/lib/pe-puppet/lib/facter/windows.rb
 /usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb

 I see a bunch of windows.rb files.

 I made the changes to the below one on puppetmaster box.
 [root@puppet-server-new ~]# vi /usr/lib/ruby/site_ruby/1.8/
 facter/util/ip/windows.rb


 Still the same issue on Windows 2012 Hyper-V box running MSCS
 C:\Users\administrator.A1000puppet agent -t
 Info: Retrieving plugin
 Error: Could not retrieve local facts: undefined method `gsub' for
 nil:NilClass
 Error: Failed to apply catalog: Could not retrieve local 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-12-02 Thread Arvind P R
That worked. Thank you :)

On Tuesday, December 3, 2013 1:57:52 AM UTC+5:30, Rob Reynolds wrote:

 This change would need to get applied to the node (the agent box). 
 Apologies I missed where you said you made the change to the puppet master 
 and not the node.

 Most likely that will be at C:\Program Files (x86)\Puppet 
 Labs\Puppet\facter\lib\facter\util\ip\windows.rb (your path may be slightly 
 different).


 On Mon, Dec 2, 2013 at 1:51 PM, Arvind P R iin...@gmail.com javascript:
  wrote:

 Thanks for your prompt answer.

 I ran this on the windows (Hyper-V) node which  is running MSCS cluster.
 Microsoft Windows [Version 6.3.9600]
 (c) 2013 Microsoft Corporation. All rights reserved.

 C:\Users\administrator.A1000facter --trace --debug
 ←[0;32mNot an EC2 host←[0m
 C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/facter/util/ip.r
 b:39:in `alphafy': undefined method `gsub' for nil:NilClass 
 (NoMethodError)
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/interfaces.rb:35:in `block (2 levels) in top (required)'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/interfaces.rb:34:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/interfaces.rb:34:in `block in top (required)'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/interfaces.rb:29:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/interfaces.rb:29:in `top (required)'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/loader.rb:95:in `load'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/loader.rb:95:in `load_file'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/loader.rb:46:in `block (2 levels) in load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/loader.rb:41:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/loader.rb:41:in `block in load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/loader.rb:38:in `each'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/loader.rb:38:in `load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/util/collection.rb:114:in `load_all'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter.rb:118:in `block (2 levels) in singletonclass'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/lib/fac
 ter/application.rb:45:in `run'
 from C:/Program Files (x86)/Puppet Labs/Puppet 
 Enterprise/facter/bin/fac
 ter:16:in `main'


 Thanks,
 Arvind

 On Tuesday, December 3, 2013 1:17:29 AM UTC+5:30, Rob Reynolds wrote:




 On Mon, Dec 2, 2013 at 12:31 PM, Arvind P R iin...@gmail.com wrote:

 Hello,

 I am a new user.
 My pupet is running on CentOS and I am facing the same issue on my 
 windows 2012 box.
 Can you please tell me where I should be running this?

 on the puppetmaster server or agent?

 I didnt make the changes to the windows.rb file but I still face the 
 same issue.

 [root@puppet-server-new ~]# find / -name windows.rb
 /opt/puppet/libexec/mcollective/mcollective/util/
 puppet_agent_mgr/v3/windows.rb
 /opt/puppet/libexec/mcollective/mcollective/util/
 puppet_agent_mgr/v2/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/util/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/file/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/service/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/exec/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/windows.rb
 /opt/puppet/lib/ruby/site_ruby/1.9.1/facter/util/ip/windows.rb
 /opt/puppet/share/puppet/modules/reboot/lib/puppet/
 provider/reboot/windows.rb
 /opt/puppet/share/puppet/modules/pe_common/lib/facter/windows.rb
 /opt/puppet/share/puppet/modules/pe_mcollective/files/
 plugins/util/puppet_agent_mgr/v3/windows.rb
 /opt/puppet/share/puppet/modules/pe_mcollective/files/
 plugins/util/puppet_agent_mgr/v2/windows.rb
 /opt/puppet/share/vendor/ruby/1.9.1/gems/sass-3.2.9/vendor/
 listen/lib/listen/adapters/windows.rb
 /root/facter-1.7.3/lib/facter/util/ip/windows.rb
 /var/opt/lib/pe-puppet/lib/puppet/provider/reboot/windows.rb
 /var/opt/lib/pe-puppet/lib/facter/windows.rb
 /usr/lib/ruby/site_ruby/1.8/facter/util/ip/windows.rb

 I see a bunch of windows.rb files.

 I made the changes to the below one on puppetmaster box.
 [root@puppet-server-new ~]# vi /usr/lib/ruby/site_ruby/1.8/
 facter/util/ip/windows.rb


 Still the same issue on Windows 2012 Hyper-V box running MSCS
 C:\Users\administrator.A1000puppet agent -t
 Info: Retrieving plugin

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-08 Thread Jason Harmon
I have the same type of setup with MSCS running in a virtual environment.
The change to the windows.rb file fixed my facter problem as well.
puppet agent --test now completes on the machines now.

On Friday, 4 October 2013 06:13:23 UTC-6, Ethan Brown wrote:

 Christian - 

 Thanks a bunch for taking the time out to verify this.  While we believed 
 our fix was correct, I was trying to replicate your network configuration 
 internally to be absolutely certain.  I was having difficulty getting the 
 virtual machines configured properly with respect to the 'Microsoft 
 Failover Cluster Virtual Adapter', so it's fantastic to hear that you were 
 able to verify this directly in your environment.



 On Fri, Oct 4, 2013 at 6:00 AM, Christian Koep der...@gmail.comjavascript:
  wrote:

 Hi Rob,
 i just applied the changes to the windows.rb file.

 The catalog run finished as usual. Thank you ;-)



 On Thu, Oct 3, 2013 at 8:47 PM, Rob Reynolds 
 r...@puppetlabs.comjavascript:
  wrote:

 This verifies for us that this is a gating issue. 

 Would you feel comfortable helping us verify that we've fixed this issue 
 for you?


 https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47




 On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep 
 der...@gmail.comjavascript:
  wrote:

 Yes, thats all i got from *facter --trace --debug*


 On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds 
 r...@puppetlabs.comjavascript:
  wrote:

 Was this the entire log (minus anything you feel sensitive)?


 On Thu, Oct 3, 2013 at 1:15 PM, cko der...@gmail.com javascript:wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run 

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use? 


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian - 

 I'm doing the final verification of our fix, and was hoping that I 
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds r...@puppetlabs.com
  wrote:

  I would say with all of this in mind we move forward with a fix 
 where we look to see that the network adapter itself is also 
 enabled. This 
 is laid out in the ticket that I noted earlier.
  

 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel 
 rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in 
 question the dag ip.

 My guess is the logic for adapters should be modded for when 
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless 
 you understand ramifications.

 --
 You received this message because you are subscribed to the 
 Google Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from 
 it, send an email to puppet-users...@googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out
 .




 -- 
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
  -- 
 You received this message because you are subscribed to the 
 Google Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to puppet-users...@googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*
  
 -- 
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to puppet-users...@googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
  
 -- 
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to puppet-users...@googlegroups.com javascript:.

 To post to this group, send email to 
 puppet...@googlegroups.comjavascript:
 .
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
  -- 
 You received this message because you are 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-04 Thread Christian Koep
Hi Rob,
i just applied the changes to the windows.rb file.

The catalog run finished as usual. Thank you ;-)



On Thu, Oct 3, 2013 at 8:47 PM, Rob Reynolds r...@puppetlabs.com wrote:

 This verifies for us that this is a gating issue.

 Would you feel comfortable helping us verify that we've fixed this issue
 for you?


 https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47




 On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep dert...@gmail.com wrote:

 Yes, thats all i got from *facter --trace --debug*


 On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds r...@puppetlabs.com wrote:

 Was this the entire log (minus anything you feel sensitive)?


 On Thu, Oct 3, 2013 at 1:15 PM, cko dert...@gmail.com wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian -

 I'm doing the final verification of our fix, and was hoping that I
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds 
 r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix
 where we look to see that the network adapter itself is also enabled. 
 This
 is laid out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in question
 the dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless
 you understand ramifications.

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/**group**
 /puppet-users http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/**grou**
 ps/opt_out https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group**/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit https://groups.google.com/**grou**
 ps/opt_out https://groups.google.com/groups/opt_out.




 --
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.
 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users+unsubscr...@googlegroups.com.

 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/_JSpNmSvg_I/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 puppet-users+unsubscr...@googlegroups.com.

 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-04 Thread Ethan Brown
Christian -

Thanks a bunch for taking the time out to verify this.  While we believed
our fix was correct, I was trying to replicate your network configuration
internally to be absolutely certain.  I was having difficulty getting the
virtual machines configured properly with respect to the 'Microsoft
Failover Cluster Virtual Adapter', so it's fantastic to hear that you were
able to verify this directly in your environment.



On Fri, Oct 4, 2013 at 6:00 AM, Christian Koep dert...@gmail.com wrote:

 Hi Rob,
 i just applied the changes to the windows.rb file.

 The catalog run finished as usual. Thank you ;-)



 On Thu, Oct 3, 2013 at 8:47 PM, Rob Reynolds r...@puppetlabs.com wrote:

 This verifies for us that this is a gating issue.

 Would you feel comfortable helping us verify that we've fixed this issue
 for you?


 https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47




 On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep dert...@gmail.com wrote:

 Yes, thats all i got from *facter --trace --debug*


 On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds r...@puppetlabs.com wrote:

 Was this the entire log (minus anything you feel sensitive)?


 On Thu, Oct 3, 2013 at 1:15 PM, cko dert...@gmail.com wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian -

 I'm doing the final verification of our fix, and was hoping that I
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds 
 r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix
 where we look to see that the network adapter itself is also enabled. 
 This
 is laid out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in
 question the dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless
 you understand ramifications.

 --
 You received this message because you are subscribed to the
 Google Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/**group**
 /puppet-users http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/**grou**
 ps/opt_out https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at http://groups.google.com/**group**
 /puppet-users http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/**grou**
 ps/opt_out https://groups.google.com/groups/opt_out.




 --
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.
 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users+unsubscr...@googlegroups.com.

 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Rob Reynolds
You should be able to run

facter --trace --debug


On Wed, Oct 2, 2013 at 5:18 PM, cko dert...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian -

 I'm doing the final verification of our fix, and was hoping that I could
 get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds r...@puppetlabs.comwrote:

 I would say with all of this in mind we move forward with a fix where we
 look to see that the network adapter itself is also enabled. This is laid
 out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.com wrote:

 Exchange DAG is essentially a cluster and the adapter in question the
 dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you
 understand ramifications.

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*

  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread cko
https://gist.github.com/anonymous/6814400


On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run 

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com javascript:wrote:

 Hi Ethan,

 what's the exact command that i would have to use? 


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian - 

 I'm doing the final verification of our fix, and was hoping that I could 
 get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix where 
 we look to see that the network adapter itself is also enabled. This is 
 laid out in the ticket that I noted earlier.
  

 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.com wrote:

  Exchange DAG is essentially a cluster and the adapter in question the 
 dag ip.

 My guess is the logic for adapters should be modded for when 
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you 
 understand ramifications.

 --
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 -- 
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
  
 -- 
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 -- 
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*
  
  -- 
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to puppet-users...@googlegroups.com javascript:.
 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
  

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Rob Reynolds
Was this the entire log (minus anything you feel sensitive)?


On Thu, Oct 3, 2013 at 1:15 PM, cko dert...@gmail.com wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian -

 I'm doing the final verification of our fix, and was hoping that I
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix
 where we look to see that the network adapter itself is also enabled. This
 is laid out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in question
 the dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you
 understand ramifications.

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group**/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**grou**ps/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group**/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**grou**ps/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.
 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Christian Koep
Yes, thats all i got from *facter --trace --debug*


On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds r...@puppetlabs.com wrote:

 Was this the entire log (minus anything you feel sensitive)?


 On Thu, Oct 3, 2013 at 1:15 PM, cko dert...@gmail.com wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian -

 I'm doing the final verification of our fix, and was hoping that I
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix
 where we look to see that the network adapter itself is also enabled. 
 This
 is laid out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in question
 the dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you
 understand ramifications.

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group**/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**grou**ps/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group**/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**grou**ps/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.
 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.

 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/_JSpNmSvg_I/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-03 Thread Rob Reynolds
This verifies for us that this is a gating issue.

Would you feel comfortable helping us verify that we've fixed this issue
for you?

https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47




On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep dert...@gmail.com wrote:

 Yes, thats all i got from *facter --trace --debug*


 On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds r...@puppetlabs.com wrote:

 Was this the entire log (minus anything you feel sensitive)?


 On Thu, Oct 3, 2013 at 1:15 PM, cko dert...@gmail.com wrote:

 https://gist.github.com/anonymous/6814400


 On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote:

 You should be able to run

 facter --trace --debug


 On Wed, Oct 2, 2013 at 5:18 PM, cko der...@gmail.com wrote:

 Hi Ethan,

 what's the exact command that i would have to use?


 On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian -

 I'm doing the final verification of our fix, and was hoping that I
 could get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds r...@puppetlabs.comwrote:

  I would say with all of this in mind we move forward with a fix
 where we look to see that the network adapter itself is also enabled. 
 This
 is laid out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comwrote:

  Exchange DAG is essentially a cluster and the adapter in question
 the dag ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless
 you understand ramifications.

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group**/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit https://groups.google.com/**grou**
 ps/opt_out https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it,
 send an email to puppet-users...@**googlegroups.**com.
 To post to this group, send email to puppet...@googlegroups.com.

 Visit this group at 
 http://groups.google.com/**group**/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**grou**ps/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 --
 Ethan Brown
 et...@puppetlabs.com
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users...@**googlegroups.com.
 To post to this group, send email to puppet...@googlegroups.com.
 Visit this group at 
 http://groups.google.com/**group/puppet-usershttp://groups.google.com/group/puppet-users
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

  --
 You received this message because you are subscribed to the Google
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to puppet-users+unsubscr...@googlegroups.com.

 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Puppet Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/puppet-users/_JSpNmSvg_I/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 puppet-users+unsubscr...@googlegroups.com.

 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 

Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-02 Thread Ethan Brown
Christian -

I'm doing the final verification of our fix, and was hoping that I could
get the output from Facter run by itself?



On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds r...@puppetlabs.com wrote:

 I would say with all of this in mind we move forward with a fix where we
 look to see that the network adapter itself is also enabled. This is laid
 out in the ticket that I noted earlier.


 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rismo...@gmail.com wrote:

 Exchange DAG is essentially a cluster and the adapter in question the dag
 ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you
 understand ramifications.

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
--
Ethan Brown
et...@puppetlabs.com
Software Engineer

*Join us at PuppetConf 2014, September 23-24 in San Francisco*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-10-02 Thread cko
Hi Ethan,

what's the exact command that i would have to use? 


On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote:

 Christian - 

 I'm doing the final verification of our fix, and was hoping that I could 
 get the output from Facter run by itself?



 On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds 
 r...@puppetlabs.comjavascript:
  wrote:

 I would say with all of this in mind we move forward with a fix where we 
 look to see that the network adapter itself is also enabled. This is laid 
 out in the ticket that I noted earlier.
  

 On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rism...@gmail.comjavascript:
  wrote:

 Exchange DAG is essentially a cluster and the adapter in question the 
 dag ip.

 My guess is the logic for adapters should be modded for when 
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you 
 understand ramifications.

 --
 You received this message because you are subscribed to the Google 
 Groups Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to puppet-users...@googlegroups.com javascript:.
 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 Rob Reynolds
 Developer, Puppet Labs

 Join us at PuppetConf 2014, September 23-24 in San Francisco
  
 -- 
 You received this message because you are subscribed to the Google Groups 
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to puppet-users...@googlegroups.com javascript:.
 To post to this group, send email to puppet...@googlegroups.comjavascript:
 .
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 -- 
 --
 Ethan Brown
 et...@puppetlabs.com javascript:
 Software Engineer

 *Join us at PuppetConf 2014, September 23-24 in San Francisco*
  

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers

2013-09-20 Thread Rob Reynolds
I would say with all of this in mind we move forward with a fix where we
look to see that the network adapter itself is also enabled. This is laid
out in the ticket that I noted earlier.


On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel rismo...@gmail.com wrote:

 Exchange DAG is essentially a cluster and the adapter in question the dag
 ip.

 My guess is the logic for adapters should be modded for when
 netconnectionid is not null.

 In general don't try to mess with hidden adapters on dags unless you
 understand ramifications.

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.