Some environments not working in puppet

[Vishal Goel]

I am experiencing a very strange error in puppet. I have around 4-5 environments in my puppet codebase and whenever i add a new environment, it doesn't work. Even thought the code of new environment added is almost similar, it doesn't work.

Below is my puppet.conf file:

[main]

logdir=/var/log/puppet

vardir=/var/lib/puppet

ssldir=/var/lib/puppet/ssl

rundir=/var/run/puppet

factpath=$vardir/lib/facter

templatedir=$confdir/templates

pluginsync=true

masterport=8141

[master]

reports = store

environment_timeout = unlimited

autosign = true

[newdcdeploy]

modulepath = $confdir/modules

manifest = $confdir/environments/newdcdeploy/manifests/site.pp

[newdcalerts]

modulepath = $confdir/modules

manifest = $confdir/environments/newdcalerts/manifests/site.pp

So, newdcdeploy is working and newdcalerts is not. And both have exact same tree directory and content in files, only the names of environment are different. Am I missing something here?

[Martin Alfke]

On 18 Sep 2015, at 09:24, Vishal Goel <vgo...@gmail.com> wrote:

> I am experiencing a very strange error in puppet. I have around 4-5 environments in my puppet codebase and whenever i add a new environment, it doesn't work. Even thought the code of new environment added is almost similar, it doesn't work.

Have you restarted the puppet master process after adding the static environment?
Maybe you want to have a look at environment path setting in puppet
https://docs.puppetlabs.com/puppet/3.8/reference/environments_configuring.html

>
> Below is my puppet.conf file:
>
> [main]
> logdir=/var/log/puppet
> vardir=/var/lib/puppet
> ssldir=/var/lib/puppet/ssl
> rundir=/var/run/puppet
> factpath=$vardir/lib/facter
> templatedir=$confdir/templates
> pluginsync=true
> masterport=8141
>
> [master]
> reports = store
> environment_timeout = unlimited
> autosign = true
>
> [newdcdeploy]
> modulepath = $confdir/modules
> manifest = $confdir/environments/newdcdeploy/manifests/site.pp
>
> [newdcalerts]
> modulepath = $confdir/modules
> manifest = $confdir/environments/newdcalerts/manifests/site.pp
>
> So, newdcdeploy is working and newdcalerts is not. And both have exact same tree directory and content in files, only the names of environment are different. Am I missing something here?
>

> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a11ba4c8-f871-4d76-85fc-99a1948fcc7a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Vishal Goel]

Yes, I always restart puppetmaster after adding a new environment or doing any changes in code for that matter.

Also, below are the two processes that are running on the puppetmaster (used ps -ef | grep puppet )

puppet   29247     1  0 12:27 ?        00:00:00 Rack: /usr/share/puppet/rack/puppetmasterd                                                                                                    

puppet   30130     1  0 12:29 ?        00:00:05 /usr/bin/ruby1.8 /usr/bin/puppet master

Maybe the problem is with them?

[Martin Alfke]

On 18 Sep 2015, at 09:49, Vishal Goel <vgo...@gmail.com> wrote:

> Yes, I always restart puppetmaster after adding a new environment or doing any changes in code for that matter.
>
> Also, below are the two processes that are running on the puppetmaster (used ps -ef | grep puppet )
> puppet 29247 1 0 12:27 ? 00:00:00 Rack: /usr/share/puppet/rack/puppetmasterd

This is the passenger process

>
>
> puppet 30130 1 0 12:29 ? 00:00:05 /usr/bin/ruby1.8 /usr/bin/puppet master

This is the ruby webrick process. Kill this one!

> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7828482b-22ea-438e-b136-2125193b2f59%40googlegroups.com.

[Vishal Goel]

When I kill it and restart the puppetmaster, it is again created. And how do i make sure that only passenger/ruby webrick runs the puppetmaster?

[Martin Alfke]

On 18 Sep 2015, at 10:53, Vishal Goel <vgo...@gmail.com> wrote:

> When I kill it and restart the puppetmaster, it is again created. And how do i make sure that only passenger/ruby webrick runs the puppet master?

service puppetmaster will start the ruby process
This is the one you want to disable.

service apache|nginx|httpd will start the passenger rack application.
The web server name depends on
- which web server
- which distribution

> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a31eadf9-c400-4a2c-86e5-848702e78af1%40googlegroups.com.