Issue #10955 has been updated by Jeff Sussna.
I am doing everything as a member of the Administrators group. Puppetmaster is running in vagrant box on the same machine, with port 8140 forwarded. If agent couldn't talk to master I'd expect to get error message, not hang. Note that hang means Ctl-C doesn't work in cmd window, have to close the window to abort. C:\Documents and Settings\<user>\.puppet\PuppetLabs\puppet\etcpuppet.conf has nothing in it except: [main] server = localhost Puppet apply and puppet agent emit nothing, even with --debug. Facter --debug emits: [0;32mFound no suitable resolves of 1 for arp [0m [0;32mvalue for arp is still nil [0m [0;32mNot an EC2 host [0m [0;32mFound no suitable resolves of 1 for xendomains [0m [0;32mvalue for xendomains is still nil [0m [0;32mFound no suitable resolves of 1 for selinux [0m [0;32mvalue for selinux is still nil [0m [0;32mFound no suitable resolves of 1 for selinux_config_mode [0m [0;32mvalue for selinux_config_mode is still nil [0m [0;32mFound no suitable resolves of 1 for vlans [0m [0;32mvalue for vlans is still nil [0m [0;32mFound no suitable resolves of 2 for lsbdistrelease [0m [0;32mvalue for lsbdistrelease is still nil [0m [0;32mFound no suitable resolves of 2 for lsbdistdescription [0m [0;32mvalue for lsbdistdescription is still nil [0m [0;32mvalue for sshecdsakey is still nil [0m [0;32mFound no suitable resolves of 1 for memorysize [0m [0;32mvalue for memorysize is still nil [0m [0;32mFound no suitable resolves of 1 for selinux [0m [0;32mvalue for selinux is still nil [0m [0;32mFound no suitable resolves of 1 for selinux_current_mode [0m [0;32mvalue for selinux_current_mode is still nil [0m [0;32mFound no suitable resolves of 1 for hardwareisa [0m [0;32mvalue for hardwareisa is still nil [0m [0;32mFound no suitable resolves of 1 for netmask [0m [0;32mvalue for netmask is still nil [0m [0;32mFound no suitable resolves of 2 for lsbrelease [0m [0;32mvalue for lsbrelease is still nil [0m [0;32mFound no suitable resolves of 1 for selinux [0m [0;32mvalue for selinux is still nil [0m [0;32mvalue for interfaces is still nil [0m [0;32mvalue for sshdsakey is still nil [0m [0;32mFound no suitable resolves of 2 for processor [0m [0;32mvalue for processor is still nil [0m [0;32mFound no suitable resolves of 1 for selinux [0m [0;32mvalue for selinux is still nil [0m [0;32mFound no suitable resolves of 1 for selinux_policyversion [0m [0;32mvalue for selinux_policyversion is still nil [0m [0;32mFound no suitable resolves of 2 for lsbdistcodename [0m [0;32mvalue for lsbdistcodename is still nil [0m [0;32mFound no suitable resolves of 2 for iphostnumber [0m [0;32mvalue for iphostnumber is still nil [0m [0;32mFound no suitable resolves of 2 for lsbdistid [0m [0;32mvalue for lsbdistid is still nil [0m [0;32mFound no suitable resolves of 1 for swapencrypted [0m [0;32mvalue for swapencrypted is still nil [0m ---------------------------------------- Bug #10955: Puppet agent hangs on Windows XP https://projects.puppetlabs.com/issues/10955 Author: Jeff Sussna Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Followed the Windows puppet agent install instructions (http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows) very carefully. Verified I'm running the correct version of ruby. All install steps completed without errors. Did install and am running as local account, not admin. Any puppet command (i.e., "puppet config print all") hangs. .puppet directory was not created. Tried creating it by hand, along with .puppet\Puppetlabs\puppet\etc and puppet.conf file. Not sure what needs to go in puppet.conf other than server=. OS is Windows XP SP3. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
