[Puppet Users] Puppet apply hangs when trying to use puppet.conf manifest attribute
Hi, I've been trying to use puppet apply with no manifest argument, so that it uses the manifest defined on my environment in my puppet.conf. For my suprise, it didn't work. I simply don't understand why the modulepath works and the manifest doesn't.. Well, on my research I found this issue: https://projects.puppetlabs.com/issues/10538. Is there any way that this can get looked up again? For now, I've been using a workaround: puppet apply --environment=dev $(puppet master --environment=dev --configprint manifest) Thanks Alan Castro -- 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/bebc7744-d6be-43b7-bb72-b11e7908a0e0%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet apply hangs
I have a bunch of dev servers which have begun experiencing the same issue when I run puppet apply. The full command I'm using is: sudo puppet apply --modulepath=/opt/puppet-conf/development/modules --environment=development. I've never had a problem running this command before, but very recently, when I run it on any of my dev servers it just hangs right after I hit enter. It never times out and I don't get any output, event when I add --verbose, --debug and --detailed-exitcodes. I investigated further, and ran the above command using strace. It appears that puppet hangs when trying to read /etc/puppet/routes.yaml (which doesn't exist). I created /etc/puppet/routes.yaml but then puppet apply just fails (I'm not really sure what to put in routes.yaml, though). Does anyone have any idea what's happening here? I'm not sure why this only just started happening. For the record, here are the packages I have installed: ii facter1.7.4-1puppetlabs1 Ruby module for collecting simple facts about a host operating system ii hiera 1.3.0-1puppetlabs1 A simple pluggable Hierarchical Database. ii puppet3.4.2-1puppetlabs1 Centralized configuration management - agent startup and compatibility scripts ii puppet-common 3.4.2-1puppetlabs1 Centralized configuration management ii puppetlabs-release1.0-7Package to install Puppet Labs gpg key and apt repo ii ruby-rgen 0.6.5-1puppetlabs1 A framework supporting Model Driven Software Development (MDSD) Thanks, Guy g...@eastsidegamestudio.com -- 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/CA%2BgQdWBXJtPer6%2BrNJ68-hTbFrXv3Nhz%2Bdg30%2Bf4LW4Sy1CWmA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet apply hangs on Executing '/etc/init.d/ntp status'
Hi, after a machine has been up for a few days the following command hangs when running `puppet apply` (--debug added to see what was hanging) Service[ntpd](provider=debian): Executing '/etc/init.d/ntp status' Running `/etc/init.d/ntp status` works fine when run as root or as myself. Is there any way to figure out what puppet is hanging on? Is it hanging on its next action or that one? Env: -nodeless -ubuntu 12.04 -puppet 2.7.11 -ruby 1.8.7 Thanks in advance for any tips! -Ryan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
