FreeBSD Port

[JA]

I have installed puppet using the FreeBSD port. However, when I try
to use the agent, it attempts to start the puppetd daemon. It seems
that there is no way to use this installation without running the
daemon. Can anyone shed any light on this?

Thank you!

[Christopher Wood]

(I'm just starting with FreeBSD, albeit with some months of puppet experience.)

The puppet agent implies a daemon, but try something like this for a single run in the foreground:

puppet agent --no-daemonize --onetime

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
>

[JA]

Thanks so much!

However, I am a bit stumped and would so appreciate any clarity you can provide.

If I execute 'puppet agent --test' on a RHEL box, it does not start
the daemon. But, if I do the same thing using the FreeBSD port, it
does attempt to start the daemon.

Obviously, I am missing something here...

Thanks!
Jackie

[Darryl Wisneski]

Why not this?

'puppet agent -t' or 'puppet agent --test'

From puppet help.. (ughh, no manpage)

* --test:
Enable the most common options used for testing. These are 'onetime',
'verbose', 'ignorecache', 'no-daemonize', 'no-usecacheonfailure',
'detailed-exit-codes', 'no-splay', and 'show_diff'.

-dkw

[JA]

The thing is, when I execute

puppet agent --test

It tries to start the daemon automatically. I do not get this same
behavior on RHEL and I am trying to understand this.... I am totally
new to puppet land so, maybe I am just missing something here

Thanks!
Jackie

[Christopher Wood]

I couldn't say, perhaps different versions? Or run with more verbosity and see what both versions are doing.

Puppet 2.6.2 on Debian Stable (6.0.4):

"Enable the most common options used for testing. These are +onetime+, +verbose+, +ignorecache, +no-daemonize+, and +no-usecacheonfailure+."

Puppet 2.7.6 on FreeBSD (9.0-RELEASE):

"Enable the most common options used for testing. These are 'onetime', 'verbose', 'ignorecache', 'no-daemonize', 'no-usecacheonfailure', 'detailed-exit-codes', 'no-splay', and 'show_diff'."

I'm not sure it matters as long as you can get a onetime run. Dig into the ruby code if it's really bothering you, of course.

As to Darryl's comment in another branch, I haven't needed more than no-daemonize, verbose, and debug to solve all my problems so far.

[Darryl Wisneski]

Jackie:

Please post your 1.) puppet.conf, OS Relase, and version of puppet.

2.) uname -a
3.) pkg_info |grep puppet

Can you check the ps output to make sure there wasn't already a
running puppet. Do you have any jails on the machine that may be
running puppet as well and causing PID confusion?

Thanks,
-dkw

On Wed, Apr 11, 2012 at 10:50:10AM -0400, Christopher Wood wrote:
> I couldn't say, perhaps different versions? Or run with more verbosity and see what both versions are doing.
>
> Puppet 2.6.2 on Debian Stable (6.0.4):
>
> "Enable the most common options used for testing. These are +onetime+, +verbose+, +ignorecache, +no-daemonize+, and +no-usecacheonfailure+."
>
> Puppet 2.7.6 on FreeBSD (9.0-RELEASE):
>
> "Enable the most common options used for testing. These are 'onetime', 'verbose', 'ignorecache', 'no-daemonize', 'no-usecacheonfailure', 'detailed-exit-codes', 'no-splay', and 'show_diff'."
>
> I'm not sure it matters as long as you can get a onetime run. Dig into the ruby code if it's really bothering you, of course.
>
> As to Darryl's comment in another branch, I haven't needed more than no-daemonize, verbose, and debug to solve all my problems so far.
>
> On Wed, Apr 11, 2012 at 10:27:19AM -0400, JA wrote:
> > Thanks so much!
> >
> > However, I am a bit stumped and would so appreciate any clarity you can provide.
> >
> > If I execute 'puppet agent --test' on a RHEL box, it does not start
> > the daemon. But, if I do the same thing using the FreeBSD port, it
> > does attempt to start the daemon.
> >
> > Obviously, I am missing something here...
> >
> > Thanks!
> > Jackie
> >
> > On Wed, Apr 11, 2012 at 10:02 AM, Christopher Wood
> > <christop...@pobox.com> wrote:
> > > (I'm just starting with FreeBSD, albeit with some months of puppet experience.)
> > >
> > > The puppet agent implies a daemon, but try something like this for a single run in the foreground:
> > >
> > > puppet agent --no-daemonize --onetime
> > >
> > > On Wed, Apr 11, 2012 at 07:31:14AM -0400, JA wrote:

> > >> I have installed puppet using the FreeBSD port. ?However, when I try
> > >> to use the agent, it attempts to start the puppetd daemon. ?It seems

> > >> that there is no way to use this installation without running the

> > >> daemon. ?Can anyone shed any light on this?

[JA]

Hi Daryl;

As requested.. and thanks for the help!!

1.)puppetdev10# vi /etc/puppet/puppet.conf

[main]
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppet

# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppet

# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl

[agent]
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is '$confdir/classes.txt'.
classfile = $vardir/classes.txt

# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig
server=puppetdev
pluginsync = true

2.)puppetdev1# pkg_info | grep puppet
puppet-2.7.12 A configuration management framework written in Ruby

3.)FreeBSD 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC
2011 ro...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
amd64

[JA]

I did verify that there are no other puppet processes running as well.
Thanks!

On Wed, Apr 11, 2012 at 11:02 AM, Darryl Wisneski
<dar...@prometheusresearch.com> wrote:

[Jax01]

Hey guys..

Thanks for the help!

I found my problem. I was using pup[pet.conf in /etc/puppet instead
of /usr/local/etc/puppet..... (FreeBSD)

Thanks and sorry for the interruption!
Jackie

> >> > >> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.

>
> >> > > --
> >> > > You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> >> > > To post to this group, send email to puppet...@googlegroups.com.
> >> > > To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

> >> > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.

>
> >> > --
> >> > You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> >> > To post to this group, send email to puppet...@googlegroups.com.
> >> > To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

> >> > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.

>
> >> --
> >> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> >> To post to this group, send email to puppet...@googlegroups.com.
> >> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

> >> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.