Puppet users - Sep 2006 - "server" config option (and cmd-line option) don''t do anything for puppetd?

Hi guys,

Unlike what it says in the documentation and the --help output, I
can''t seem to get puppetd to use the --server setting. The only way I
can get puppetd to work is to include a ''puppet'' alias to the
ip of
the machine I''m running puppetmasterd on in my hosts file.

The strange thing though, is that the logs of my puppetmaster show
that it *is* getting the requests from puppetd when I use --server to
point puppetd to the machine name I decided to use for it.

Is this intentional and are the docs out of sync or is it a bug? Or am
I doing something else wrong and it works for everyone else? (BTW: now
using the latest source releases of facter and puppet on Ubuntu
dapper)


Regards,

Thijs

Thijs Oppermann wrote:
> Hi guys,
> 
> Unlike what it says in the documentation and the --help output, I
> can''t seem to get puppetd to use the --server setting. The only
way I
> can get puppetd to work is to include a ''puppet'' alias to
the ip of
> the machine I''m running puppetmasterd on in my hosts file.
> 
> The strange thing though, is that the logs of my puppetmaster show
> that it *is* getting the requests from puppetd when I use --server to
> point puppetd to the machine name I decided to use for it.
I don''t really understand -- you''re saying the client
isn''t connecting
to the server but the server is seeing connection attempts?
> Is this intentional and are the docs out of sync or is it a bug? Or am
> I doing something else wrong and it works for everyone else? (BTW: now
> using the latest source releases of facter and puppet on Ubuntu
> dapper)
As far as I can tell, --server works fine.  Do you have a server defined 
in /etc/puppet/puppetd.conf?  A CLI-specified server should override 
that value, but if it''s set in both places that could be the source of 
the bug.

Is anyone else experiencing this bug?  Is anyone else successfully using 
--server?

-- 
It''s not that I''m afraid to die. I just don''t want to
be there when it
happens.  -- Woody Allen
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com

On 28/09/06, Luke Kanies <luke@madstop.com> wrote:
> Thijs Oppermann wrote:
> > Hi guys,
> >
> > Unlike what it says in the documentation and the --help output, I
> > can''t seem to get puppetd to use the --server setting. The
only way I
> > can get puppetd to work is to include a ''puppet''
alias to the ip of
> > the machine I''m running puppetmasterd on in my hosts file.
> >
> > The strange thing though, is that the logs of my puppetmaster show
> > that it *is* getting the requests from puppetd when I use --server to
> > point puppetd to the machine name I decided to use for it.
>
> I don''t really understand -- you''re saying the client
isn''t connecting
> to the server but the server is seeing connection attempts?
>
Well, what I was trying to say is that puppetd fails with an error if
I don''t name my puppetmaster maching "puppet". After some
testing,
this is what I get:

-> putting in an alias (in the hosts file) to "puppet" for the
puppetmaster (which I have called "dalang"): everything works

-> removing the alias and then running "puppetd --test" gives
*only*:
"err: Could not find server puppet"

-> no alias and running "puppetd --test --server dalang" gives the
following sequence:
info: Caching configuration at /etc/puppet/localconfig.yaml
notice: Starting configuration run
err: Could not find server puppet


So with the --server option brings me further, but it does fail
somewhere later in the process.

>
> > Is this intentional and are the docs out of sync or is it a bug? Or am
> > I doing something else wrong and it works for everyone else? (BTW: now
> > using the latest source releases of facter and puppet on Ubuntu
> > dapper)
>
> As far as I can tell, --server works fine.  Do you have a server defined
> in /etc/puppet/puppetd.conf?  A CLI-specified server should override
> that value, but if it''s set in both places that could be the
source of
> the bug.
>
The above tests were on a machine without any /etc/puppet/puppetd.conf
>
> Is anyone else experiencing this bug?  Is anyone else successfully using
> --server?
>
> --
> It''s not that I''m afraid to die. I just don''t
want to be there when it
> happens.  -- Woody Allen
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>

Thijs Oppermann wrote:
> 
> Well, what I was trying to say is that puppetd fails with an error if
> I don''t name my puppetmaster maching "puppet". After
some testing,
> this is what I get:
> 
> -> putting in an alias (in the hosts file) to "puppet" for the
> puppetmaster (which I have called "dalang"): everything works
> 
> -> removing the alias and then running "puppetd --test" gives
*only*:
> "err: Could not find server puppet"
> 
> -> no alias and running "puppetd --test --server dalang" gives
the
> following sequence:
> info: Caching configuration at /etc/puppet/localconfig.yaml
> notice: Starting configuration run
> err: Could not find server puppet
> 
> 
> So with the --server option brings me further, but it does fail
> somewhere later in the process.
Are you doing file-copying in your configuration?  Might some of that 
file-copying be looking for a server named ''puppet''?

You should be able to open /etc/puppet/localconfig.yaml and search for 
''puppet''; if you see something like
''puppet://puppet/...'', then you''re
contacting a server named ''puppet''.  Try changing that to 
''puppet://<servername>/...'' in your configuration.

-- 
The most overlooked advantage to owning a computer is that if they foul
up there''s no law against wacking them around a little.  -- Joe Martin
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com

I''m an idiot. You are of course correct. Thanks.

Thijs

On 28/09/06, Luke Kanies <luke@madstop.com> wrote:
> Thijs Oppermann wrote:
> >
> > Well, what I was trying to say is that puppetd fails with an error if
> > I don''t name my puppetmaster maching "puppet".
After some testing,
> > this is what I get:
> >
> > -> putting in an alias (in the hosts file) to "puppet"
for the
> > puppetmaster (which I have called "dalang"): everything
works
> >
> > -> removing the alias and then running "puppetd --test"
gives *only*:
> > "err: Could not find server puppet"
> >
> > -> no alias and running "puppetd --test --server dalang"
gives the
> > following sequence:
> > info: Caching configuration at /etc/puppet/localconfig.yaml
> > notice: Starting configuration run
> > err: Could not find server puppet
> >
> >
> > So with the --server option brings me further, but it does fail
> > somewhere later in the process.
>
> Are you doing file-copying in your configuration?  Might some of that
> file-copying be looking for a server named ''puppet''?
>
> You should be able to open /etc/puppet/localconfig.yaml and search for
> ''puppet''; if you see something like
''puppet://puppet/...'', then you''re
> contacting a server named ''puppet''.  Try changing that to
> ''puppet://<servername>/...'' in your configuration.
>
> --
> The most overlooked advantage to owning a computer is that if they foul
> up there''s no law against wacking them around a little.  -- Joe
Martin
> ---------------------------------------------------------------------
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>