[Puppet Users] apache module class order issue with ENC
I'm attempting to use puppetlabs-apache with all my classes defined via
Foreman (1.5.1) with Puppet 3.4.3. Servers are all CentOS 6.5.
With puppetlabs-apache-1.0.1 when I applied both the apache class and
apache::mod::ssl class in Foreman I received this error on the server:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
undefined method `>=' for :undef:Symbol at
/etc/puppet/environments/production/modules/apache/manifests/mod/ssl.pp:36
on node web01.brazos.tamu.edu
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
I found the commit that changed how "apache_version" was handled and
deployed that and then I get:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Failed to parse template apache/mod/ssl.conf.erb:
Filepath: /usr/lib/ruby/site_ruby/1.8/puppet/util/package.rb
Line: 4
Detail: private method `scan' called for nil:NilClass
at
/etc/puppet/environments/production/modules/apache/manifests/mod/ssl.pp:51
on node web01.brazos.tamu.edu
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
This time the "@apache_version" variable in the template is being passed
the to versoncmp function, producing that error.
I don't know if this is a symptom of using an ENC, or a bug in the apache
module, but the class parameters in apache::mod::ssl reference the apache
class and despite the class being defined, the variables are all 'undef'.
I also ran into this same issue when I applied the apache::mod::wsgi class:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Invalid relationship: File[wsgi.conf] { before => File[undef] }, because
File[undef] doesn't seem to be in the catalog
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
In that case the fix was easier, just add "include ::apache" to the top of
the class.
Thanks
- Trey
--
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/f1d69f13-7a11-40cf-b5ab-0f33e8e6038f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: RHEL7 facts missing
Jelle, Installing net-tools package solved it. Thanks for your pointer! Op zaterdag 21 juni 2014 14:17:56 UTC+2 schreef Jelle B: > > Hi , Yes this is to be expected as RHEL 7 does away with some of the > dependencies like ifconfig etc. You will have to install thoose after. > For that you will also have to install some extra repos if I recall right. > > You will have to install bind-utils and net-tools for all to function > normal again. > > Hope this helps. > > On Friday, June 20, 2014 9:49:38 PM UTC+2, Bas Wildemann wrote: >> >> I'm looking into Redhat 7.0 at the moment and I discovered some facts >> missing compared to Redhat 6/ Centos 6 >> Some of my modules are relying on 'network_ethX' or 'interfaces' >> >> I noticed that the 'network_' fact is absent and the 'interface' >> fact is empty >> I'm using facter 2.0.2 >> >> Anyone experiencing this problem too? >> >> -- 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/9aa1f821-4b63-42e9-ad29-480c4e137a56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet Agent Run Problems
Hi all, We have a system configured with PE 3.1 and we have separate servers for the Puppet Master, PuppetDB (postgres) and puppet console. Running on Passenger and Apache. Everything was well up until yesterday where the DB box ran out of space so I added a new volume group and added it the existing volume for the DB and restarted the box. Then all hell broke loose so to speak! Firstly there was a Kaha corruption so I stopped Pe-PuppetDB service and renamed the Kaha file to .old and restarted it. Logs are fine and it starts ok. Just to be safe I also rebooted Pe Master server. Now there is very erratic behaviour, Some nodes the agent reports "Cannot Apply Catalogue Timeout:Error", other times it runs the catalogue but get a "Cannot find resource timeout" error. Other times I get a SSL Connect timeout message. Sometimes nodes even seem to run catalogue fine. I checked logs in PM, PDB and agents and cant find anything to suggest a issue. Any suggestions? Thanks -- 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/4cd6ff80-65f5-4ef3-b9de-3447b006c8cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: RHEL7 facts missing
Hi , Yes this is to be expected as RHEL 7 does away with some of the dependencies like ifconfig etc. You will have to install thoose after. For that you will also have to install some extra repos if I recall right. You will have to install bind-utils and net-tools for all to function normal again. Hope this helps. On Friday, June 20, 2014 9:49:38 PM UTC+2, Bas Wildemann wrote: > > I'm looking into Redhat 7.0 at the moment and I discovered some facts > missing compared to Redhat 6/ Centos 6 > Some of my modules are relying on 'network_ethX' or 'interfaces' > > I noticed that the 'network_' fact is absent and the 'interface' > fact is empty > I'm using facter 2.0.2 > > Anyone experiencing this problem too? > > -- 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/6f5283a0-7d40-4558-ac49-ace9f07d1c11%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Any solutions for server-side facts?
It also might be a cheap way of doing it, but if your looking at stuff at the node level anyway you can leverage LDAP. All objects in LDAP in puppet 3.x are treated as top scope variables. On Fri, Jun 20, 2014 at 6:58 PM, Matthew Hyclak wrote: > I was thinking about this not too long ago myself. It seems a little silly, > but creating a custom fact (let's stick with room number) that gets pushed > out by a paramaterized class in puppet does what you're looking for I think. > > The ENC defines the room number, but by having that show up in the custom > fact, you see the results of that in the puppet reports (and therefore in > your dashboard) in a convenient manner. You're also only managing that > definition in one place. > > So not-quite server-side, but close? > > Matt > > > On Fri, Jun 20, 2014 at 5:34 PM, Fine, Thomas wrote: >> >> Hi, >> >> As I get more into this and look at what puppet dashboard (and whatever I >> replace it with, sigh) can do and what we've been doing, it's great for >> simple inventory tracking. Except that if it's good at that I might as well >> get all the information in one place, like the room location, the user the >> system is assigned to, what's it's local inventory control number, and are >> there any important notes (like from human beings) on the current status of >> the system. >> >> Is there any system that provides for this functionality? Dashboard? >> Foreman? Anything else? I know about custom facts, and external facts, but >> those are all for client-side facts. I don't want to have to put a file on >> each machine that says what it's room number is, that'd be silly. >> >> I could make an external fact that consults our existing database to get >> the fact into the system, but my whole hope here is to eliminate our >> existing legacy inventory system in favor of having everything in one >> database. >> >> Also, I realize it's probably a bigger issue than simply adding fields, as >> it's sort of a different philosophy. For example renaming a machine >> currently creates a new node in the database (and leaves an old one to be >> cleaned up some day), but with this metadata attached we'd want to somehow >> connect the hardware information so that the metadata that's not changing >> follows automatically after the name change. >> >> So is there anything that provides this? I've searched and have come up >> empty but maybe I just don't know the magic buzzword I should be googling? >> >> Thanks, >> >> tom >> >> -- >> 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/CANVEBdh7Qn7Xvz425DYHSY%2Bm3DLp-p%2BxSxZaQOVVoMU3s52mNA%40mail.gmail.com. >> 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/CAO7w0s7hTKGMV2DRg8sDKx6HeYrPHQY7sgFAXRntTCThBh1i1g%40mail.gmail.com. > > 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/CAMM%2BeSXBxof4RwcnATHh1e0pnK_s7k136Yg5e3%3D6M8Ak%3DEvUYg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
