I''m having issues getting puppet to work properly on our servers. we have puppet allready running on our linux servers however are unable to have the puppet agent run on windows. the log displays only the following: Puppet (notice): Starting Puppet client version 2.7.11 Puppet (err): Could not run: fork() function is unimplemented on this machine The only modules the servers load is: node ''win2'' { include windows-admin } This is the the contents of the module: class windows-admin { user { "Administrator": ensure => present, password => ''w5&X341144!'' } This works properly if running it as a test and sets the password. As soon as you start the service and the log fills up with: Puppet (err): Could not run: fork() function is unimplemented on this machine Thanks, Igor -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Feb 27, 2012 at 9:29 AM, Igor <icherfas@gmail.com> wrote:> I''m having issues getting puppet to work properly on our servers. we > have puppet allready running on our linux servers however are unable > to have the puppet agent run on windows. > > the log displays only the following: > > Puppet (notice): Starting Puppet client version 2.7.11 > Puppet (err): Could not run: fork() function is unimplemented on this > machine > > The only modules the servers load is: > > > node ''win2'' { > include windows-admin > } > > > This is the the contents of the module: > > class windows-admin { > user { "Administrator": > ensure => present, > password => ''w5&X341144!'' > } > > This works properly if running it as a test and sets the password. As > soon as you start the service and the log fills up with: > Puppet (err): Could not run: fork() function is unimplemented on this > machine > >Igor, Are you running the Puppet agent as a windows service? If so, what is your configuration? Are you using a wrapper script? -Jeff McCune -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Yes, we are running it as a windows service. We are using nssm as a wrapper, here is how we created the service: nssm.exe install puppet-agent c:\ruby187\bin\puppet.bat agent -- logdest c:\puppet.log The puppet.bat is the default that the install script creates. Thanks, Igor On Feb 27, 12:48 pm, Jeff McCune <j...@puppetlabs.com> wrote:> On Mon, Feb 27, 2012 at 9:29 AM, Igor <icher...@gmail.com> wrote: > > I''m having issues getting puppet to work properly on our servers. we > > have puppet allready running on our linux servers however are unable > > to have the puppet agent run on windows. > > > the log displays only the following: > > > Puppet (notice): Starting Puppet client version 2.7.11 > > Puppet (err): Could not run: fork() function is unimplemented on this > > machine > > > The only modules the servers load is: > > > node ''win2'' { > > include windows-admin > > } > > > This is the the contents of the module: > > > class windows-admin { > > user { "Administrator": > > ensure => present, > > password => ''w5&X341144!'' > > } > > > This works properly if running it as a test and sets the password. As > > soon as you start the service and the log fills up with: > > Puppet (err): Could not run: fork() function is unimplemented on this > > machine > > Igor, > > Are you running the Puppet agent as a windows service? If so, what is your > configuration? Are you using a wrapper script? > > -Jeff McCune-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Igor, On Mon, Feb 27, 2012 at 12:54 PM, Igor <icherfas@gmail.com> wrote:> Yes, we are running it as a windows service. > > We are using nssm as a wrapper, here is how we created the service: > > nssm.exe install puppet-agent c:\ruby187\bin\puppet.bat agent -- > logdest c:\puppet.log >Can you set the trace[1] option in puppet.conf[2]. Restart the service, and reply with the backtrace? Thanks, Josh [1] http://docs.puppetlabs.com/references/stable/configuration.html#trace [2] http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows#Settings -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Here you go: Mon Feb 27 13:41:20 -0800 2012 Puppet (notice): Starting Puppet client version 2.7.11 Mon Feb 27 13:41:20 -0800 2012 Puppet (err): Could not run: fork() function is unimplemented on this machine Mon Feb 27 13:41:20 -0800 2012 Puppet (err): c:/Ruby187/bin/c:/Ruby187/ lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/(eval):2 c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/event-loop.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/daemon.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/ command_line.rb c:/Ruby187/bin/c:/Ruby187/bin/puppet Mon Feb 27 13:41:23 -0800 2012 Puppet (notice): Starting Puppet client version 2.7.11 Mon Feb 27 13:41:23 -0800 2012 Puppet (err): Could not run: fork() function is unimplemented on this machine Mon Feb 27 13:41:24 -0800 2012 Puppet (err): c:/Ruby187/bin/c:/Ruby187/ lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/signal-system.rb c:/Ruby187/bin/(eval):2 c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event- loop/event-loop.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/daemon.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/ command_line.rb c:/Ruby187/bin/c:/Ruby187/bin/puppet Thanks, Igor On Feb 27, 4:33 pm, Josh Cooper <j...@puppetlabs.com> wrote:> Hi Igor, > > On Mon, Feb 27, 2012 at 12:54 PM, Igor <icher...@gmail.com> wrote: > > Yes, we are running it as a windows service. > > > We are using nssm as a wrapper, here is how we created the service: > > > nssm.exe install puppet-agent c:\ruby187\bin\puppet.bat agent -- > > logdest c:\puppet.log > > Can you set the trace[1] option in puppet.conf[2]. Restart the service, and > reply with the backtrace? > > Thanks, > Josh > > [1]http://docs.puppetlabs.com/references/stable/configuration.html#trace > [2]http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows#Settings > -- > 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Igor, Are you using the ruby interpreter from rubyinstaller.org? Or cygwin? On Mon, Feb 27, 2012 at 1:43 PM, Igor <icherfas@gmail.com> wrote:> Here you go: > > Mon Feb 27 13:41:20 -0800 2012 Puppet (notice): Starting Puppet client > version 2.7.11 > Mon Feb 27 13:41:20 -0800 2012 Puppet (err): Could not run: fork() > function is unimplemented on this machine > Mon Feb 27 13:41:20 -0800 2012 Puppet (err): c:/Ruby187/bin/c:/Ruby187/ > lib/ruby/site_ruby/1.8/puppet/agent.rbc:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb> c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb > c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb > c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb >Something is wrong here. The path should be c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb. Also, the backtrace normally contains line numbers. How did you install ruby and puppet? Can you run the following: cd c:\Ruby187\bin ruby -v ruby -e "require ''puppet''; puts Puppet[:daemonize]" ruby -e "require ''puppet''; puts Puppet.features.microsoft_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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
We are using the ruby installer from the Puppet windows page: http://rubyforge.org/frs/download.php/74293/rubyinstaller-1.8.7-p334.exe http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows Here are the command you wanted me to run: C:\Ruby187\bin>ruby -v ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-mingw32] C:\Ruby187\bin>ruby -e "require ''puppet''; puts Puppet[:daemonize]" false C:\Ruby187\bin>ruby -e "require ''puppet''; puts Puppet.features.microsoft_windows?" true Thanks, Igor On Feb 27, 6:26 pm, Josh Cooper <j...@puppetlabs.com> wrote:> Hi Igor, > > Are you using the ruby interpreter from rubyinstaller.org? Or cygwin? > > On Mon, Feb 27, 2012 at 1:43 PM, Igor <icher...@gmail.com> wrote: > > Here you go: > > > Mon Feb 27 13:41:20 -0800 2012 Puppet (notice): Starting Puppet client > > version 2.7.11 > > Mon Feb 27 13:41:20 -0800 2012 Puppet (err): Could not run: fork() > > function is unimplemented on this machine > > Mon Feb 27 13:41:20 -0800 2012 Puppet (err): c:/Ruby187/bin/c:/Ruby187/ > > lib/ruby/site_ruby/1.8/puppet/agent.rb > > c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb > > > c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb > > c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb > > c:/Ruby187/bin/c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb > > Something is wrong here. The path should be > c:/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb. Also, the backtrace > normally contains line numbers. How did you install ruby and puppet? > > Can you run the following: > > cd c:\Ruby187\bin > ruby -v > ruby -e "require ''puppet''; puts Puppet[:daemonize]" > ruby -e "require ''puppet''; puts Puppet.features.microsoft_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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''m having the same issue. I''m new to puppet and have setup a linux puppet master server. I have successfully signed the cert from the windows computer. In fact, the windows agent was able to perform the actions once but now it can''t. I''m running puppet agent interactively from a command prompt (with elevated privileges). puppet agent --verbose --server master.puppet.xxxxxx.com --logdest c: \junk\puppetinfo_145.txt This may or may not have an impact. I''m connection the windows computer to the network through a wireless 4g network (clearwire) so there is not local DNS. I get my IP from clearwire. When I run facter is get unexpected results: facter hostname WN7X64-6MYJ5Q1 facter domain <<blank>> I have tracing turned on: notice: Starting Puppet client version 2.7.10 err: Could not run: fork() function is unimplemented on this machine err: C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb: 101:in `fork'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:101:in `run_in_fork''C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ agent.rb:45:in `run'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/ puppet/application.rb:172:in `call'' C:/Dev/tools/Ruby187/lib/ruby/ site_ruby/1.8/puppet/application.rb:172:in `controlled_run'' C:/Dev/ tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run'' C:/ Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:87:in `start'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event-loop/ signal-system.rb:95:i n `call'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ event-loop/signal-system.rb:95:in `__signal__'' C:/Dev/tools/Ruby187/ lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb: 95:in `each'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ external/event-loop/signal-system.rb:95:in `__signal__'' (eval):2:in `signal'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ event-loop/event-loop.rb:317:in `sound_alarm'' C:/Dev/tools/Ruby187/lib/ ruby/site_ruby/1.8/puppet/agent.rb:91:in `start'' C:/Dev/tools/Ruby187/ lib/ruby/site_ruby/1.8/puppet/daemon.rb:126:in `start'' C:/Dev/tools/ Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:347:in `main'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb:302:in `run_command'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/ 1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/Ruby187/lib/ruby/ site_ruby/1.8/puppet/application.rb:412:in `hook'' C:/Dev/tools/Ruby187/ lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/ Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:404:in `exit_on_fail'' C:/Dev/tools/R uby187/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/ Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb: 69:in `execute'' C:/Dev/tools/Ruby187/bin/puppet:4 On Feb 27, 11:48 am, Jeff McCune <j...@puppetlabs.com> wrote:> On Mon, Feb 27, 2012 at 9:29 AM, Igor <icher...@gmail.com> wrote: > > I''m having issues getting puppet to work properly on our servers. we > > have puppet allready running on our linux servers however are unable > > to have the puppet agent run on windows. > > > the log displays only the following: > > > Puppet (notice): Starting Puppet client version 2.7.11 > > Puppet (err): Could not run: fork() function is unimplemented on this > > machine > > > The only modules the servers load is: > > > node ''win2'' { > > include windows-admin > > } > > > This is the the contents of the module: > > > class windows-admin { > > user { "Administrator": > > ensure => present, > > password => ''w5&X341144!'' > > } > > > This works properly if running it as a test and sets the password. As > > soon as you start the service and the log fills up with: > > Puppet (err): Could not run: fork() function is unimplemented on this > > machine > > Igor, > > Are you running the Puppet agent as a windows service? If so, what is your > configuration? Are you using a wrapper script? > > -Jeff McCune-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Daniel, On Tue, Feb 28, 2012 at 11:58 AM, Daniel <wildahunden@gmail.com> wrote:> I''m having the same issue. I''m new to puppet and have setup a linux > puppet master server. I have successfully signed the cert from the > windows computer. In fact, the windows agent was able to perform the > actions once but now it can''t. > > I''m running puppet agent interactively from a command prompt (with > elevated privileges). > > puppet agent --verbose --server master.puppet.xxxxxx.com --logdest c: > \junk\puppetinfo_145.txt > > This may or may not have an impact. I''m connection the windows > computer to the network through a wireless 4g network (clearwire) so > there is not local DNS. I get my IP from clearwire. When I run > facter is get unexpected results: > > facter hostname > WN7X64-6MYJ5Q1 > > facter domain > <<blank>> >What is your primary dns suffix (try running ipconfig /all). This is likely https://projects.puppetlabs.com/issues/12864> I have tracing turned on: > > notice: Starting Puppet client version 2.7.10 > err: Could not run: fork() function is unimplemented on this machine > err: C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb: > 101:in `fork'' >This code only exists in master, not 2.7.x. I''m guessing there is something wrong with the code Brice added to apply catalogs in a separate process when run on Windows (see 6812ee9fc51f327f3a74fc6a6c0eefd9758d0134). Can you check that you installed puppet from the 2.7.x branch?> C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:101:in > `run_in_fork''C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ > agent.rb:45:in `run'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/ > puppet/application.rb:172:in `call'' C:/Dev/tools/Ruby187/lib/ruby/ > site_ruby/1.8/puppet/application.rb:172:in `controlled_run'' C:/Dev/ > tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run'' C:/ > Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:87:in `start'' > C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event-loop/ > signal-system.rb:95:i > n `call'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ > event-loop/signal-system.rb:95:in `__signal__'' C:/Dev/tools/Ruby187/ > lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb: > 95:in `each'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ > external/event-loop/signal-system.rb:95:in `__signal__'' (eval):2:in > `signal'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ > event-loop/event-loop.rb:317:in `sound_alarm'' C:/Dev/tools/Ruby187/lib/ > ruby/site_ruby/1.8/puppet/agent.rb:91:in `start'' C:/Dev/tools/Ruby187/ > lib/ruby/site_ruby/1.8/puppet/daemon.rb:126:in `start'' C:/Dev/tools/ > Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:347:in > `main'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ > agent.rb:302:in `run_command'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/ > 1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/Ruby187/lib/ruby/ > site_ruby/1.8/puppet/application.rb:412:in `hook'' C:/Dev/tools/Ruby187/ > lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/ > Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:404:in > `exit_on_fail'' C:/Dev/tools/R > uby187/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/ > Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb: > 69:in `execute'' C:/Dev/tools/Ruby187/bin/puppet:4 > > > > > On Feb 27, 11:48 am, Jeff McCune <j...@puppetlabs.com> wrote: > > On Mon, Feb 27, 2012 at 9:29 AM, Igor <icher...@gmail.com> wrote: > > > I''m having issues getting puppet to work properly on our servers. we > > > have puppet allready running on our linux servers however are unable > > > to have the puppet agent run on windows. > > > > > the log displays only the following: > > > > > Puppet (notice): Starting Puppet client version 2.7.11 > > > Puppet (err): Could not run: fork() function is unimplemented on this > > > machine > > > > > The only modules the servers load is: > > > > > node ''win2'' { > > > include windows-admin > > > } > > > > > This is the the contents of the module: > > > > > class windows-admin { > > > user { "Administrator": > > > ensure => present, > > > password => ''w5&X341144!'' > > > } > > > > > This works properly if running it as a test and sets the password. As > > > soon as you start the service and the log fills up with: > > > Puppet (err): Could not run: fork() function is unimplemented on this > > > machine > > > > Igor, > > > > Are you running the Puppet agent as a windows service? If so, what is > your > > configuration? Are you using a wrapper script? > > > > -Jeff McCune > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I setup puppet on the Windows servers that Igor has mentioned. As a temporary workaround, I''m just using the windows task scheduler to run this every 30 minutes... puppet agent --verbose --onetime --no-daemonize --logdest C: \puppet.log It''s certainly not a very elegant solution but it has at least allowed us to have puppet running on these machines for now. On Feb 28, 6:57 pm, Josh Cooper <j...@puppetlabs.com> wrote:> Hi Daniel, > > > > > > > > > > On Tue, Feb 28, 2012 at 11:58 AM, Daniel <wildahun...@gmail.com> wrote: > > I''m having the same issue. I''m new to puppet and have setup a linux > > puppet master server. I have successfully signed the cert from the > > windows computer. In fact, the windows agent was able to perform the > > actions once but now it can''t. > > > I''m running puppet agent interactively from a command prompt (with > > elevated privileges). > > > puppet agent --verbose --server master.puppet.xxxxxx.com --logdest c: > > \junk\puppetinfo_145.txt > > > This may or may not have an impact. I''m connection the windows > > computer to the network through a wireless 4g network (clearwire) so > > there is not local DNS. I get my IP from clearwire. When I run > > facter is get unexpected results: > > > facter hostname > > WN7X64-6MYJ5Q1 > > > facter domain > > <<blank>> > > What is your primary dns suffix (try running ipconfig /all). This is likelyhttps://projects.puppetlabs.com/issues/12864 > > > I have tracing turned on: > > > notice: Starting Puppet client version 2.7.10 > > err: Could not run: fork() function is unimplemented on this machine > > err: C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb: > > 101:in `fork'' > > This code only exists in master, not 2.7.x. I''m guessing there is something > wrong with the code Brice added to apply catalogs in a separate process > when run on Windows (see 6812ee9fc51f327f3a74fc6a6c0eefd9758d0134). Can you > check that you installed puppet from the 2.7.x branch? > > > > > > > > > > > C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:101:in > > `run_in_fork''C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ > > agent.rb:45:in `run'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/ > > puppet/application.rb:172:in `call'' C:/Dev/tools/Ruby187/lib/ruby/ > > site_ruby/1.8/puppet/application.rb:172:in `controlled_run'' C:/Dev/ > > tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run'' C:/ > > Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:87:in `start'' > > C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event-loop/ > > signal-system.rb:95:i > > n `call'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ > > event-loop/signal-system.rb:95:in `__signal__'' C:/Dev/tools/Ruby187/ > > lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb: > > 95:in `each'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ > > external/event-loop/signal-system.rb:95:in `__signal__'' (eval):2:in > > `signal'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ > > event-loop/event-loop.rb:317:in `sound_alarm'' C:/Dev/tools/Ruby187/lib/ > > ruby/site_ruby/1.8/puppet/agent.rb:91:in `start'' C:/Dev/tools/Ruby187/ > > lib/ruby/site_ruby/1.8/puppet/daemon.rb:126:in `start'' C:/Dev/tools/ > > Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:347:in > > `main'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ > > agent.rb:302:in `run_command'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/ > > 1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/Ruby187/lib/ruby/ > > site_ruby/1.8/puppet/application.rb:412:in `hook'' C:/Dev/tools/Ruby187/ > > lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/ > > Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:404:in > > `exit_on_fail'' C:/Dev/tools/R > > uby187/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/ > > Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb: > > 69:in `execute'' C:/Dev/tools/Ruby187/bin/puppet:4 > > > On Feb 27, 11:48 am, Jeff McCune <j...@puppetlabs.com> wrote: > > > On Mon, Feb 27, 2012 at 9:29 AM, Igor <icher...@gmail.com> wrote: > > > > I''m having issues getting puppet to work properly on our servers. we > > > > have puppet allready running on our linux servers however are unable > > > > to have the puppet agent run on windows. > > > > > the log displays only the following: > > > > > Puppet (notice): Starting Puppet client version 2.7.11 > > > > Puppet (err): Could not run: fork() function is unimplemented on this > > > > machine > > > > > The only modules the servers load is: > > > > > node ''win2'' { > > > > include windows-admin > > > > } > > > > > This is the the contents of the module: > > > > > class windows-admin { > > > > user { "Administrator": > > > > ensure => present, > > > > password => ''w5&X341144!'' > > > > } > > > > > This works properly if running it as a test and sets the password. As > > > > soon as you start the service and the log fills up with: > > > > Puppet (err): Could not run: fork() function is unimplemented on this > > > > machine > > > > Igor, > > > > Are you running the Puppet agent as a windows service? If so, what is > > your > > > configuration? Are you using a wrapper script? > > > > -Jeff McCune > > > -- > > 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+unsubscribe@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en. > > -- > 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Feb 28, 2012 at 3:57 PM, Josh Cooper <josh@puppetlabs.com> wrote:> This code only exists in master, not 2.7.x. I''m guessing there is > something wrong with the code Brice added to apply catalogs in a separate > process when run on Windows (see 6812ee9fc51f327f3a74fc6a6c0eefd9758d0134). > Can you check that you installed puppet from the 2.7.x branch? >It''s fairly easy to switch Puppet versions. You can grab the current state of our 2.7.x series from this URL: https://github.com/puppetlabs/puppet/zipball/2.7.x Then simply run ruby install.rb to install it. I also recommend removing C:/Ruby187/lib/ruby/site_ruby/1.8/puppet and C:/Ruby187/lib/ruby/site_ruby/1.8/puppet.rb to avoid issues with dynamically loading code from a different version of Puppet. Hope this helps, -- Jeff McCune -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I installed the latest rc from: puppetlabs-puppet-2.7.12rc1-7- g281901e.zip https://github.com/puppetlabs/puppet/zipball/2.7.x I no longer get the fork error. It connects to the master puppet server and runs the configuration. But, it gets a different error at the end. As the new error does not seem to be related to the original error, I''ll start a new discussion. Thank you for your help! On Feb 28, 5:57 pm, Josh Cooper <j...@puppetlabs.com> wrote:> Hi Daniel, > > > > > > > > > > On Tue, Feb 28, 2012 at 11:58 AM, Daniel <wildahun...@gmail.com> wrote: > > I''m having the same issue. I''m new to puppet and have setup a linux > > puppet master server. I have successfully signed the cert from the > > windows computer. In fact, the windows agent was able to perform the > > actions once but now it can''t. > > > I''m running puppet agent interactively from a command prompt (with > > elevated privileges). > > > puppet agent --verbose --server master.puppet.xxxxxx.com --logdest c: > > \junk\puppetinfo_145.txt > > > This may or may not have an impact. I''m connection the windows > > computer to the network through a wireless 4g network (clearwire) so > > there is not local DNS. I get my IP from clearwire. When I run > > facter is get unexpected results: > > > facter hostname > > WN7X64-6MYJ5Q1 > > > facter domain > > <<blank>> > > What is your primary dns suffix (try running ipconfig /all). This is likelyhttps://projects.puppetlabs.com/issues/12864 > > > I have tracing turned on: > > > notice: Starting Puppet client version 2.7.10 > > err: Could not run: fork() function is unimplemented on this machine > > err: C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb: > > 101:in `fork'' > > This code only exists in master, not 2.7.x. I''m guessing there is something > wrong with the code Brice added to apply catalogs in a separate process > when run on Windows (see 6812ee9fc51f327f3a74fc6a6c0eefd9758d0134). Can you > check that you installed puppet from the 2.7.x branch? > > > > > > > > > > > C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:101:in > > `run_in_fork''C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ > > agent.rb:45:in `run'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/ > > puppet/application.rb:172:in `call'' C:/Dev/tools/Ruby187/lib/ruby/ > > site_ruby/1.8/puppet/application.rb:172:in `controlled_run'' C:/Dev/ > > tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:43:in `run'' C:/ > > Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/agent.rb:87:in `start'' > > C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/event-loop/ > > signal-system.rb:95:i > > n `call'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ > > event-loop/signal-system.rb:95:in `__signal__'' C:/Dev/tools/Ruby187/ > > lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb: > > 95:in `each'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/ > > external/event-loop/signal-system.rb:95:in `__signal__'' (eval):2:in > > `signal'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/external/ > > event-loop/event-loop.rb:317:in `sound_alarm'' C:/Dev/tools/Ruby187/lib/ > > ruby/site_ruby/1.8/puppet/agent.rb:91:in `start'' C:/Dev/tools/Ruby187/ > > lib/ruby/site_ruby/1.8/puppet/daemon.rb:126:in `start'' C:/Dev/tools/ > > Ruby187/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:347:in > > `main'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/application/ > > agent.rb:302:in `run_command'' C:/Dev/tools/Ruby187/lib/ruby/site_ruby/ > > 1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/Ruby187/lib/ruby/ > > site_ruby/1.8/puppet/application.rb:412:in `hook'' C:/Dev/tools/Ruby187/ > > lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/Dev/tools/ > > Ruby187/lib/ruby/site_ruby/1.8/puppet/application.rb:404:in > > `exit_on_fail'' C:/Dev/tools/R > > uby187/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'' C:/ > > Dev/tools/Ruby187/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb: > > 69:in `execute'' C:/Dev/tools/Ruby187/bin/puppet:4 > > > On Feb 27, 11:48 am, Jeff McCune <j...@puppetlabs.com> wrote: > > > On Mon, Feb 27, 2012 at 9:29 AM, Igor <icher...@gmail.com> wrote: > > > > I''m having issues getting puppet to work properly on our servers. we > > > > have puppet allready running on our linux servers however are unable > > > > to have the puppet agent run on windows. > > > > > the log displays only the following: > > > > > Puppet (notice): Starting Puppet client version 2.7.11 > > > > Puppet (err): Could not run: fork() function is unimplemented on this > > > > machine > > > > > The only modules the servers load is: > > > > > node ''win2'' { > > > > include windows-admin > > > > } > > > > > This is the the contents of the module: > > > > > class windows-admin { > > > > user { "Administrator": > > > > ensure => present, > > > > password => ''w5&X341144!'' > > > > } > > > > > This works properly if running it as a test and sets the password. As > > > > soon as you start the service and the log fills up with: > > > > Puppet (err): Could not run: fork() function is unimplemented on this > > > > machine > > > > Igor, > > > > Are you running the Puppet agent as a windows service? If so, what is > > your > > > configuration? Are you using a wrapper script? > > > > -Jeff McCune > > > -- > > 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+unsubscribe@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en. > > -- > 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.