Thanks for your help. I have reported the issue.
http://projects.puppetlabs.com/issues/3514
Byron
On Apr 6, 5:04 pm, Ken <k...@bob.sh> wrote:
> Looks like you are right. Line 892 from puppet/util/settings.rb:
>
> text.split(/\n/).each { |line|
>
> Its splitting on line feed. I'd raise a ticket if I was you - seems
> like a trivial change to that regular expression.
>
> Also - I think the puppet configuration doesn't throw errors when its
> wrong. It does when you get it wrong on the command line however, so
> the logic is there somewhere. This is already an open ticket here:
>
> http://projects.puppetlabs.com/issues/3119
>
> ken.
>
> On Apr 6, 9:52 pm, byron appelt <byron.app...@gmail.com> wrote:
>
> > I found the problem. My puppet.conf somehow got checked into SVN with
> > CR/LF line endings. Apparently this causes puppet to fail to read it,
> > quite silently even with --debug unfortunately.
>
> > On Apr 6, 11:59 am, byron appelt <byron.app...@gmail.com> wrote:
>
> > > Thanks, testing other settings was an excellent suggestion. It seems
> > > no settings in my puppet.conf are working. Any suggestions on how to
> > > debug this? This was all working before I upgrading from 0.24.5 to
> > > 0.25.4 For reference, here are my configs, although it seems that the
> > > client config is not even being read.
>
> > > Here is my client puppet.conf:[main]
>
> > > logdir=/var/log/puppet
> > > vardir=/var/lib/puppet
> > > ssldir=/etc/puppet/ssl
> > > rundir=/var/run/puppet
> > > factpath=/var/lib/facter
> > > pluginsync=true
> > > server=puppetmaster.numerex.com
> > > environments=production,testing
> > > environment=production
>
> > > [puppetd]
> > > report = true
>
> > > And here is the puppetmaster:
>
> > > main]
> > > logdir=/var/log/puppet
> > > vardir=/var/lib/puppet
> > > ssldir=/var/lib/puppet/ssl
> > > rundir=/var/run/puppet
> > > pluginsync=true
> > > server = puppetmaster.numerex.com
> > > environments = development,testing,production
> > > node_terminus = exec
> > > external_nodes = /etc/puppet/query_deploymanager.rb
>
> > > [puppetmasterd]
> > > certname=puppetmaster.numerex.com
>
> > > [puppetd]
> > > report = true
>
> > > [testing]
> > > modulepath = /etc/puppet-dev/manifests/classes
> > > templatedir=/etc/puppet-dev/templates
> > > manifest = /etc/puppet-dev/manifests/site.pp
> > > pluginsync = true
>
> > > [production]
> > > modulepath = /etc/puppet/manifests/classes
> > > templatedir=/etc/puppet/templates
> > > manifest = /etc/puppet/manifests/site.pp
> > > pluginsync = true
>
> > > On Apr 6, 2:17 am, Ken <k...@bob.sh> wrote:
>
> > > > Yes in theory. Depending on the section you put it in of course. I
> > > > have pluginsync=true in the [main] section of my puppet.conf, on both
> > > > my client and server and sync works fine.
>
> > > > Can you post your full configuration? Both client and server? Can you
> > > > confirm your other settings are working when you adjust them in
> > > > puppet.conf?
>
> > > > On Apr 5, 10:43 pm, byron appelt <byron.app...@gmail.com> wrote:
>
> > > > > I am trying to get a custom fact to sync. The fact is in a module. It
> > > > > will sync if I run puppet with "--pluginsync" but not otherwise. I
> > > > > have "pluginsync=true" in my puppet.conf. Shouldn't the command line
> > > > > option and puppet.conf option have the same results?
--
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.
