On Tue, Dec 30, 2008 at 7:16 AM, Christian Hofstaedtler <
hofstaedt...@inqnet.at> wrote:
>
> I've just checked on my installation, and filebucket seems to work
> fine (under passenger).
>
> For testing, I put these into the manifest:
> filebucket { main: server => $servername }
> File { backup => main }
>
> And these into namespaceauth.conf on the puppetmaster:
> [puppetbucket]
> allow *.domain.com
>
>
> Is your puppetmaster really called "puppet"? Can you connect (for
> example by using telnet) from the client to "puppet" on port 8140?
>
Gah! Of course my puppetmaster isn't named "puppet"! How did I miss that.
Trying $servername or $server both fail, but using the actual nodename seems
to work ok. Using the variables has it choke on certificate validation even
though using puppet://$server/files/ type urls work fine for sources. The
tricky bit is that the nodes need to talk to the puppetmaster on a specific
interface which isn't defined by the puppetmaster's hostname or fqdn. So,
certname is set for puppetmaster and puppetd on the puppetmaster.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~----------~----~----~----~------~----~------~--~---
