[Puppet Users] Puppet on windows ignoring puppet.conf

[Mattis Haase]

Hello,

we have been using puppet for unix machines for quite a while and it works 
fine.

I have installed the latest puppet-agent (1.4.1) on Windows Server 2012R2. 
The installation went fine and the communication between the puppetmaster 
and the client works.

However, it uses the production environment, ignoring the environment 
setting in:

c:\program files\puppet labs\puppet\etc\puppet.conf


It is worth noting that this folder did originally not exist. The folder 
for the conf files was:

c:\program files\puppet labs\puppet\puppet\conf


However, all documentation points torwards the first folder. I put the same 
puppet conf into these three folders:

c:\program files\puppet labs\puppet\puppet\conf
c:\program files\puppet labs\puppet\puppet\etc
c:\program files\puppet labs\puppet\etc


The contents of the file are this:

# This file can be used to override the default puppet settings.
# See the following links for more details on what settings are available:
# - 
https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html
# - 
https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html
# - 
https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html
# - https://docs.puppetlabs.com/puppet/latest/reference/configuration.html
[main]
server=puppetmaster.develop.local
environment=develop


However, it still tries to pull from the production environment.
 

puppet.bat agent --configprint environment
production


I restarted the service, to no avail. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d5550288-e96d-4990-a255-44ffd2eeb5f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet on Windows running in no daemon mode...how to handle required reboots?

[Rob Reynolds]

On Fri, Aug 22, 2014 at 10:38 AM, Charlie Baum 
wrote:

> Running Puppet on Windows 2008r2 and 2012 in no daemon mode for a few
> applications.  Issue we are having is some tools/apps such as .net 4.5 and
> some MSI files we are installing require a reboot.  In no daemon mode, when
> the system reboots and comes back up the puppet recipe doesn't continue
> where it left off, so you have to run the puppet command again to kick it
> off.  If there's a couple reboots, there are multiple interactions here.
>  If this is on 10 systems, it's a little ridiculous.
>
> Any idea how we can get around this?  How we can get the recipe to pick up
> where it left off?  Can't seem to find anything out there related to this
> issue.
>

Puppet does need to be kicked back off. The agent runs when the system is
booted, so it just picks back up and starts processing puppet again (the
whole idempotent catalog, the net affect is that it picks up where it left
off).

To achieve the same with a no daemon mode you need to set up something to
make puppet apply run when the box is first booted.  The least fancy way is
to just set up a script to run when the box is first turned on.  The harder
part is getting it to work without having to login. A scheduled task could
achieve this with the trigger "At startup"[1]. Be aware that networking may
or may not be available yet. Note that while "at startup" is a valid
trigger and it is in the win32-taskscheduler[2] gem version that we use, it
will likely not work with the scheduled_task resource[3] without changes to
validation of win32_taskscheduler[4] and other areas to allow for
at_startup to be considered a valid trigger schedule value.

[1] http://technet.microsoft.com/en-us/library/cc748841.aspx
[2]
https://github.com/djberg96/win32-taskscheduler/blob/win32-taskscheduler-0.2.2/lib/win32/taskscheduler.rb#L110
[3]
https://docs.puppetlabs.com/references/3.6.latest/type.html#scheduled_task-attribute-trigger
[4]
https://github.com/puppetlabs/puppet/blob/3.6.2/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb#L347-L348

>  --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/1bdf4074-61a7-4a1f-892e-61f2f75b74f1%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2014 , September
20-24 in San Francisco*
*Register by September 8th to take advantage of the Final Countdown

*
*--**save $149!*

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMJiBK5mRFUh3zwDXcymBRpZcExL%3DYNgZHNszLPBYJ8DLY5c%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet on Windows running in no daemon mode...how to handle required reboots?

[Charlie Baum]

Running Puppet on Windows 2008r2 and 2012 in no daemon mode for a few 
applications.  Issue we are having is some tools/apps such as .net 4.5 and 
some MSI files we are installing require a reboot.  In no daemon mode, when 
the system reboots and comes back up the puppet recipe doesn't continue 
where it left off, so you have to run the puppet command again to kick it 
off.  If there's a couple reboots, there are multiple interactions here. 
 If this is on 10 systems, it's a little ridiculous.

Any idea how we can get around this?  How we can get the recipe to pick up 
where it left off?  Can't seem to find anything out there related to this 
issue.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1bdf4074-61a7-4a1f-892e-61f2f75b74f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] [puppet on windows] notice: Run of Puppet configuration client already in progress; skipping

[sinc]

Hello,
I use puppet on windows, many servers works perfectly but I have19 servers 
in out of sync state... 
When i launch a puppet test on them, I have the following error message: 
notice: Run of Puppet configuration customer already in progress; skipping

I tried a puppet agent --enable then delete the file puppetdlock but it was 
not found. 
The client and server have the same version (2.7.20) 
The node OS is Windows Server 2003 SP2 

Do you have any ideas? 

Thanks a lot, 
sinc

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a421c35c-97b7-4e35-9a85-a08cca396efb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet on Windows (Package and File Dependencies)

[Rob Reynolds]

MSIs can be installed from a url which may help keep the packages off of
each individual box. This means they are installable from a file share as
well. I am not sure about FTP support with MSIs.

Note that MSIs, not exe installers are the ones that work in this way.
Those would need to be accessible (but might still work with a file share).
 I am not sure if this is desired for you or not.


On Thu, Mar 13, 2014 at 10:44 AM, Louis  wrote:

> I have several windows boxes as puppet agents and most of them install
> packages the following way..
>
>file{
>   ... make sure my .msi file is where i want
> }
>
>   package{
>... install the msi package from a local msi
>   }
>
> Now, as a general rule Puppet will make sure that the .msi package is
> always there but the question is... Do I really want the package to be
> sitting there (even when i have big msi packages) or maybe i just want the
> file to be there only if the Package is not installed.
>
> Couldn't find a way to do it with Notify/Subscribe since that is done for
> a different purpose. If the package resource type could support the url to
> download the package then i wouldn't have a whole bunch of installers
> sitting there locally.
>
> Wondering if someone has the same issue. Linux is a different story
> regarding Packages because they all depend on their Package Manager.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/ba5230e3-072a-4a85-942e-15a4df60c258%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rob Reynolds
Developer, Puppet Labs

*Join us at PuppetConf 2014, September 23-24 in San Francisco - *
http://bit.ly/pupconf14
Register now and save $350!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMJiBK4TqAa4ibtppSZULKzTfyMy4gDh3USkhAGW7wcxy_gfXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet on Windows (Package and File Dependencies)

[Louis]

I have several windows boxes as puppet agents and most of them install 
packages the following way..

   file{
  ... make sure my .msi file is where i want
}

  package{
   ... install the msi package from a local msi 
  }

Now, as a general rule Puppet will make sure that the .msi package is 
always there but the question is... Do I really want the package to be 
sitting there (even when i have big msi packages) or maybe i just want the 
file to be there only if the Package is not installed. 

Couldn't find a way to do it with Notify/Subscribe since that is done for a 
different purpose. If the package resource type could support the url to 
download the package then i wouldn't have a whole bunch of installers 
sitting there locally.

Wondering if someone has the same issue. Linux is a different story 
regarding Packages because they all depend on their Package Manager.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ba5230e3-072a-4a85-942e-15a4df60c258%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet on Windows 2003 Server > wrong IP via facter?

[Josh Cooper]

Hi Alan,

On Wed, Sep 19, 2012 at 8:31 AM, Alan Phillips  wrote:
> Hello!
>
> I'm just getting started working with Puppet and testing on a Windows 2003
> server. When I run facter on this server it returns a wrong value for the
> ipaddress (should be 10.10.0.203, but facter sets ipaddress=10.0.0.203). As
> you can see from the following ipconfig output, facter is looking at the
> TELECOM Ethernet adapter instead of the adapter used for the local domain
> (QALAB). Any work-around for this situation?
>
> C:\Documents and Settings\Administrator>ipconfig
>
> Windows IP Configuration
>
> Ethernet adapter QALAB 10.10.0.203:
>
>Connection-specific DNS Suffix  . :
>IP Address. . . . . . . . . . . . : 10.10.0.203
>Subnet Mask . . . . . . . . . . . : 255.255.254.0
>Default Gateway . . . . . . . . . : 10.10.0.1
>
> Ethernet adapter TELECOM 10.0.0.203:
>
>Connection-specific DNS Suffix  . :
>IP Address. . . . . . . . . . . . : 10.0.0.203
>Subnet Mask . . . . . . . . . . . : 255.255.255.0
>Default Gateway . . . . . . . . . :
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/XqsWrS-vLHUJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

Facter (on all platforms) doesn't handle multiple interfaces very
well. The logic is typically pick the ipaddress from the "first"
interface. See http://projects.puppetlabs.com/issues/5816

This code is undergoing some changes. See
http://projects.puppetlabs.com/issues/1346 and
https://github.com/puppetlabs/facter/pull/267

On Windows the current logic is:

require 'socket'
IPSocket.getaddress(Socket.gethostname)

I'm not sure why it does this to be honest. I would have expected it
to use WMI to only report on interfaces that have IP enabled,
something like:

wmic nicconfig where (IPEnabled = "true") get IPAddress

Or using netsh:

netsh.exe interface ip show ipaddresses 10

where 10 is my interface index for my "Local Area Connection" interface

Note facter does, or at least should be, reporting on the ipaddress
associated with each interface, downcased and with underscores. In my
case:

ipaddress_local_area_connection => 172.16.138.231
ipaddress_loopback_pseudo_interface_1 => 127.0.0.1

Josh

-- 
Josh Cooper
Developer, Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet on Windows 2003 Server > wrong IP via facter?

[Alan Phillips]

Hello!

I'm just getting started working with Puppet and testing on a Windows 2003 
server. When I run facter on this server it returns a wrong value for the 
ipaddress (should be 10.10.0.203, but facter sets ipaddress=10.0.0.203). As 
you can see from the following ipconfig output, facter is looking at the 
TELECOM Ethernet adapter instead of the adapter used for the local domain 
(QALAB). Any work-around for this situation?

C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration

Ethernet adapter QALAB 10.10.0.203:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 10.10.0.203
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   Default Gateway . . . . . . . . . : 10.10.0.1

Ethernet adapter TELECOM 10.0.0.203:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 10.0.0.203
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/XqsWrS-vLHUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on Windows: Avoid download msi files if they aren't going to be installed

[tiochan]

Jeff, thank for your reply.


Really puppet downloads the file only once, this is not in fact a problem.
I re-made the previous code to simplify it:

class 7Zip() {

include software_dir

file { 'C:\\SOFTWARE\\7z920.msi':
source  => 'puppet://puppet.upc.edu/modules/windows/7z920.msi',
}

package { '7-zip 9.20':
ensure => installed,
provider => 'msi',
source => 'C:\\SOFTWARE\\7z920.msi',
}
}

I can see that if the msi has been installed (by puppet), puppet will not 
try to install again, this is correct. But always, if it has been installed 
or not, the file C:\\SOFTWARE\\7z920.msi is downloaded.

A band of having a software repository mounted as a mapped drive... Is 
possible to avoid that the msi file to being downloaded if it is not going 
to be installed?



Thanks again.




-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/4y1VTSJ2QFsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on Windows: Avoid download msi files if they aren't going to be installed

[Jeff McCune]

On Thu, May 24, 2012 at 6:06 AM, tiochan  wrote:

> Hi all!
>
> I'm new on puppet, and I making my firsts classes.
>

Welcome!


> I have defined an example class to install 7Zip on Windows servers, it
> runs right, but I would like to improve it.
> The problem is that each time that I execute the "puppet agent --test" it
> downloads the 7zip.msi file, although it is really installed.
>

When using a file resource, Puppet should only transfer the file if there
is a mis-match between the local file and the copy on the puppet master.

Could you paste the output of puppet agent --test so we can see why the
file is being transfered more than once?  Do you happen to be removing the
MSI from C:\Software\ between puppet runs?  If so, Puppet will just put the
file right back in place.


> So, my question is:
> Is possible to avoid the download of the associated source file, I there
> is no need to install it?
>
> This is the code:
>
>
> class software_dir {
>
> file { 'SOFTWARE_DIR':
> path => 'C:\\SOFTWARE',
> ensure => directory,
> }
> }
>
> class 7Zip() {
>
> include software_dir
>
> $7Zip_source = 'puppet://puppet.upc.edu/modules/windows/7z920.msi'
> $7Zip_path = 'C:\\SOFTWARE\\7z920.msi'
> $7Zip_package_name = '7-zip 9.20'
>
> file { $7Zip_path:
> source  => $7Zip_source;
> }
>
> package { $7Zip_package_name:
> ensure => installed,
> provider => 'msi',
> source => File[$7Zip_path],


I think this line above should be source => "${7Zip_path}"  It shouldn't
contain a reference to the _resource_ File[$7Zip_path] but instead simply
the string that contains the path.

I'm not sure this is actually the problem though.  I think the output of
puppet agent --test will help diagnose this further.

-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet on Windows: Avoid download msi files if they aren't going to be installed

[tiochan]

Hi all!

I'm new on puppet, and I making my firsts classes.

I have defined an example class to install 7Zip on Windows servers, it runs 
right, but I would like to improve it.
The problem is that each time that I execute the "puppet agent --test" it 
downloads the 7zip.msi file, although it is really installed.

So, my question is:
Is possible to avoid the download of the associated source file, I there is 
no need to install it?

This is the code:


class software_dir {

file { 'SOFTWARE_DIR':
path => 'C:\\SOFTWARE',
ensure => directory,
}
}

class 7Zip() {

include software_dir

$7Zip_source = 'puppet://puppet.upc.edu/modules/windows/7z920.msi'
$7Zip_path = 'C:\\SOFTWARE\\7z920.msi'
$7Zip_package_name = '7-zip 9.20'

file { $7Zip_path:
source  => $7Zip_source;
}

package { $7Zip_package_name:
ensure => installed,
provider => 'msi',
source => File[$7Zip_path],
}
}

Thanks in advance.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/BO6yk8wHFasJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on Windows

[Josh Cooper]

Hi Jay,

On Thu, Feb 16, 2012 at 6:14 AM, Jay Ze wrote:

> Hi,
>
> I want to run Puppet on a Windows 2003 Server. I already have a
> working Puppetmaster (Scientific Linux).
>
> I installed Puppet on Windows like shown here:
> http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows
>
> This worked very well.
>

Great to hear.


> notice: Ignoring --listen on onetime run
> info: Retrieving plugin
> err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
> PuppetLabs/p
> uppet/var/lib]: Failed to generate additional resources using
> 'eval_generate: Co
> uld not intern_multiple from pson: Paths must be fully qualified
> err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
> PuppetLabs/p
> uppet/var/lib]: Could not evaluate: Could not intern from pson: Paths
> must be fu
> lly qualified Could not retrieve file metadata for puppet://
> foreman.id.dvag.com/
> plugins: Could not intern from pson: Paths must be fully qualified
>

This is https://projects.puppetlabs.com/issues/11408#note-32

It will be fixed shortly.


> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: PGError
> : ERROR:  invalid byte sequence for encoding "UTF8": 0xe46973
> : INSERT INTO "fact_values" ("value", "host_id", "created_at",
> "fact_name_id", "
> updated_at") VALUES ('Mitteleuropõische Zeit   ', 88, '2012-02-16
> 15:13:29.29309
> 9', 28, '2012-02-16 15:13:29.293099') RETURNING "id"


Somewhere between facter gathering the hostname and the hostname being
inserted into the database, there is a problem with how we are handling
UTF8 encoding. The text 'Mitteleuropõische Zeit' should be UTF8 encoded as
'4D 69 74 74 65 6C 65 75 72 6F 70 C3 B5 69 73 63 68 65 20 5A 65 69 74 20'
(in hex). The sequence 'e4 69 73' is most definitely an illegal UTF8
sequence.

Can you file a ticket against puppet?

Thanks,
Josh

-- 
Josh Cooper
Developer, Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet on Windows

[Jay Ze]

Hi,

I want to run Puppet on a Windows 2003 Server. I already have a
working Puppetmaster (Scientific Linux).

I installed Puppet on Windows like shown here:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows

This worked very well.

But when I want to run puppet.

puppet agent --test --debug

I get the following output: (I already tried different ruby and puppet
versions without success.)

notice: Ignoring --listen on onetime run
info: Retrieving plugin
err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
PuppetLabs/p
uppet/var/lib]: Failed to generate additional resources using
'eval_generate: Co
uld not intern_multiple from pson: Paths must be fully qualified
err: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
PuppetLabs/p
uppet/var/lib]: Could not evaluate: Could not intern from pson: Paths
must be fu
lly qualified Could not retrieve file metadata for puppet://foreman.id.dvag.com/
plugins: Could not intern from pson: Paths must be fully qualified
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: PGError
: ERROR:  invalid byte sequence for encoding "UTF8": 0xe46973
: INSERT INTO "fact_values" ("value", "host_id", "created_at",
"fact_name_id", "
updated_at") VALUES ('Mitteleuropõische Zeit   ', 88, '2012-02-16
15:13:29.29309
9', 28, '2012-02-16 15:13:29.293099') RETURNING "id"
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
notice: /File[C:/Dokumente und Einstellungen/All Users/Anwendungsdaten/
PuppetLab
s/puppet/var/state/last_run_summary.yaml]/content:




Can anybody here help me out?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on Windows - client installer?

[Josh Cooper]

On Wed, Jan 18, 2012 at 5:54 AM, jmp242  wrote:

> Is this the case, or am I missing where the installer is? Is there any

thought to creating a msi / exe installer in the future that would
> have puppet be self contained


Funny you should ask: https://projects.puppetlabs.com/issues/11205. We are
working on an MSI installed containing everything you need to install
puppet, facter, ruby, gems.


> and run a service?
>

This is something we are not planning on doing, partly because of the issue
with long running ruby processes, memory usage, etc. Instead we were
looking to use scheduled tasks to run puppet on a specified interval. It
does mean you couldn't `puppet kick` these agents. Would that work in your
environment?

Josh

-- 
Josh Cooper
Developer, Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet on Windows - client installer?

[jmp242]

I've been watching Puppet on Windows and may be interested in trying
it out - our Linux team is already working with it in a pilot... The
issue I see is it doesn't seem to have a msi or exe I could install on
client computers, instead it looks like it'd need a ruby environment
installed to get started (if I understand correctly)...

Is this the case, or am I missing where the installer is? Is there any
thought to creating a msi / exe installer in the future that would
have puppet be self contained and run a service?

Thank...

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on windows: File resource problem

[Mohamed Lrhazi]

One odd thing is that setting "show_diff=false" in puppet.conf, in
"agent" stanza seems to be ignored, I get the error still.

I am not a Windows guy, but I installed GNU diff and it seems like it
could be pretty straightforward to deploy:

- Get installer : http://gnuwin32.sourceforge.net/downlinks/diffutils.php
- Run it: C:\Temp\diffutils-2.8.7-1.exe /silent
- Add "diff' to puppet.conf:
diff = "C:\Program Files\GnuWin32\bin\diff"

et voila.

Thanks,
Mohamed.

On Sun, Nov 20, 2011 at 7:21 PM, Josh Cooper  wrote:
> On Sat, Nov 19, 2011 at 6:35 PM, Mohamed Lrhazi  wrote:
>>
>> I should note that "--test" enables "--show_diff", even if you add
>> "--show_diff false" to the command line... took me a while to figure
>> that out!
>>
>
> I was hoping to be able to use fc.exe (file compare) on Windows in lieu of
> diff, but it doesn't work so well. If you know of another utility that comes
> pre-installed with Windows that can do diffs, I'd love to hear about it.
> Otherwise, we'll have to set show_diff to false by default on Windows.
> Thanks,
> Josh
> --
> Josh Cooper
> Developer, Puppet Labs
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on windows: File resource problem

[Josh Cooper]

On Sat, Nov 19, 2011 at 6:35 PM, Mohamed Lrhazi  wrote:

> I should note that "--test" enables "--show_diff", even if you add
> "--show_diff false" to the command line... took me a while to figure
> that out!
>
>
I was hoping to be able to use fc.exe (file compare) on Windows in lieu of
diff, but it doesn't work so well. If you know of another utility that
comes pre-installed with Windows that can do diffs, I'd love to hear about
it. Otherwise, we'll have to set show_diff to false by default on Windows.

Thanks,
Josh
-- 
Josh Cooper
Developer, Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on windows: File resource problem

[Mohamed Lrhazi]

I should note that "--test" enables "--show_diff", even if you add
"--show_diff false" to the command line... took me a while to figure
that out!



On Fri, Nov 18, 2011 at 5:13 PM, Josh Cooper  wrote:
> Hi Mohamed,
> This is issue https://projects.puppetlabs.com/issues/10417 Windows doesn't
> have a 'diff.exe' command by default.
> You can work around this by setting show_diff = false or by specifying
> appropriate values for 'diff' and 'diff_args'
> Josh
>
> On Fri, Nov 18, 2011 at 1:42 PM, Mohamed Lrhazi  wrote:
>>
>> Anybody knows what this error, bellow, means, the target file,
>> C:/Splunk/etc/system/local/inputs.conf, does exist.
>> sometimes, if I delete the file, it does actually create it, but never
>> update it if it exists and changed...
>>
>> The resource is defined as:
>>
>>
>>
>>     file { "splunk_inputs":        owner   => SYSTEM,        group
>> => SYSTEM,        mode    => 664,        require =>
>> Exec["install_splunk"],        notify => Service["splunk"],
>> path => "$splunk_home\\etc\\system\\local\\inputs.conf",
>> content => template("gu_splunk/inputs.conf.windows.erb"),    }
>> debug: /Stage[main]/Gu_splunk::Windows/File[splunk_inputs]/content:
>> Executing 'diff -u C:/Splunk/etc/system/local/inputs.conf
>> C:/Users/ml623/AppData/Local/Temp/
>> puppet-file2018-3304-81qt4z-0'
>>
>> C:/Ruby187/lib/ruby/gems/1.8/gems/win32-process-0.6.5/lib/win32/process.rb:889:in
>> `create'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:336:in `execute_windows'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:374:in `execute'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/diff.rb:12:in `diff'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:107:in
>> `insync?'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:152:in
>> `write_temporarily'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:106:in
>> `insync?'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/property.rb:162:in `safe_insync?'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:61:in
>> `perform_changes'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
>> `each'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
>> `perform_changes'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:133:in
>> `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:49:in `apply'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:84:in
>> `eval_resource'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:476:in `thinmark'
>> C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:475:in `thinmark'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:351:in `traverse'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:99:in `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:141:in
>> `apply'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:121:in
>> `retrieve_and_apply_catalog'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:180:in `benchmark'
>> C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:179:in `benchmark'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:120:in
>> `retrieve_and_apply_catalog'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:151:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
>> C:/Ruby187/lib/ruby/1.8/sync.rb:230:in `synchronize'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `call'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in
>> `controlled_run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:336:in
>> `onetime'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:310:in
>> `run_command'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in `hook'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:401:in
>> `exit_on_fail'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in
>> `execute'
>> C:/Ruby187/bin/puppet:4
>> err: /Stage[main]/Gu_splunk::Windows/File[splunk_in

Re: [Puppet Users] Puppet on windows: File resource problem

[Mohamed Lrhazi]

Thanks a lot Josh.

On Fri, Nov 18, 2011 at 5:13 PM, Josh Cooper  wrote:
> Hi Mohamed,
> This is issue https://projects.puppetlabs.com/issues/10417 Windows doesn't
> have a 'diff.exe' command by default.
> You can work around this by setting show_diff = false or by specifying
> appropriate values for 'diff' and 'diff_args'
> Josh
>
> On Fri, Nov 18, 2011 at 1:42 PM, Mohamed Lrhazi  wrote:
>>
>> Anybody knows what this error, bellow, means, the target file,
>> C:/Splunk/etc/system/local/inputs.conf, does exist.
>> sometimes, if I delete the file, it does actually create it, but never
>> update it if it exists and changed...
>>
>> The resource is defined as:
>>
>>
>>
>>     file { "splunk_inputs":        owner   => SYSTEM,        group
>> => SYSTEM,        mode    => 664,        require =>
>> Exec["install_splunk"],        notify => Service["splunk"],
>> path => "$splunk_home\\etc\\system\\local\\inputs.conf",
>> content => template("gu_splunk/inputs.conf.windows.erb"),    }
>> debug: /Stage[main]/Gu_splunk::Windows/File[splunk_inputs]/content:
>> Executing 'diff -u C:/Splunk/etc/system/local/inputs.conf
>> C:/Users/ml623/AppData/Local/Temp/
>> puppet-file2018-3304-81qt4z-0'
>>
>> C:/Ruby187/lib/ruby/gems/1.8/gems/win32-process-0.6.5/lib/win32/process.rb:889:in
>> `create'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:336:in `execute_windows'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:374:in `execute'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/diff.rb:12:in `diff'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:107:in
>> `insync?'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:152:in
>> `write_temporarily'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:106:in
>> `insync?'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/property.rb:162:in `safe_insync?'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:61:in
>> `perform_changes'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
>> `each'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
>> `perform_changes'
>>
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:133:in
>> `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:49:in `apply'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:84:in
>> `eval_resource'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:476:in `thinmark'
>> C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:475:in `thinmark'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:351:in `traverse'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:99:in `evaluate'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:141:in
>> `apply'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:121:in
>> `retrieve_and_apply_catalog'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:180:in `benchmark'
>> C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:179:in `benchmark'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:120:in
>> `retrieve_and_apply_catalog'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:151:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
>> C:/Ruby187/lib/ruby/1.8/sync.rb:230:in `synchronize'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `call'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in
>> `controlled_run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:336:in
>> `onetime'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:310:in
>> `run_command'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in `hook'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:401:in
>> `exit_on_fail'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
>> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in
>> `execute'
>> C:/Ruby187/bin/puppet:4
>> err: /Stage[main]/Gu_splunk::Windows/File[splunk_inputs]: Could not
>> evaluate: CreateProcess() failed: The system cannot find the file
>> specified.
>> notice: /Stage[main]/Gu_sp

Re: [Puppet Users] Puppet on windows: File resource problem

[Josh Cooper]

Hi Mohamed,

This is issue https://projects.puppetlabs.com/issues/10417 Windows doesn't
have a 'diff.exe' command by default.

You can work around this by setting show_diff = false or by specifying
appropriate values for 'diff' and 'diff_args'

Josh

On Fri, Nov 18, 2011 at 1:42 PM, Mohamed Lrhazi  wrote:

> Anybody knows what this error, bellow, means, the target file,
> C:/Splunk/etc/system/local/inputs.conf, does exist.
> sometimes, if I delete the file, it does actually create it, but never
> update it if it exists and changed...
>
> The resource is defined as:
>
>
>
> file { "splunk_inputs":owner   => SYSTEM,group
> => SYSTEM,mode=> 664,require =>
> Exec["install_splunk"],notify => Service["splunk"],
> path => "$splunk_home\\etc\\system\\local\\inputs.conf",
> content => template("gu_splunk/inputs.conf.windows.erb"),}
> debug: /Stage[main]/Gu_splunk::Windows/File[splunk_inputs]/content:
> Executing 'diff -u C:/Splunk/etc/system/local/inputs.conf
> C:/Users/ml623/AppData/Local/Temp/
> puppet-file2018-3304-81qt4z-0'
>
> C:/Ruby187/lib/ruby/gems/1.8/gems/win32-process-0.6.5/lib/win32/process.rb:889:in
> `create'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:336:in `execute_windows'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:374:in `execute'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/diff.rb:12:in `diff'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:107:in
> `insync?'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:152:in
> `write_temporarily'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:106:in
> `insync?'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/property.rb:162:in `safe_insync?'
>
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:61:in
> `perform_changes'
>
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
> `each'
>
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
> `perform_changes'
>
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:133:in
> `evaluate'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:49:in `apply'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:84:in
> `eval_resource'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:476:in `thinmark'
> C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:475:in `thinmark'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:351:in `traverse'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:99:in `evaluate'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:141:in `apply'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:121:in
> `retrieve_and_apply_catalog'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:180:in `benchmark'
> C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:179:in `benchmark'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:120:in
> `retrieve_and_apply_catalog'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:151:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
> C:/Ruby187/lib/ruby/1.8/sync.rb:230:in `synchronize'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `call'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in
> `controlled_run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:336:in
> `onetime'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:310:in
> `run_command'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in `hook'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:401:in
> `exit_on_fail'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
> C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in
> `execute'
> C:/Ruby187/bin/puppet:4
> err: /Stage[main]/Gu_splunk::Windows/File[splunk_inputs]: Could not
> evaluate: CreateProcess() failed: The system cannot find the file
> specified.
> notice: /Stage[main]/Gu_splunk::Windows/Service[splunk]: Dependency
> File[splunk_inputs] has failures: true
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet User

[Puppet Users] Puppet on windows: File resource problem

[Mohamed Lrhazi]

Anybody knows what this error, bellow, means, the target file,
C:/Splunk/etc/system/local/inputs.conf, does exist.
sometimes, if I delete the file, it does actually create it, but never
update it if it exists and changed...

The resource is defined as:



    file { "splunk_inputs":        owner   => SYSTEM,        group
=> SYSTEM,        mode    => 664,        require =>
Exec["install_splunk"],        notify => Service["splunk"],
path => "$splunk_home\\etc\\system\\local\\inputs.conf",
content => template("gu_splunk/inputs.conf.windows.erb"),    }
debug: /Stage[main]/Gu_splunk::Windows/File[splunk_inputs]/content:
Executing 'diff -u C:/Splunk/etc/system/local/inputs.conf
C:/Users/ml623/AppData/Local/Temp/
puppet-file2018-3304-81qt4z-0'
C:/Ruby187/lib/ruby/gems/1.8/gems/win32-process-0.6.5/lib/win32/process.rb:889:in
`create'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:336:in `execute_windows'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:374:in `execute'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/diff.rb:12:in `diff'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:107:in `insync?'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:152:in
`write_temporarily'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb:106:in `insync?'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/property.rb:162:in `safe_insync?'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:61:in
`perform_changes'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
`each'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:60:in
`perform_changes'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction/resource_harness.rb:133:in
`evaluate'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:49:in `apply'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:84:in `eval_resource'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:476:in `thinmark'
C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:475:in `thinmark'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:103:in `evaluate'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:351:in `traverse'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/transaction.rb:99:in `evaluate'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:141:in `apply'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:121:in
`retrieve_and_apply_catalog'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:180:in `benchmark'
C:/Ruby187/lib/ruby/1.8/benchmark.rb:308:in `realtime'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util.rb:179:in `benchmark'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:120:in
`retrieve_and_apply_catalog'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/configurer.rb:151:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
C:/Ruby187/lib/ruby/1.8/sync.rb:230:in `synchronize'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `call'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `controlled_run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:336:in `onetime'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:310:in
`run_command'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in `hook'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:401:in `exit_on_fail'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
C:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute'
C:/Ruby187/bin/puppet:4
err: /Stage[main]/Gu_splunk::Windows/File[splunk_inputs]: Could not
evaluate: CreateProcess() failed: The system cannot find the file
specified.
notice: /Stage[main]/Gu_splunk::Windows/Service[splunk]: Dependency
File[splunk_inputs] has failures: true

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet on Windows

[Sandor Szuecs]

On Oct 26, 2010, at 8:51 PM, Kikanny wrote:

> Hi. I know that puppet for windows is in its basic stages but I've
> been screwing around with it. I can get facter working. However one
> error that it spits out is that: "Could not retrieve puppetversion:
> Cannot determine basic system flavour."
> 
> When I try to run puppet, I get an error saying "ruby: No such file or
> directory -- bin/puppetd (LoadError)"

This sounds to me like a ruby GEMPATH issue.
Try to run puppet using the ruby interpreter directly.
ruby -I/path/to/dir-with-puppet.rb/ puppet 

If this works you should set the GEMPATH env variable.

> Was wondering if anyone here has succeeded in getting puppet installed
> on Windows? I've been following this document:
> http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows. Thanks!

I don't know but would like to read about this, too.

All the best, Sandor Szücs
--



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet on Windows

[Kikanny]

Hi. I know that puppet for windows is in its basic stages but I've
been screwing around with it. I can get facter working. However one
error that it spits out is that: "Could not retrieve puppetversion:
Cannot determine basic system flavour."

When I try to run puppet, I get an error saying "ruby: No such file or
directory -- bin/puppetd (LoadError)"

Was wondering if anyone here has succeeded in getting puppet installed
on Windows? I've been following this document:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows. Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppet on windows.

[Sukh Khehra]

Is anyone running puppet on windows? 

 

I attempted to use the instructions at
http://reductivelabs.com/trac/puppet/wiki/PuppetWindows on my windows xp
machine but ran into the following error:

 

H:\>puppetd -tv

C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require': no such file to load -- syslog (

LoadError)

from
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/util/log.rb:1

from
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'

from
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/util/logging.rb:
2

from
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'

from
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/util.rb:456

 ... 7 levels...

from
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/bin/puppetd:158

from C:/Ruby/bin/puppetd:19:in `load'

from C:/Ruby/bin/puppetd:19

 

 

I created an empty syslog.rb file in the lib directory and got past the
above error but now get this:

 

C:\>puppetd -tv --server admin1016.us.proofpoint.com

The system cannot find the path specified.

C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/external/event-l
oop/event-loop.rb:78:in `initialize': uninitiali

zed constant Fcntl::F_SETFD (NameError)

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/external/event-l
oop/event-loop.rb:31:in `new'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/external/event-l
oop/event-loop.rb:31:in `default'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/external/event-l
oop/event-loop.rb:35:in `current'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/external/event-l
oop/event-loop.rb:285:in `initializ

e'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/util/settings.rb
:559:in `new'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/util/settings.rb
:559:in `set_filetimeout_timer'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/util/settings.rb
:323:in `parse'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/application.rb:2
15:in `run'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/application.rb:3
06:in `exit_on_fail'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/lib/puppet/application.rb:2
15:in `run'

from
C:/Ruby/lib/ruby/gems/1.8/gems/puppet-0.25.3/bin/puppetd:159

from C:/Ruby/bin/puppetd:19:in `load'

from C:/Ruby/bin/puppetd:19

 

 

Anyone gotten this to work? I am not a developer but if anyone is doing
development work on getting puppet to work on windows, I wouldn't mind
helping with the testing.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet on Windows?

[li...@truthisfreedom.org.uk]

Hi All,

I notice from http://reductivelabs.com/trac/puppet/wiki/PuppetWindows 
that puppet will be able to run on windows as of 0.26.0.

The document only really talks about managing users, are there plans to 
expand this to other things, or are there other functions that are 
enabled already...or should I just read the source code and find out? :P

I'm specifically thinking about management of IIS configs etc.

Thanks in advance,

M.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] puppet on windows - installation problems

[Grzegorz Marszałek]

Hello!

I've just tried to install puppet 0.25rc1 (from source) on windows. I  
have three problems:
* install.rb script tries to create files puppetca, puppetd, puppetqd,  
puppetrun in c:\ruby\sbin (no such dir in ruby installation) - small  
one :)
* puppet cannot start - it tires to require syslog, which is not  
available (easy to fix)
* then I stuck with this:


C:/Ruby/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event- 
loop.rb:78:in `i
nitialize': uninitialized constant Fcntl::F_SETFD (NameError)
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/external/event- 
loop/event-loo
p.rb:31:in `new'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/external/event- 
loop/event-loo
p.rb:31:in `default'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/external/event- 
loop/event-loo
p.rb:35:in `current'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/external/event- 
loop/event-loo
p.rb:285:in `initialize'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: 
532:in `new'

 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: 
532:in `set_
filetimeout_timer'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: 
314:in `pars
e'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/application.rb: 
215:in `run'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/application.rb: 
306:in `exit_o
n_fail'
 from C:/Ruby/lib/ruby/site_ruby/1.8/puppet/application.rb: 
215:in `run'
 from C:/Ruby/bin/puppet:71 

---
Grzegorz Marszałek
gr...@post.pl



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---