[Puppet Users] Host name look up failure- unable to generate certificate in agent and transfer that to master for signature.
Hi all, 1)I installed puppet agent in one of the server and i gave the name of the master for which it needs to be connected as puppet. But am unable to connect to the host..the certificate is not present in the master when i searched for it with this command *puppet cert list -all *am getting this error in the master *err: Could not call list: header too long header too long.* ** 2)When am trying to connect through the agent to the master with *puppet agent --test , *am getting host name look up failure..and unable to connect to there.. 3) You can see the result of *puppet agent --test* in this link - * http://192.168.24.171:8080/softwares/connect*http://192.168.24.171:8080/softwares/connect * * 4) You can see the result of *puppet agent --test --debug* in this link -* * *http://192.168.24.171:8080/softwares/debug*http://192.168.24.171:8080/softwares/debug *dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure * this is common in the starting two lines of both the commands Can any one please suggest me a solution for this.. Regards, Ramya Y -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Host name look up failure- unable to generate certificate in agent and transfer that to master for signature.
On Wednesday, 20 March 2013 11:36:30 UTC+5:30, yarlagadda ramya wrote: Hi all, I tried disabling selinux also..i disabled it..but still am getting the same errors. 1)I installed puppet agent in one of the server and i gave the name of the master for which it needs to be connected as puppet. But am unable to connect to the host..the certificate is not present in the master when i searched for it with this command *puppet cert list -all *am getting this error in the master *err: Could not call list: header too long header too long.* ** 2)When am trying to connect through the agent to the master with *puppet agent --test , *am getting host name look up failure..and unable to connect to there.. 3) You can see the result of *puppet agent --test* in this link - * http://192.168.24.171:8080/softwares/connect*http://192.168.24.171:8080/softwares/connect * * 4) You can see the result of *puppet agent --test --debug* in this link -* **http://192.168.24.171:8080/softwares/debug*http://192.168.24.171:8080/softwares/debug *dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure * this is common in the starting two lines of both the commands Can any one please suggest me a solution for this.. Regards, Ramya Y -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Verbose debugging of template variable binding ?
Figured it out - by removing the line 'daemonize %= daemonize %' from the template, the template works as expected. Looks like the variable whose name is deamonize ( %= daemonize %) for some reason does not play nice in a template. Can someone shed some light on reserved variables in templates ~Francis On Tue, Mar 19, 2013 at 11:04 PM, Ellison Marks gty...@gmail.com wrote: If it's working using the declaration from your tests directory, but not from your master, then it stands to reason that either something is wrong with the way you're calling it on the master or something is wrong in your master setup that is causing a communication error. Could you post how you're calling it from your master? On Tuesday, March 19, 2013 6:29:12 AM UTC-7, Francis Pereira wrote: I seem to have made some error in my template but cant seem find a way to debug it except for removing (deleting) parts of the template file and figuring out where there is a mistake. On my puppetmaster with --debug I get the following error debug: template[/etc/puppet/**manifests/lib/redis/templates/**redis.conf.erb]: Bound template variables for /etc/puppet/manifests/lib/**redis/templates/redis.conf.erb in 0.00 seconds On the client I get err: Could not retrieve catalog from remote server: No content type in http response; cannot parse. I am certain that there is something wrong in my template. How do I debug binding of template variables ? Is there a verbose mode that would tell me where the binding breaks ? The template is available at https://github.com/7terminals/** puppet-redis/blob/master/**templates/redis.conf.erbhttps://github.com/7terminals/puppet-redis/blob/master/templates/redis.conf.erband the full module is hosted at https://github.com/7terminals/**puppet-redis/https://github.com/7terminals/puppet-redis/ Ironically, when running in standalone mode i.e puppet apply tests/ini.pp this module/template seems to work. ~Francis -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Host name look up failure- unable to generate certificate in agent and transfer that to master for signature.
Please refrain from multi-posting the same problem. :) -- Krish -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Verbose debugging of template variable binding ?
Looks like this is related to https://projects.puppetlabs.com/issues/9901 I have changed 'daemonize %= daemonize %' to 'daemonize %= @daemonize %' and it seems to work. The variable daemonize seems to collide with Ruby method names as docuimented here http://docs.puppetlabs.com/guides/templating.html Helpful error messages would be nice in these cases ~Francis On Wed, Mar 20, 2013 at 11:39 AM, Francis Pereira francispere...@7terminals.com wrote: Figured it out - by removing the line 'daemonize %= daemonize %' from the template, the template works as expected. Looks like the variable whose name is deamonize ( %= daemonize %) for some reason does not play nice in a template. Can someone shed some light on reserved variables in templates ~Francis On Tue, Mar 19, 2013 at 11:04 PM, Ellison Marks gty...@gmail.com wrote: If it's working using the declaration from your tests directory, but not from your master, then it stands to reason that either something is wrong with the way you're calling it on the master or something is wrong in your master setup that is causing a communication error. Could you post how you're calling it from your master? On Tuesday, March 19, 2013 6:29:12 AM UTC-7, Francis Pereira wrote: I seem to have made some error in my template but cant seem find a way to debug it except for removing (deleting) parts of the template file and figuring out where there is a mistake. On my puppetmaster with --debug I get the following error debug: template[/etc/puppet/**manifests/lib/redis/templates/**redis.conf.erb]: Bound template variables for /etc/puppet/manifests/lib/**redis/templates/redis.conf.erb in 0.00 seconds On the client I get err: Could not retrieve catalog from remote server: No content type in http response; cannot parse. I am certain that there is something wrong in my template. How do I debug binding of template variables ? Is there a verbose mode that would tell me where the binding breaks ? The template is available at https://github.com/7terminals/** puppet-redis/blob/master/**templates/redis.conf.erbhttps://github.com/7terminals/puppet-redis/blob/master/templates/redis.conf.erband the full module is hosted at https://github.com/7terminals/**puppet-redis/https://github.com/7terminals/puppet-redis/ Ironically, when running in standalone mode i.e puppet apply tests/ini.pp this module/template seems to work. ~Francis -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Error: stack level too deep
But I've installed the 0.0.1 and I think that is the only one present and I think the first release In the other installation I have I never found this problem and never bothered which version was installed. Luca 2013/3/19 Peter Meier peter.me...@immerda.ch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The problem is that when I install activerecord-mysql-adapter it automatically install the latest activerectord gem Is there a way to disable it or there is a fix for activerecord gem? Maybe install an older mysql-adapter? ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFIe5AACgkQbwltcAfKi39ycACfQUEnvLIqaoj2LF4vg9YJ3I7r YDsAn0fV13Bd/KeIBf/JLkA1DiAeYfg/ =dRe/ -END PGP SIGNATURE- -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Verbose debugging of template variable binding ?
On 03/20/2013 08:09 AM, Francis Pereira wrote: Looks like this is related to https://projects.puppetlabs.com/issues/9901 I have changed 'daemonize %= daemonize %' to 'daemonize %= @daemonize %' and it seems to work. The variable daemonize seems to collide with Ruby method names as docuimented here http://docs.puppetlabs.com/guides/templating.html Good find! Helpful error messages would be nice in these cases Humm, difficult - the problem originates in the bowels of the erb engine I presume. Calling a daemonize method is not even strictly illegal, so there is likely no exception to catch and process. Perhaps it can be made illegal. I'll take a look at that bug report some time. Cheers, Felix -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Error: stack level too deep
I've compared the others installations of mine and it seems that I do not have installed mysql and activerecord-mysql adapter and all is working so I've removed them and I get the error below: Error: Could not autoload puppet/indirector/catalog/active_record: uninitialized constant ActiveRecord Error: Cached catalog for zabbix.dev.turkey.cloudlabcsi.eu failed: Could not autoload puppet/indirector/catalog/active_record: uninitialized constant ActiveRecord Error: Could not autoload puppet/indirector/facts/active_record: uninitialized constant ActiveRecord Error: Could not autoload puppet/indirector/facts/active_record: uninitialized constant ActiveRecord any hint? Luca 2013/3/20 Luca Gioppo lucagio...@gmail.com But I've installed the 0.0.1 and I think that is the only one present and I think the first release In the other installation I have I never found this problem and never bothered which version was installed. Luca 2013/3/19 Peter Meier peter.me...@immerda.ch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The problem is that when I install activerecord-mysql-adapter it automatically install the latest activerectord gem Is there a way to disable it or there is a fix for activerecord gem? Maybe install an older mysql-adapter? ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFIe5AACgkQbwltcAfKi39ycACfQUEnvLIqaoj2LF4vg9YJ3I7r YDsAn0fV13Bd/KeIBf/JLkA1DiAeYfg/ =dRe/ -END PGP SIGNATURE- -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Error: stack level too deep
I have a puppet dashboard with MySQL and I want to point to that externale store it should be a bit more straitforward !!! (It was) Luca 2013/3/20 Luca Gioppo lucagio...@gmail.com I've compared the others installations of mine and it seems that I do not have installed mysql and activerecord-mysql adapter and all is working so I've removed them and I get the error below: Error: Could not autoload puppet/indirector/catalog/active_record: uninitialized constant ActiveRecord Error: Cached catalog for zabbix.dev.turkey.cloudlabcsi.eu failed: Could not autoload puppet/indirector/catalog/active_record: uninitialized constant ActiveRecord Error: Could not autoload puppet/indirector/facts/active_record: uninitialized constant ActiveRecord Error: Could not autoload puppet/indirector/facts/active_record: uninitialized constant ActiveRecord any hint? Luca 2013/3/20 Luca Gioppo lucagio...@gmail.com But I've installed the 0.0.1 and I think that is the only one present and I think the first release In the other installation I have I never found this problem and never bothered which version was installed. Luca 2013/3/19 Peter Meier peter.me...@immerda.ch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The problem is that when I install activerecord-mysql-adapter it automatically install the latest activerectord gem Is there a way to disable it or there is a fix for activerecord gem? Maybe install an older mysql-adapter? ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFIe5AACgkQbwltcAfKi39ycACfQUEnvLIqaoj2LF4vg9YJ3I7r YDsAn0fV13Bd/KeIBf/JLkA1DiAeYfg/ =dRe/ -END PGP SIGNATURE- -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Windows ACL best practise
Hi Josh, 2013/3/20 Josh Cooper j...@puppetlabs.com S-1-5-18 thanks for the clarification, I wasn't aware that the SIDs are always the same as stated in http://support.microsoft.com/kb/243330. What's about everyone or user, will everyone or user get read-only access when I change the mode to 0775? Multiple groups can't be specified inside the file type, can they? The reference documentation ( http://docs.puppetlabs.com/references/3.1.latest/type.html#file) isn't really clear about this topics ... at least from my point of view ;). Regards Thomas -- Linux ... enjoy the ride! -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
Hello,
Seems that file ressource gets a new idea of what to be given.
I have the following recipe :
class resolvconf {
file {
/etc/resolv.conf:
owner = root,
group = wheel,
mode = 644,
source = puppet:///puppet/dist/resolv.conf,
}
}
When doing puppet agent --test I have this cryptic message :
# puppet agent --test -D
Info: Retrieving plugin
Info: Caching catalog for puppet.local.oav.net
Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
So I went into documentation, but user or target attribute is not the right for
this kind of recipe... Or the documentation is not up to date.
Is there any hint about this new error...
Xavier
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Export a file from one node and collect on another
I'm trying to use Puppet and PuppetDB to export a config file from one node, and collect it on another i.e. export */etc/app1/file1.cfg* from *node a* and collect */etc/app2/file2.cfg*on *node b*. I need the contents of file1.cfg and file2.cfg to be the same, but the paths and file names themselves are different. I cannot centralise this file as it is generated at install time by node a. Is this even possible with Puppet? Although what I am trying to do removes the concept that Puppet should centrally manage and be authoritative for things, but if I can achieve this it would be very helpful. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Correct means to tell if a class is instantiated/defined
Hi, On 03/20/2013 01:37 PM, Kubes wrote: I am using puppet 3.1.1 and I need to know if a class has been defined. I have tried defined() and tagged(), but neither seem to work. They either return true when the class was not include for that node or false please don't. You're making yourself parse order dependent and that *will* bite you at some point down the road. Do not even try. You may get away with declaring a subclass instead, and have class mysql::service include that subclass in order to achieve the necessary modification. Otherwise, your best choice is probably external data, as in hiera. That being said: when it is included. #My understand is NOT to use Class['mysql::service'] How have you come to understand this? I would have thought that Class[] is fine. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
Hi,
what else is in your manifest? Does your node also declare a cron or
ssh_authorized_key resource? Because that would make a lot more sense.
Cheers,
Felix
On 03/20/2013 12:40 PM, Xavier Beaudouin wrote:
Hello,
Seems that file ressource gets a new idea of what to be given.
I have the following recipe :
class resolvconf {
file {
/etc/resolv.conf:
owner = root,
group = wheel,
mode = 644,
source = puppet:///puppet/dist/resolv.conf,
}
}
When doing puppet agent --test I have this cryptic message :
# puppet agent --test -D
Info: Retrieving plugin
Info: Caching catalog for puppet.local.oav.net
Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
So I went into documentation, but user or target attribute is not the right
for this kind of recipe... Or the documentation is not up to date.
Is there any hint about this new error...
Xavier
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Export a file from one node and collect on another
Hi,
you could try something like
@@file { ...: tag = my-exported-file }
and on the receiver end:
File| tag == my-exported-file | {
path = /my/different/path
}
But even if that works, I'm not at all sure how sound it really is.
HTH,
Felix
On 03/20/2013 11:41 AM, Russell Parsloe wrote:
I'm trying to use Puppet and PuppetDB to export a config file from one
node, and collect it on another i.e.
export */etc/app1/file1.cfg* from /node a/ and collect
*/etc/app2/file2.cfg* on /node b/.
I need the contents of file1.cfg and file2.cfg to be the same, but the
paths and file names themselves are different. I cannot centralise this
file as it is generated at install time by node a.
Is this even possible with Puppet? Although what I am trying to do
removes the concept that Puppet should centrally manage and be
authoritative for things, but if I can achieve this it would be very
helpful.
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Windows Reboot
My idea on reboots is different. I don't think we should have puppet do the reboot. If we go down this road, we need autologon, credentials, runonce, and a subsequent puppet agent run among other things. Not ideal if a puppet agent service is running during business time. This is orchestration and not where puppet should not be trying to succeed. Originally I thought I needed a facter fact to determine if a reboot pending state existed, but the problem is that the facts are determined upfront. So if a resource triggers a state where a reboot is needed the fact is busted. I think we need a new embedded construct which can check the reboot state before processing every resource. It has to happen before it makes it to the provider since it should not be left to a provider author as it could apply to any resource. If this boolean goes true then every resource in that graph needs to be skipped. A meta param can be added to say reboot = force which can force a resource to be processed _despite_ the boolean. I also need way to stateful trigger reboot flag like a lockfile so I can do a bios upgrade. Actually _rebooting_ with puppet I am leery of. I welcome all input on 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Correct means to tell if a class is instantiated/defined
Thanks for the response. On Wednesday, March 20, 2013 8:43:00 AM UTC-4, Felix.Frank wrote: Hi, On 03/20/2013 01:37 PM, Kubes wrote: I am using puppet 3.1.1 and I need to know if a class has been defined. I have tried defined() and tagged(), but neither seem to work. They either return true when the class was not include for that node or false please don't. You're making yourself parse order dependent and that *will* bite you at some point down the road. Do not even try. You may get away with declaring a subclass instead, and have class mysql::service include that subclass in order to achieve the necessary modification. I was checking for a subclass mysql::service Otherwise, your best choice is probably external data, as in hiera. Thanks, but I dont understand how heira solve the issues, can you please elaborator a bit for me? I an using heira for storing my user info, but I dont know how to use it to handle if a node is a db server, etc? That being said: when it is included. #My understand is NOT to use Class['mysql::service'] How have you come to understand this? I would have thought that Class[] is fine. Via post on this group and the documentation. Using Resource[] is only needed for resource refferences, as I understand it. http://docs.puppetlabs.com/references/latest/function.html#defined -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: LSB Fact resolution in the absence of -lsb package
On Tuesday, March 19, 2013 2:27:22 PM UTC-5, Wolf Noble wrote:
Hi there,
in house, we rely on the lsb facts:
lsbdistcodename, lsbdistdescription, lsbdistid, lsbdistrelease, and
lsbmajdistrelease
all of which are essentially derived from the
/etc/${distro-specific-release-file} and don't _really_ need the lsb
packages (and the associated bloat) installed.
Well, that's a matter of interpretation. The lsb packages typically ensure
that the system has all the pieces required for compliance with the LSB
specifications, and the facts describe details of the compliance, such as
which version of LSB the system complies with. If your systems are not, in
fact, fully LSB-compliant, then it is of questionable wisdom to suggest
otherwise to Puppet.
I'd like to come up with a good way to allow these facts to exist while
streamlining our systems.
I see a few different approaches, and thought Id ask for community input
on the best solution before just picking a direction and running with it.
If you do not want to require your systems to be fully LSB-compliant, then
your Puppet manifests should not rely on LSB-associated facts. If, on the
other hand, you need to rely on LSB facts, then you should ensure your
systems LSB-compliant. Certainly if you rely on third-party modules that
in turn require LSB-associated facts for correct operation then you have to
assume that your nodes must be LSB-compliant.
John
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Correct means to tell if a class is instantiated/defined
Hi again,
On 03/20/2013 01:56 PM, Kubes wrote:
You may get away with declaring a subclass instead, and have class
mysql::service include that subclass in order to achieve the necessary
modification.
I was checking for a subclass mysql::service
Not really. The class is named mysql::service, but I sincerely hope it
is not inheriting anything.
Point in fact - if you are not yet very keen on inheritance and how it
works, I advise to steer clear for the moment.
Otherwise, your best choice is probably external data, as in hiera.
Thanks, but I dont understand how heira solve the issues, can you please
elaborator a bit for me? I an using heira for storing my user info, but
I dont know how to use it to handle if a node is a db server, etc?
You have it working already? Excellent!
The idea is simple: Introduce a hiera value that, for each node, tells
it whether it is a mysql server or not.
Each last of your nodes can then e.g.
if hiera(mysql-server) == true { include mysql }
It is now trivial to use the same hiera value in other places.
How have you come to understand this? I would have thought that Class[]
is fine.
Via post on this group and the documentation. Using Resource[] is only
needed for resource refferences, as I understand it.
http://docs.puppetlabs.com/references/latest/function.html#defined
Ah, misunderstanding.
defined() will tell you whether the class *exists*, not if this node has
included the class. (At least that's what I make of the documentation).
HTH,
Felix
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] OS specific configuration
Thanks Peter and Brendan, Indeed Facter is what I needed. I worked the case example from here http://docs.puppetlabs.com/learning/variables.html and it seems to be working smooth. Now I understand why it takes so much to run the agent: facter running before fetching catalogs. regards On Tuesday, March 19, 2013 4:53:35 PM UTC+2, Peter Meier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Does Facter need direct connection to clients ? If yes I cannot use it since my clients are behind firewalls/routers. facter runs on the clients before the client asks (with the gathered facts) the master for the catalog. In your manifests you can then use these facts to influence the catalog that is produced for a client. ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFIe+4ACgkQbwltcAfKi3/zkACfbw8W6VG+u8xvEJHtJbQTUrgF 08YAn2fovAp6+gghC7o/yzZuHAwA9O70 =9GL+ -END PGP SIGNATURE- -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Slow user resource-type when host is attached to LDAP directory
On Tuesday, March 19, 2013 12:34:23 PM UTC-5, Josh wrote: The majority of our servers are attached to large LDAP directories. However, there are also cases when we need to define local service accounts for whatever reason. We do this with the user resource-type. If the host is attached to a LDAP directory, it takes Puppet a VERY long time to process the user resource-type. In our case, it takes 60+ seconds to process each user type. Running puppet resource user username on the host takes over 2 minutes. During this time, the puppet process on each hosts is pegged at 100% CPU usage. Is there any way around this? I have seen it brought up on the list, but not anytime recently (2008, last I searched). This sounds like an issue associated more with your hosts' configuration than with Puppet itself. Try running your system's user management commands (for example, useradd / usermod / userdel) directly. I think you will see similar long runtimes. If so, then you cannot attribute your performance problem to Puppet. It is possible that you could improve performance for existing local users by modifying the service priorities in your name service policy to give the local user and group files highest priority (but be aware that this makes local user and group entries supercede LDAP). On common Linuxes that typically means modifying /etc/nsswitch.conf. That's the best I can do without any details of your manifests or target node configurations. John -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] How does puppetlabs-lvm determine if a filesystem is absent?
We had puppet turned off on a host for a few days, and when we turned it back on, we started seeing: (/Stage[setup]/Foo::Filesystems/Filesystem[/dev/data_vg/foo_lv]/ensure) change from absent to present failed: Execution of 'mkfs.ext4 /dev/data_vg/foo_lv' returned 1: mke2fs 1.41.12 (17-May-2010)#012/dev/data_vg/foo_lv is mounted; will not make a filesystem here! It's mounted because there is already I filesystem! I had added another lv by hand, but we never messed with foo_lv. This module is working fine in our prod hosts and other dev host, so I'm not sure what is going on. I've tried to step through the puppet labs-lvm module to see how it determines if a filesystem is absent or present without any luck. Any pointers? -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: User Groups (hadnling undefine groups)
On Tuesday, March 19, 2013 1:01:04 PM UTC-5, Kubes wrote:
I am trying to handle in my user class assigning user to groups, and
handling that some groups might not be defined for that node. Example here
is handling a non-datase node,
juser fails with Error: Failed to apply catalog: Parameter groups
failed on User[juser]: Group names must not be empty. If you want to
specify no groups pass an empty array even in the notice and logs the
correct value (wheel) is logged?
I was inital just planning on passing undef variables, but the dont seems
to undefined (see the second example (hsmith)
Any suggestions on either fixing the empty groups issue ora better
handling groups that are not part of this node would be greatly appreciated.
Thanks
my user class
$default_groups = [ 'wheel' ]
# db_user will be undef and it need to be a empty string
if defined(Class['mysql']) {
$db_group = $mysql::params::group
} else {
$db_group = ''
}
$all_groups = [ $default_groups, $db_group ]
That line is a problem when $db_group has value '', because '' is not a
valid group name. It may also be a problem that $default_groups is an
array. The value of $all_groups ends up being [ ['wheel'], ''], whereas
you want it to be ['wheel']. You could possibly solve the problem by
setting $db_group to an array, either [$mysql::params::group] or [], and
then flattening [ $default_groups, $db_group ] to get the value for
$all_groups. PuppetLabs' 'stdlib' add-in module has a suitable flatten()
function.
While I'm at it, however, the use of defined() in the code fragment
presents an additional, separate problem by making the code parse-order
and/or evaluation-order sensitive. There are pretty much *no* good uses
for defined(), and that is likely to bite you eventually.
John
notice All: ${all_groups} # This logs correctly
Scope(Class[User::Users]) (notice): All: wheel
#fails, but the notice function does correctly log the correct groups
value
@user::virtual{ 'juser': groups = $all_groups }
#fails, even though mysql::params is never include, it is defined...
maybe autoloaded?
@user::virtual{ 'hsmith': groups = [ 'wheel', $mysql::params::group ] }
Here is the virtual class
define user::virtual ( $groups = [] ) {
$user = hiera($title,nil,${environment}/user)
notice Virt: ${groups} #log correcly
Scope(User::Virtual[juser]) (notice): Virt: wheel
user { $title:
ensure= 'present',
uid = $user['uid'],
gid = $title,
groups= $groups, # also tried [ $groups ], same result
shell = '/bin/bash',
home = /home/${title},
comment = $user['comment'],
password = $user['hash'],
managehome= true,
require = Group[$title],
}
...
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
Hi,
My node is declaring (for now) only this classe
node mail01 {
include resolvconf
}
It was working on puppet 2.8 but in 3.0 and 3.1 - now way...
Xavier
Le 20 mars 2013 à 13:44, Felix Frank felix.fr...@alumni.tu-berlin.de a écrit :
Hi,
what else is in your manifest? Does your node also declare a cron or
ssh_authorized_key resource? Because that would make a lot more sense.
Cheers,
Felix
On 03/20/2013 12:40 PM, Xavier Beaudouin wrote:
Hello,
Seems that file ressource gets a new idea of what to be given.
I have the following recipe :
class resolvconf {
file {
/etc/resolv.conf:
owner = root,
group = wheel,
mode = 644,
source = puppet:///puppet/dist/resolv.conf,
}
}
When doing puppet agent --test I have this cryptic message :
# puppet agent --test -D
Info: Retrieving plugin
Info: Caching catalog for puppet.local.oav.net
Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
So I went into documentation, but user or target attribute is not the right
for this kind of recipe... Or the documentation is not up to date.
Is there any hint about this new error...
Xavier
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet always has an exitcode of 0
I am writing a bash script which will run puppet as follows: puppetd --test --env test I need my script to be able to tell if puppet ran successfully, I thought I might be able to do this by checking the exit code ($?) but it seems that regardless of whether the puppet run succeeds or fails it always gives and exit code of 0. for example: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to contact Foreman execution expired at /var/puppet...script.pp on node servername.com warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run [user@servername]# echo $? 0 I read on the puppet documentation web pages that there is a parameter called --detailed-exitcodes which I thought might help but that doesn't work at all: puppetd --test --detailed-exitcodes --env test invalid option: --detailed-exitcodes Try '/usr/sbin/puppetd --help' Am I missing something here, is there any other way for me to tell if puppet failed? Thanks Martin -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet always has an exitcode of 0
On Mar 20, 2013, at 8:00 AM, MartinW mwy...@gmail.com wrote: I read on the puppet documentation web pages that there is a parameter called --detailed-exitcodes which I thought might help but that doesn't work at all: puppetd --test --detailed-exitcodes --env test invalid option: --detailed-exitcodes Try '/usr/sbin/puppetd --help' Am I missing something here, is there any other way for me to tell if puppet failed? Isn't puppetd deprecated in favor of puppet agent? I use --detailed-exitcodes with puppet apply and Puppet 3 and it works like it says on the box. -- Brian Lalor bla...@bravo5.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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet always has an exitcode of 0
Hi, good find. As far as I've learned, --test implies the funny exit codes option, so you likely want to try puppet agent --one-time --nodaemonize. HTH, Felix On 03/20/2013 03:00 PM, MartinW wrote: I read on the puppet documentation web pages that there is a parameter called --detailed-exitcodes which I thought might help but that doesn't work at all: puppetd --test --detailed-exitcodes --env test invalid option: --detailed-exitcodes Try '/usr/sbin/puppetd --help' Am I missing something here, is there any other way for me to tell if puppet failed? Thanks Martin -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
On 03/20/2013 03:11 PM, Xavier Beaudouin wrote:
Hi,
My node is declaring (for now) only this classe
node mail01 {
include resolvconf
}
It was working on puppet 2.8 but in 3.0 and 3.1 - now way...
OK, then I suggest commenting out that include for the time being.
Add a simple 'notify { It works: }' to the node and see if that runs.
If yes, add a simple file resource etc.
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet always has an exitcode of 0
Thanks for the replies. I may have found why --test isn't giving the expected response. puppetd --version 0.25.5 :o - I have no choice but to continue using it as well. Will it be impossible for me to get this working with such an old version? -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet always has an exitcode of 0
On 03/20/2013 03:26 PM, MartinW wrote: Thanks for the replies. I may have found why --test isn't giving the expected response. puppetd --version 0.25.5 Yea, shame on you. :o - I have no choice but to continue using it as well. Will it be impossible for me to get this working with such an old version? The --onetime will do anyway, just replace puppet agent with puppetd. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
Hi,
Le 20 mars 2013 à 15:18, Felix Frank felix.fr...@alumni.tu-berlin.de a écrit :
On 03/20/2013 03:11 PM, Xavier Beaudouin wrote:
Hi,
My node is declaring (for now) only this classe
node mail01 {
include resolvconf
}
It was working on puppet 2.8 but in 3.0 and 3.1 - now way...
OK, then I suggest commenting out that include for the time being.
Add a simple 'notify { It works: }' to the node and see if that runs.
If yes, add a simple file resource etc.
This is what I did :
node.pp :
class resolvconf {
file {
/etc/resolv.conf:
owner = root,
group = wheel,
mode = 0644,
source = puppet:///puppet/dist/resolv.conf,
}
}
node mail01 {
include resolvconf
}
Is it very simple... Now WTF is broken ...
Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
I tryed to use :
user = root
But puppet agent says : Invalid parameter 'user' - ok so the error is bloody
stupdi
When I try to add
target = puppet:///puppet/dist/resolv.conf
I get this stupid error : Error: Failed to apply catalog: You cannot specify
more than one of content, source, target
So does this things want ?
Xavier
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
1. What's in your site.pp then?
2. Please follow the advised steps.
On 03/20/2013 03:44 PM, Xavier Beaudouin wrote:
This is what I did :
node.pp :
class resolvconf {
file {
/etc/resolv.conf:
owner = root,
group = wheel,
mode = 0644,
source = puppet:///puppet/dist/resolv.conf,
}
}
node mail01 {
include resolvconf
}
Is it very simple... Now WTF is broken ...
Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
I tryed to use :
user = root
But puppet agent says : Invalid parameter 'user' - ok so the error is bloody
stupdi
When I try to add
target = puppet:///puppet/dist/resolv.conf
I get this stupid error : Error: Failed to apply catalog: You cannot specify
more than one of content, source, target
So does this things want ?
Xavier
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet always has an exitcode of 0
On Wednesday, March 20, 2013 7:16:17 AM UTC-7, blalor wrote: Isn't puppetd deprecated in favor of puppet agent? I use --detailed-exitcodes with puppet apply and Puppet 3 and it works like it says on the box. huh. never realized there was such a flag. Thanks for that. but really, [return an appropriate exitcode] should be standard, dont you think? Particularly in the case of calling puppet agent /file/does/not/exist and it still returns 0 ? !! Is there a way to force sane exitcode behaviour by default, in puppet.conf? -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
Okay after fighting, seem that my class user that use ssh_authorized_key ressource is giving me this headache. So... I tried some stuff on this : http://pastealacon.com/32000 but I have no clues :( So bad the error is so simple that we can wastes hours just about a wrong class... Xavier -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Problem installing packages dependencies for tarball softwatre
Hi,
I have created a puppuet module to install a software from its source code
as follow:
exec {
'build_opensaf':
cwd = /opt/opensaf-4.2.2,
command = '/opt/opensaf-4.2.2/configure --disable-tipc',
timeout = 0,
logoutput = 'on_failure',
require = Exec[opensaf_extract_installer],
}
exec {
'compile_opensaf':
cwd = /opt/opensaf-4.2.2,
command = 'make',
timeout = 0,
logoutput = 'on_failure',
require = Exec[build_opensaf],
}
exec {
'install_opensaf':
cwd = /opt/opensaf-4.2.2,
command = 'make install',
timeout = 0,
logoutput = 'on_failure',
require = Exec[compile_opensaf],
}
The above code works fine when the prerequisites packages are installed.
But, in the reverse case, I have met a problem of the dependancies packages.
The prerequisites packages are:
- libxml2-dev
- automake
- m4
- autoconf (2.61 or later)
- libtool
- pkg-config
- gcc/g++
- GNU make
- python-dev(el)
Is there someone who can help me to find a solution for installing the
above packages in Ubunutu 12.4 taking into account the two cases: with and
without internet connection. That means if I have internet connection, I
use apt-get install else I use dpkg -i command.
Thanks in advance,
--Ridha
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: LSB Fact resolution in the absence of -lsb package
Hi John,
Thanks for taking the time to respond :) Replies inline.
On Mar 20, 2013, at 8:01 AM, jcbollinger john.bollin...@stjude.org
wrote:
On Tuesday, March 19, 2013 2:27:22 PM UTC-5, Wolf Noble wrote:
Hi there,
in house, we rely on the lsb facts:
lsbdistcodename, lsbdistdescription, lsbdistid, lsbdistrelease, and
lsbmajdistrelease
all of which are essentially derived from the
/etc/${distro-specific-release-file} and don't _really_ need the lsb packages
(and the associated bloat) installed.
Well, that's a matter of interpretation. The lsb packages typically ensure
that the system has all the pieces required for compliance with the LSB
specifications, and the facts describe details of the compliance, such as
which version of LSB the system complies with. If your systems are not, in
fact, fully LSB-compliant, then it is of questionable wisdom to suggest
otherwise to Puppet.
the lsbrelease fact certainly lists what parts of the LSB spec and additional
lsb modules the node is compliant with. I am not suggesting altering the output
of that.
The remainder of the facts seem to consistently correlate with pieces from the
distro specific release file. I've not found a node which does not (although
one may exist).
Looking at the lsb_release script, I see it referencing /etc/lsb-release and
/etc/[distro]-release and returning what it finds.
This enhancement didn't seem too far out of line with what's going on behind
the scenes in the first place.
I'd like to come up with a good way to allow these facts to exist while
streamlining our systems.
I see a few different approaches, and thought Id ask for community input on
the best solution before just picking a direction and running with it.
If you do not want to require your systems to be fully LSB-compliant, then
your Puppet manifests should not rely on LSB-associated facts. If, on the
other hand, you need to rely on LSB facts, then you should ensure your
systems LSB-compliant. Certainly if you rely on third-party modules that in
turn require LSB-associated facts for correct operation then you have to
assume that your nodes must be LSB-compliant.
Well, the motivation behind this is easy collaboration. All my modules really
care about is lsbmajdistrelease and lsbdistid/osfamily/operatingsystem.
Stepping back a bit though, the underlying question is what's the best way to
determine what major version of the OS is running.
lsbmajdistrelease is currently part of core, and one could expect it to exist
on any (linux) node that has puppet installed, unlike a custom site-specific
fact which would work fine for us, but not so well collaboratively.
Expanding the listed lsb facts' functionality to provide the information that
can be derived in the absence of the lsb_release script doesn't seem like an
overstep to me, but I'm happy to concede that there may be a better direction
to go. I'd be equally satisfied (maybe even slightly happier) if
operatingsystemmajrelease was added to current facter to accompany
operatingsystemrelease.
I felt that suggestion might be met with greater resistance, and then there's
the same problem that depending on osfamily can bring for earlier versions,
although that problem is becoming less and less of a concern.
I don't want to resort to a regex every time I looked to see what major version
of $os I'm on. That doesn't seem the most efficient way to go.
I want to remove the requirement for the lsb packages, as that is meeting with
some understandable resistance.
I'm not opposed to refactoring to include a not-yet-existent
operatingsystemmajrelease fact. I want to solve this in a fashion that is …
least likely to bite me or someone else later. :)
Do you still feel expanding lsbdistcodename lsbdistdescription lsbdistid
lsbdistrelease and lsbmajdistrelease (and not touching lsbrelease) is more
likely to lead to problems?
What would you suggest as an alternative?
John
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
This message may contain confidential or privileged information. If you are not
the intended recipient, please advise us immediately and delete this message.
See http://www.datapipe.com/legal/email_disclaimer/ for further information on
confidentiality and the risks of non-secure electronic communication. If you
cannot access these links, please notify us by reply message and we will send
the contents to you.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe
[Puppet Users] Re: How does puppetlabs-lvm determine if a filesystem is absent?
On Mar 20, 2013, at 9:48 AM, Mason Turner opsma...@gmail.com wrote: We had puppet turned off on a host for a few days, and when we turned it back on, we started seeing: (/Stage[setup]/Foo::Filesystems/Filesystem[/dev/data_vg/foo_lv]/ensure) change from absent to present failed: Execution of 'mkfs.ext4 /dev/data_vg/foo_lv' returned 1: mke2fs 1.41.12 (17-May-2010)#012/dev/data_vg/foo_lv is mounted; will not make a filesystem here! It's mounted because there is already I filesystem! I had added another lv by hand, but we never messed with foo_lv. This module is working fine in our prod hosts and other dev host, so I'm not sure what is going on. I've tried to step through the puppet labs-lvm module to see how it determines if a filesystem is absent or present without any luck. Any pointers? To answer my own question: puppet is calling mount -f --guess-fstype PATH_TO_VOLUME for whatever reason, my mount no longer takes '--guess-fstype'. same version as everywhere else, although different checksum. This'll be fun :/ -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Export a file from one node and collect on another
On Wednesday, March 20, 2013 5:41:47 AM UTC-5, Russell Parsloe wrote: I'm trying to use Puppet and PuppetDB to export a config file from one node, and collect it on another i.e. export */etc/app1/file1.cfg* from *node a* and collect * /etc/app2/file2.cfg* on *node b*. I need the contents of file1.cfg and file2.cfg to be the same, but the paths and file names themselves are different. I cannot centralise this file as it is generated at install time by node a. If by generated at install time by node a you mean that a local process running on node a creates the file, then what you are asking for is not Puppet exported resources. Exported resources are a means for the master to record certain declarations made during the compilation of one node's catalog so that they can later be incorporated by reference into other nodes' catalogs. All the necessary details of the resource to be exported must therefore be known to the master -- exported resources do not collect data from clients. If, on the other hand, what you want to do is consistent with Puppet exported resources as I described them, then I think Felix's suggestion of using property overrides at collection time will probably work fine. The only caveat is that you may find that Puppet will not let you declare a physical /etc/app1/file1.cfg on node b because of title collision with the collected resource. John -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Store configuration problem (mysql)
Is strange because the problem began only when I configured the stored with mysql. Before I had configure my puppet master and puppet nodes and the community from these was good (the node applied the class definition on master without ptoblem) I dont have any firewall, selinux or iptables active. From node run telnet to port 8140 and is ok but 8141 sheds error. Thanks. El 20/03/2013 00:52, Ellison Marks gty...@gmail.com escribió: Pro Puppet wouldn't mention puppetdb, as it was written before puppetdb came out. As to your original question, if the puppetmaster service is running, that would probably inhibit you from starting a second one, as the PID file would already be in use. For the client not being able to connect, you need to make sure that the master is listening on the correct port and that your firewall isn't blocking on that port. On Tuesday, March 19, 2013 7:30:34 PM UTC-7, mike wrote: I don't have idea of mysql and backed becoming obsolete. My guide is the book: Pro Puppet, but within the section stored configuration speak about: mysql, postgres, sqlite and oracle and never puppetdb. (Thanks for this tips). Respect whether puppet master is running, yes is ok and the ports is 8140 is available . [……...] [root@puppet ~]# netstat -tlpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 0.0.0.0:33060.0.0.0:* LISTEN 8288/mysqld tcp0 0 0.0.0.0:81400.0.0.0:* LISTEN 15436/ruby tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1120/sshd tcp0 0 :::22 :::* LISTEN 1120/sshd [root@puppet ~]# [root@puppet ~]# service puppetmaster status puppet (pid 15436) is running… [……...] Thanks!! El 19-03-2013, a las 22:13, 尹川 yinchu...@gmail.com escribió: backend -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/oqX3Jr4F_cQ/unsubscribe?hl=en . To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Passing variables from one template to another included template
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So what options do I have in 3.x to address my requirements? Something that would also work on 3.x would be nice. I figured out that I can achieve that with an extended templatewrapper: http://forge.puppetlabs.com/duritong/templatewlv ~pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFKIrQACgkQbwltcAfKi38HlQCcC/QSyb8bYs2EoOzSU+0bNP01 pJAAn1w0L9nUfQQjqaXyBa3uk5TMjWbM =9xo1 -END PGP SIGNATURE- -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Still problem using Chocolatey provider on Windows
As some before me on the group, I have a problem getting the Chocolatey
provider to work on Windows.
I downloaded it from Github and placed it in
/etc/puppetlabs/puppet/modules/chocolatey. (I am running Puppet Enterprise
2.7.19).
On a Windows 8 client, I have a very simple manifest:
class install_notepadplusplus {
if $::osfamily == 'windows {
$pkg = 'notepadplusplus'
package { $pkg:
ensure = installed,
provider = 'chocolatey',
}
}
}
When I run the agent on the client, I get
err: Failed to apply catalog: Parameter provider failed: Invalid package
provider 'chocolatey' at ...
I have pluginsync = true on both master and client which is set by default
using PE.
Any hints will be greatly appreciated.
Werner
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] How to make sure my common module executes before all other ones
I am running puppet 3.1.1 and have a site.pp which roughly looks like this
site.pp:
node basenode {
include common
}
node 'server1' inherits basenode {
include role::appserver
}
node 'server2' inherits basenode {
include role::webserver
}
And my common module includes lots of different types of classes for
creating base directories, adding in users/groups, setting up LDAP,
mcollective, etc.. So my issue is how to make sure that the common module
runs before the roles listed in my node definitions. I know that I could
write out
node 'server1' inherits basenode {
class{'common': } -
class{'role::appserver': }
}
node 'server2' inherits basenode {
class{'common': } -
class{'role::webserver': }
}
but I am trying to think of a better way to do this. Thoughts?
Thanks,
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] What's your hiera tree look like?
On Tue, Mar 19, 2013 at 2:30 PM, Larry Fast lfast1...@gmail.com wrote:
My Hiera tree is turning into a chaotic mess. I'm guessing that my tree
structure is one problem source. So I'm wondering how other real users have
setup hiera. Here are the core problems that are giving me headaches.
I'd be interested in seeing some of these as well. I'm looking for real
world examples of what people are putting in their hierarchies that we
might be able to make better in a hiera 2, which is something that my team
is looking at working on.
# I need to version control my modules separately but hiera data is
monolithic. If I need to change anything anywhere, I need to release a new
version of the whole tree.
Would you like to version the data with the modules, or would you want
something else?
# I can't easily review the final output from hiera within puppet because
the traversal is dependent on facts. I need to feed the facts into Hiera
before I get anything meaningful.
yeah. As long as the data and hierarchy can be dependent on facts, I don't
see any way around that.
# Can't easily compare the config of two different servers. (really the
same as the previous)
Here's my Hiera tree. I'm very interested to know how others deal with
these issues. Does Puppet Enterprise include Hiera mgmt tools?
- %{environment}/%{project}/%{server_env}/%{module_name}
- %{environment}/%{project}/%{server_env}/common
- %{environment}/%{project}/%{role_name}-role/%{module_name}
- %{environment}/%{project}/%{role_name}-role/common
- %{environment}/%{project}/%{module_name}
- %{environment}/%{location}/%{module_name}
- %{environment}/%{module_name}
- %{environment}/common
PE doesn't include any tools for managing hiera, unfortunately. Are you
only using the YAML backend? Or are you using anything else?
NOTES:
Each Environment is a copy of our git repo and includes the hiera tree.
Project, Server_env, Role_name Location are custom facts
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: How does puppetlabs-lvm determine if a filesystem is absent?
You probably need to update puppet-lvm http://forge.puppetlabs.com/puppetlabs/lvm http://projects.puppetlabs.com/issues/19410#change-87203 On Wednesday, March 20, 2013 12:58:35 PM UTC-5, Mason wrote: On Mar 20, 2013, at 9:48 AM, Mason Turner opsm...@gmail.com javascript: wrote: We had puppet turned off on a host for a few days, and when we turned it back on, we started seeing: (/Stage[setup]/Foo::Filesystems/Filesystem[/dev/data_vg/foo_lv]/ensure) change from absent to present failed: Execution of 'mkfs.ext4 /dev/data_vg/foo_lv' returned 1: mke2fs 1.41.12 (17-May-2010)#012/dev/data_vg/foo_lv is mounted; will not make a filesystem here! It's mounted because there is already I filesystem! I had added another lv by hand, but we never messed with foo_lv. This module is working fine in our prod hosts and other dev host, so I'm not sure what is going on. I've tried to step through the puppet labs-lvm module to see how it determines if a filesystem is absent or present without any luck. Any pointers? To answer my own question: puppet is calling mount -f --guess-fstype PATH_TO_VOLUME for whatever reason, my mount no longer takes '--guess-fstype'. same version as everywhere else, although different checksum. This'll be fun :/ -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] How to make sure my common module executes before all other ones
Hi Chris,
Take a look at run stages
http://docs.puppetlabs.com/guides/language_guide.html#stages
They make it a little easier to perform some coarse ordering.
additionally, you can use PuppetLabs stdlib module and take advantage of the
anchor pattern sparingly.
Here's a good example of its use:
https://github.com/adrienthebo/puppetlabs-mrepo/blob/master/manifests/init.pp
Hope that helps!
W
On Mar 20, 2013, at 5:04 PM, Chris Handy chrisjha...@gmail.com
wrote:
I am running puppet 3.1.1 and have a site.pp which roughly looks like this
site.pp:
node basenode {
include common
}
node 'server1' inherits basenode {
include role::appserver
}
node 'server2' inherits basenode {
include role::webserver
}
And my common module includes lots of different types of classes for creating
base directories, adding in users/groups, setting up LDAP, mcollective, etc..
So my issue is how to make sure that the common module runs before the roles
listed in my node definitions. I know that I could write out
node 'server1' inherits basenode {
class{'common': } -
class{'role::appserver': }
}
node 'server2' inherits basenode {
class{'common': } -
class{'role::webserver': }
}
but I am trying to think of a better way to do this. Thoughts?
Thanks,
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
This message may contain confidential or privileged information. If you are not
the intended recipient, please advise us immediately and delete this message.
See http://www.datapipe.com/legal/email_disclaimer/ for further information on
confidentiality and the risks of non-secure electronic communication. If you
cannot access these links, please notify us by reply message and we will send
the contents to you.
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] How does puppetlabs-lvm determine if a filesystem is absent?
Great, thank you! On Mar 20, 2013, at 6:38 PM, Chuck cssc...@gmail.com wrote: You probably need to update puppet-lvm http://forge.puppetlabs.com/puppetlabs/lvm http://projects.puppetlabs.com/issues/19410#change-87203 On Wednesday, March 20, 2013 12:58:35 PM UTC-5, Mason wrote: On Mar 20, 2013, at 9:48 AM, Mason Turner opsm...@gmail.com wrote: We had puppet turned off on a host for a few days, and when we turned it back on, we started seeing: (/Stage[setup]/Foo::Filesystems/Filesystem[/dev/data_vg/foo_lv]/ensure) change from absent to present failed: Execution of 'mkfs.ext4 /dev/data_vg/foo_lv' returned 1: mke2fs 1.41.12 (17-May-2010)#012/dev/data_vg/foo_lv is mounted; will not make a filesystem here! It's mounted because there is already I filesystem! I had added another lv by hand, but we never messed with foo_lv. This module is working fine in our prod hosts and other dev host, so I'm not sure what is going on. I've tried to step through the puppet labs-lvm module to see how it determines if a filesystem is absent or present without any luck. Any pointers? To answer my own question: puppet is calling mount -f --guess-fstype PATH_TO_VOLUME for whatever reason, my mount no longer takes '--guess-fstype'. same version as everywhere else, although different checksum. This'll be fun :/ -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Host name lookup failure
You need to reboot for selinux to be disabled. Try setenforce permissive to switch off enforcing mode. On 20 March 2013 15:28, yarlagadda ramya rams.15...@gmail.com wrote: Hi krish, I also tried modifying SELINUX=disabled in /etc/selinux/config but its of no use..it dint get disabled Regards, Ramya Y On Wednesday, 20 March 2013 10:29:17 UTC+5:30, yarlagadda ramya wrote: Hi.. I tried to disable selinux but it dint worked...it is enabled..only... I used this command to check whether it is enabled or diabled - selinuxenabled echo enabled || echo disabled As u said to disable it, i tried to do it...using this command - echo 0 /selinux/enforce but itis not working... please check it out... Regards Ramya Y On Monday, 18 March 2013 20:16:20 UTC+5:30, krish wrote: On Mon, Mar 18, 2013 at 6:24 PM, yarlagadda ramya rams@gmail.comwrote: Hi krish.. Am able to reach the master through user..and am mentioning down the debugging results..please do help me in getting a solution.. dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure debug: Failed to load library 'selinux' for feature 'selinux' Holy carp... can you use pastebin/pastie next time!!! Anyway, please try disabling selinux and then clearing certs from master and agent and try to req cert again. And what is that lookup failed? :) Should tell you something. -- Krish -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Problem installing packages dependencies for tarball softwatre
There is any help to solve the problem of dependencies in puppet?
Regards,
--Ridha
On Wednesday, March 20, 2013 12:35:25 PM UTC-4, ridha gadhgadhi wrote:
Hi,
I have created a puppuet module to install a software from its source code
as follow:
exec {
'build_opensaf':
cwd = /opt/opensaf-4.2.2,
command = '/opt/opensaf-4.2.2/configure --disable-tipc',
timeout = 0,
logoutput = 'on_failure',
require = Exec[opensaf_extract_installer],
}
exec {
'compile_opensaf':
cwd = /opt/opensaf-4.2.2,
command = 'make',
timeout = 0,
logoutput = 'on_failure',
require = Exec[build_opensaf],
}
exec {
'install_opensaf':
cwd = /opt/opensaf-4.2.2,
command = 'make install',
timeout = 0,
logoutput = 'on_failure',
require = Exec[compile_opensaf],
}
The above code works fine when the prerequisites packages are installed.
But, in the reverse case, I have met a problem of the dependancies packages.
The prerequisites packages are:
- libxml2-dev
- automake
- m4
- autoconf (2.61 or later)
- libtool
- pkg-config
- gcc/g++
- GNU make
- python-dev(el)
Is there someone who can help me to find a solution for installing the
above packages in Ubunutu 12.4 taking into account the two cases: with and
without internet connection. That means if I have internet connection, I
use apt-get install else I use dpkg -i command.
Thanks in advance,
--Ridha
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Windows Reboot
Hi Josh, As you may recall, I'm the odd kid on the block using Puppet to manage many many embedded Windows 7 and XP devices, so my needs are probably not very representative of the Puppet community. I have no need for a reboot message/code. Most our devices already have a nightly scheduled reboot. I use run stages and a delayed shutdown to, for all practical purposes, ensure a resource that requires a reboot runs last and give the agent enough time to cleanly finish the run and send reports back. I also use a schedule resource to control when devices are allowed to apply a resource that requires a reboot. I'll check out your reboot provider, thanks. I just use an exec currently. Regards, Adam On Tuesday, March 19, 2013 11:42:19 PM UTC-5, Josh Cooper wrote: On Monday, March 11, 2013, ad wrote: James, Not yet, see http://projects.puppetlabs.com/issues/19162. My (ugly) approach for this now is a refreshonly exec with a delayed shutdown. I'd like to see a reboot = true or such for all resources that tell the agent to reboot after a run is complete when that resource is applied. I did something similar, reboot resource type that is only triggered via notify/subscribe relationship from another resource. See https://github.com/joshcooper/puppetlabs-reboot Adam, I'm curious about the approach you're talking about also. If reboot was a metaparameter, I don't think it would be possible to specify the reboot message or reason code (for different resources) But perhaps that's not really important? Adam On Monday, March 11, 2013 6:55:46 AM UTC-5, jim wrote: Hi Guys I'm using puppet for my windows configuration, and was wondering when installing / configuration something windowys, it requires a reboot, how does this effect the puppet run e.g. join to domain ? e.g. removing old version of software e.g. host re-name Is there options you can tell puppet its going to reboot and to finish that puppet run upon restart Regards James -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- Josh Cooper Developer, Puppet Labs -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
