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+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
