Hello everyone,

First of all, thanks for the prompt help. I should  be able to move forward.

I followed the suggestions pointed here. None of them seemed to work.
However, the problem was in the versions I was using. I could not confirm in
changelogs, but the versions I had installed from both distros (ubuntu -
master, RH - slave) don't seem to support multiple environments. Also, I
refactored my puppet.conf file.

I decide to go for the versions from EPEL-testing and from Rubygems (btw,
the latest just released) and it seemed to work fine, as showed in:

Slave ...
# puppet agent --no-daemonize --verbose --noop --test --environment
development
# puppet agent --no-daemonize --verbose --noop --test --environment testing

# puppet master --no-daemonize --debug
debug: importing '/etc/puppet/manifests/nodes.pp' in environment production
notice: Compiled catalog for XXXX in environment development in 0.07 seconds
info: Caching node for XXXXX
notice: Compiled catalog for XXXXXX in environment testing in 0.03 seconds

thanks,
-fred




On Sat, Aug 13, 2011 at 1:15 AM, Stefan Schulte <
[email protected]> wrote:

> On Fri, Aug 12, 2011 at 02:39:37PM -0700, Frederiko Costa wrote:
> > Hello everyone,
> >
> > I have the following environments configured as master:
> >
> > # puppetmasterd -V
> > 0.25.4
> >
> > # cat puppet.conf
> > [main]
> >  confir=/etc/puppet
> >  logdir=/var/log/puppet
> >  vardir=/var/lib/puppet
> >  ssldir=/var/lib/puppet/ssl
> >  rundir=/var/run/puppet
> >  pidfile=$rundir/puppetmasterd.pid
> >  factpath=$vardir/lib/facter
> >  pluginsync=true
> >  templatedir=$confdir/templates
> >  prerun_command=/etc/puppet/etckeeper-commit-pre
> >  postrun_command=/etc/puppet/etckeeper-commit-post
> >
> > [master]
> >   modulepath=$confdir/environments/$environment/modules:$confdir/modules
> >   manifest=$confdir/manifests/unknown.pp
> >
> > [development]
> >  manifest   = $confdir/manifests/site.pp
> >
> > [testing]
> >  manifest   = $confdir/manifests/site.pp
> >
> > I have the modules in place, for every environment. This does not seem to
> be
> > an issue. Certificates are correctly signed.
> > The problem is that my agent located on another host, does not load the
> > development environment whenever I run the following command:
> > # puppetd -V
> > 0.25.4
> >
> > # puppetd agent --verbose --server=lbre-puppet.stanford.edu --noop
> --test
> > --environment development
> >
>
> The first thing to notice here is that you're mixing >2.6.0 syntax with
> old 0.25.4 syntax. In 0.25.4 to run the agent you use
>
>  puppetd
>
> in 2.6.0 and above it is [1]
>
>  puppet agent
>
> Also your master section in your puppet.conf should be [puppetmasterd]
> instead of [master].[2] This might not solve the issue but I would correct
> this first. (or update to a recent puppet version of course)
>
> [1] http://docs.puppetlabs.com/guides/tools.html
> [2]
> http://docs.puppetlabs.com/guides/configuring.html#notes-on-puppet-0255-and-older
>
> -Stefan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" 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-users?hl=en.

Reply via email to