RE: [Puppet Users] Newbie: Agent doesn't find master
Chris, Try this on the server running the puppet agent to verify the puppet master the agent is configured to use Command: sudo puppet config print server --section agent If it is incorrect then follow these steps 1. Stop the puppet service Command Example: sudo puppet resource service puppet ensure=stopped 2. Remove (or rename) ssl cert directory Command Example: sudo mv /etc/puppetlabs/puppet/ssl /etc/puppetlabs/puppet/ssl.orig 3. Clean any certs on the puppet master Command Example: sudo puppet cert clean agentHostName 4. Change name of puppet master on agent Command Exmaple: sudo puppet config set server puppetMaster --section agent 5. Verify desired puppet master is now configured Command: sudo puppet config print server --section agent 6. Perform a puppet run puppet agent -t 7. If that works, start up the puppet service Example Command: sudo puppet resource service puppet ensure=started 8. If you renamed in step 2 then remove the original directory HTH Billy- -Original Message- From: "Chris" Sent: Saturday, July 25, 2015 2:25pm To: "Puppet Users" Subject: [Puppet Users] Newbie: Agent doesn't find master Dear All, sorry, I'm a newbie. My agent doesn't find the master. Where can I specify the master's name? It's working, when the master is called puppet, but not if it has another name ... TIA - Chris -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/29ce43d247fe735be68a91310484b1e8%40postbox.xyz. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1438029966.75016471%40apps.rackspace.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] fileserver.conf -- files not serving
Hi there,
I am trying to keep Puppet modules in sync between Puppet masters in an
environment where SSH is being blocked between the masters (long story
there, corporate security rules), Git and other such are not an option but
I can use port 8140 between them.
So I set up a fileserver.conf like thus:
[data]
path=/data
allow *
and added this to the auth.conf file:
path ~ ^/file_(metadata|content)s?/data/
auth yes
allow *
and one of the classes managing this looks like:
class puppet::master::classdir {
include puppet::params
$src_uri = 'puppet:///data/puppet-modules'
file { '/data/puppet-modules':
source => $src_uri,
owner => root,
group => root,
mode=> '0755',
recurse => true
}
}
and when the Puppet agent runs I see this:
Error: /Stage[main]/Puppet::Master::Classdir/File[/data/puppet-modules]:
Failed to generate additional resources using 'eval_generate': Error 400 on
SERVER: Not authorized to call search on /file_metadata/data/puppet-modules
with {:recurse=>true, :checksum_type=>"md5", :links=>"manage"}
Error: /Stage[main]/Puppet::Master::Classdir/File[/data/puppet-modules]:
Could not evaluate: Could not retrieve file metadata for
puppet:///data/puppet-modules: Error 400 on SERVER: Not authorized to call
find on /file_metadata/data/puppet-modules with
{:source_permissions=>"use", :links=>"manage"}
Wrapped exception:
Error 400 on SERVER: Not authorized to call find on
/file_metadata/data/puppet-modules with {:source_permissions=>"use",
:links=>"manage"}
OK.. so what am I missing 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAArvnv0V2GxEh_6kVB54VWf11MrX7LN5javu9ipL5T6r40kVaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Puppet 4 on Debian Jessie amd64
On Mon, Jul 27, 2015 at 2:43 AM, Richard Wales wrote: > Hi folks, > > Apparently PC1 is available on Debian Jessie now. Unfortunately, I can't get > it to work. I've attached a vagrant file to facilitate reproduction (remove > the .txt extension that I had to add to upload it). > > Here are the relevant commands I am running (as per the docs at > https://docs.puppetlabs.com/puppet/latest/reference/install_linux.html ): > > # wget https://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb > # dpkg -i puppetlabs-release-pc1-jessie.deb > # apt-get update > # apt-get install puppetserver -y # This fails We have puppet-agent packages available for Debian Jessie, but not Puppet Server packages[1]. Those should be available with the next Puppet Server release. So, you can't yet run Debian Jessie as a master, but you can run it as an agent with the puppet-agent package against a master on a different platform. [1] - http://apt.puppetlabs.com/pool/jessie/PC1/p/ > > The bottom line is the new packages aren't available; only the old (puppet > 3.7.x packages). Can anyone shed any light? Where am I going wrong guys? > > Cheers, > Richard > > P.S. Here are some diagnostic commands for the curious: > > # apt-cache search puppet | grep ^puppet > > ==> default: puppet - configuration management system, agent > > ==> default: puppet-common - configuration management system > > ==> default: puppet-el - syntax highlighting for puppet manifests in emacs > > ==> default: puppet-testsuite - configuration management system, development > test suite > > ==> default: puppetmaster - configuration management system, master service > > ==> default: puppetmaster-common - configuration management system, master > common files > > ==> default: puppetmaster-passenger - configuration management system, > scalable master service > > ==> default: puppet-lint - check puppet manifests for style guide conformity > > ==> default: puppet-module-puppetlabs-apache - Puppet module for apache > > ==> default: puppet-module-puppetlabs-apt - Puppet module for apt > > ==> default: puppet-module-puppetlabs-concat - Puppet module for concat > > ==> default: puppet-module-puppetlabs-firewall - Puppet module for Firewall > management > > ==> default: puppet-module-puppetlabs-inifile - Puppet module for ini files > > ==> default: puppet-module-puppetlabs-mysql - Puppet module for mysql > > ==> default: puppet-module-puppetlabs-ntp - Puppet module for ntp > > ==> default: puppet-module-puppetlabs-postgresql - Puppet module for > PostgreSQL database > > ==> default: puppet-module-puppetlabs-stdlib - Puppet module standard > library > > ==> default: puppet-module-puppetlabs-xinetd - Puppet module for xinetd > > ==> default: puppet-module-saz-memcached - Puppet module for memcached > > ==> default: puppetlabs-release-pc1 - Release packages for the Puppet Labs > PC1 repository > > ==> default: puppet-agent - The Puppet Agent package contains all of the > elements needed to run puppet, including ruby, facter, hiera and > mcollective. > > > # uname -a > > ==> default: Linux test 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 > (2015-05-24) x86_64 GNU/Linux > > > # cat /etc/os-release > > ==> default: PRETTY_NAME="Debian GNU/Linux 8 (jessie)" > > ==> default: NAME="Debian GNU/Linux" > > ==> default: VERSION_ID="8" > > ==> default: VERSION="8 (jessie)" > > ==> default: ID=debian > > ==> default: HOME_URL="http://www.debian.org/"; > > ==> default: SUPPORT_URL="http://www.debian.org/support/"; > > ==> default: BUG_REPORT_URL="https://bugs.debian.org/"; > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/7dfcb022-6c5e-4337-84c2-9fc7a2e9cd94%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Melissa Stone Release Engineer, Puppet Labs -- PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9. Register now to take advantage of the Early Bird discount —save $249! -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAHEe_ko3-1OVm94X_PJ%3DUWxrqbLsAZj4msmmkvW0S81rZgyuzQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Hi All, Can someone help me to understand chef & puppet detail. I am new to this.
On Monday, July 27, 2015 at 10:06:38 AM UTC-4, JZacharias wrote: > > Hi All, Can someone help me to understand chef & puppet detail. I am new > to this > Hello, I apologize if I'm misunderstanding your question, but what I'm getting is that you're trying to understand what Chef and Puppet do? If that's your intent, then you should know that they are both configuration management tools. At their core, they do the same thing, they just go about it in different ways. You might want to start by reading the following: https://en.wikipedia.org/wiki/Configuration_management https://en.wikipedia.org/wiki/Puppet_%28software%29 https://en.wikipedia.org/wiki/Chef_%28software%29 As far as Puppet goes, you can easily take it for a spin yourself with the Learning VM: https://puppetlabs.com/download-learning-vm I hope this helps. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d7c777d6-7610-4c1f-96c7-122fe1e10a34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Hi All, Can someone help me to understand chef & puppet detail. I am new to this.
Hi All, Can someone help me to understand chef & puppet detail. I am new to this -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0dbbe256-ca19-4265-b84e-9fbe937c0cb1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Newbie: Agent doesn't find master
In the [agent] section of your puppet.conf: server=master.example.com https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html On Monday, 27 July 2015 14:41:17 UTC+1, Chris wrote: > > Dear All, > > sorry, I'm a newbie. > > My agent doesn't find the master. Where can I specify the master's > name? > > It's working, when the master is called puppet, but not if it has > another name ... > > TIA > > - Chris > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/eb640987-6c48-4700-9233-a0ecd1a9409b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Newbie: Agent doesn't find master
Hi, you can specify the hosts name in the puppet.conf in the [agents] section as follows: server = puppet.example.com Please make sure, that you can ping the exact name as you specified it. Best regards, Titus Am 25.07.2015 um 20:25 schrieb Chris : > Dear All, > > sorry, I'm a newbie. > > My agent doesn't find the master. Where can I specify the master's name? > > It's working, when the master is called puppet, but not if it has another > name ... > > TIA > > - Chris > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/29ce43d247fe735be68a91310484b1e8%40postbox.xyz. > For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CA546121-80E4-4A0E-84AC-FF5DB2D6890F%40gt-it.de. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet 4 on Debian Jessie amd64
Hi folks, Apparently PC1 is available on Debian Jessie now. Unfortunately, I can't get it to work. I've attached a vagrant file to facilitate reproduction (remove the .txt extension that I had to add to upload it). Here are the relevant commands I am running (as per the docs at https://docs.puppetlabs.com/puppet/latest/reference/install_linux.html ): # wget https://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb # dpkg -i puppetlabs-release-pc1-jessie.deb # apt-get update # apt-get install puppetserver -y # This fails The bottom line is the new packages aren't available; only the old (puppet 3.7.x packages). Can anyone shed any light? Where am I going wrong guys? Cheers, Richard P.S. Here are some diagnostic commands for the curious: *# apt-cache search puppet | grep ^puppet* ==> default: puppet - configuration management system, agent ==> default: puppet-common - configuration management system ==> default: puppet-el - syntax highlighting for puppet manifests in emacs ==> default: puppet-testsuite - configuration management system, development test suite ==> default: puppetmaster - configuration management system, master service ==> default: puppetmaster-common - configuration management system, master common files ==> default: puppetmaster-passenger - configuration management system, scalable master service ==> default: puppet-lint - check puppet manifests for style guide conformity ==> default: puppet-module-puppetlabs-apache - Puppet module for apache ==> default: puppet-module-puppetlabs-apt - Puppet module for apt ==> default: puppet-module-puppetlabs-concat - Puppet module for concat ==> default: puppet-module-puppetlabs-firewall - Puppet module for Firewall management ==> default: puppet-module-puppetlabs-inifile - Puppet module for ini files ==> default: puppet-module-puppetlabs-mysql - Puppet module for mysql ==> default: puppet-module-puppetlabs-ntp - Puppet module for ntp ==> default: puppet-module-puppetlabs-postgresql - Puppet module for PostgreSQL database ==> default: puppet-module-puppetlabs-stdlib - Puppet module standard library ==> default: puppet-module-puppetlabs-xinetd - Puppet module for xinetd ==> default: puppet-module-saz-memcached - Puppet module for memcached ==> default: puppetlabs-release-pc1 - Release packages for the Puppet Labs PC1 repository ==> default: puppet-agent - The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. *# uname -a* ==> default: Linux test 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux *# cat /etc/os-release* ==> default: PRETTY_NAME="Debian GNU/Linux 8 (jessie)" ==> default: NAME="Debian GNU/Linux" ==> default: VERSION_ID="8" ==> default: VERSION="8 (jessie)" ==> default: ID=debian ==> default: HOME_URL="http://www.debian.org/"; ==> default: SUPPORT_URL="http://www.debian.org/support/"; ==> default: BUG_REPORT_URL="https://bugs.debian.org/"; -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7dfcb022-6c5e-4337-84c2-9fc7a2e9cd94%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. $script = <
Re: [Puppet Users] rpm installation ordering question and yum repos
Oh I misread the question sorry :) -- Yes the stages is probably the right
approach.
/Martin
On Mon, Jul 27, 2015 at 2:18 PM Martin wrote:
> We simply use YUM priorities for that:
>
> http://wiki.centos.org/PackageManagement/Yum/Priorities
>
>
> On Fri, Jul 24, 2015 at 6:30 PM Vince Skahan
> wrote:
>
>> Like many sites, we have internal yum repos that contain our
>> internally-created rpms, as well as some other repos that are internal
>> mirrors of upstream sites (centos updates, etc.). We're running into an
>> ordering issue that I'm looking for what the current suggested best
>> practice is
>>
>> We cooked up a 'my-mirrors-release' rpm notionally like 'epel-release' or
>> 'centos-release' etc. that you'd commonly see. Contents are the
>> /etc/yum.repos.d files for the various internal repos, and some /etc/pki
>> gpg keys for the repos that have signed rpms. Typical yum repo stuff.
>>
>> Question is how to ensure that our local mirrors-release rpm installs
>> before any other rpms that would need to have the repo defined in order to
>> find the rpms therein. In other words we want this rpm installed first.
>> Like 'really' first
>>
>> We're trying to avoid having to specify having the my-mirrors-release rpm
>> be installed before rpmXYZ every time we specify a rpm to be installed in
>> all the places we might want to specify a package be installed. Looking
>> for suggestions for a current best practice (assume puppet 3.8 but if
>> there's 4.0 magic, that would be good to know)
>>
>> One solution we came up with is the bottom line in the code snippet
>> below. Is this today's best practice for this kind of thing ? Again -
>> we're trying to ensure this 'one' rpm is there before installing later rpms
>> that would depend on it. Suggestions ?
>>
>>
>> class myprofiles::my_mirrors { # disable upstream repos yumrepo {
>> 'updates': enabled => 0, } # enable our mirrors yumrepo {
>> 'my-repos': baseurl =>
>> 'http://mirrors.example.com/my-mirrors-release/el6', enabled => 1,
>> } package { 'my-mirrors-release':provider => yum,ensure =>
>> latest,require => Yumrepo['my-repos'], } # Ensure our repositories
>> are installed before any other package. # (Otherwise the package may not be
>> found.) Package<| title == 'my-mirrors-release' |> -> Package<| title !=
>> 'my-mirrors-release' |>
>> }
>>
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/aa22ca14-f478-48f9-bda1-6d5d804ac657%40googlegroups.com
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> http://www.xing.com/profile/Martin_Marcher
> http://www.linkedin.com/in/martinmarcher
> Mobil: +43 / 660 / 62 45 103
> UID: ATU68801424
>
--
--
http://www.xing.com/profile/Martin_Marcher
http://www.linkedin.com/in/martinmarcher
Mobil: +43 / 660 / 62 45 103
UID: ATU68801424
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAK1mKEQTAz%3Dpvr8eCBd9sw%2BUbNWi2nmUQFZeJ8P%3DCyHVwHfO2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] rpm installation ordering question and yum repos
We simply use YUM priorities for that:
http://wiki.centos.org/PackageManagement/Yum/Priorities
On Fri, Jul 24, 2015 at 6:30 PM Vince Skahan wrote:
> Like many sites, we have internal yum repos that contain our
> internally-created rpms, as well as some other repos that are internal
> mirrors of upstream sites (centos updates, etc.). We're running into an
> ordering issue that I'm looking for what the current suggested best
> practice is
>
> We cooked up a 'my-mirrors-release' rpm notionally like 'epel-release' or
> 'centos-release' etc. that you'd commonly see. Contents are the
> /etc/yum.repos.d files for the various internal repos, and some /etc/pki
> gpg keys for the repos that have signed rpms. Typical yum repo stuff.
>
> Question is how to ensure that our local mirrors-release rpm installs
> before any other rpms that would need to have the repo defined in order to
> find the rpms therein. In other words we want this rpm installed first.
> Like 'really' first
>
> We're trying to avoid having to specify having the my-mirrors-release rpm
> be installed before rpmXYZ every time we specify a rpm to be installed in
> all the places we might want to specify a package be installed. Looking
> for suggestions for a current best practice (assume puppet 3.8 but if
> there's 4.0 magic, that would be good to know)
>
> One solution we came up with is the bottom line in the code snippet
> below. Is this today's best practice for this kind of thing ? Again -
> we're trying to ensure this 'one' rpm is there before installing later rpms
> that would depend on it. Suggestions ?
>
>
> class myprofiles::my_mirrors { # disable upstream repos yumrepo {
> 'updates': enabled => 0, } # enable our mirrors yumrepo {
> 'my-repos': baseurl =>
> 'http://mirrors.example.com/my-mirrors-release/el6', enabled => 1, }
> package { 'my-mirrors-release':provider => yum,ensure => latest,
> require => Yumrepo['my-repos'], } # Ensure our repositories are installed
> before any other package. # (Otherwise the package may not be found.)
> Package<| title == 'my-mirrors-release' |> -> Package<| title !=
> 'my-mirrors-release' |>
> }
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/aa22ca14-f478-48f9-bda1-6d5d804ac657%40googlegroups.com
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
--
http://www.xing.com/profile/Martin_Marcher
http://www.linkedin.com/in/martinmarcher
Mobil: +43 / 660 / 62 45 103
UID: ATU68801424
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAK1mKETLjS2QZ7fki%2BpbdkDrK7ncQ6ycNMJf8sbpQS9Uu1%2BqzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] ripienaar/puppet-module-data Not working with the Vagrant puppet provisioner.
Yes, thanks for the comment. I am aware of this approach, but given the module still works ok under Puppet4 and we have a used it a fair bit, I (and my bosses) would obviously prefer not to have to develop a new solution. That said, it is something I am looking into. Fraser. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cfdcee69-cab8-455a-bc42-2b8d167ec83a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
