Hi,
I did fork the repo and submitted a pull request but I don't think it
has been merged yet.
My for is here if that helps. https://github.com/rendhalver/puppetlabs-apache
I have been pretty busy lately and I haven't had a chance to chase up
what is happening.
On 24 July 2013 00:09, Pawel Tomu
I installed Cygwin on some Windows 7 x64 client nodes (v3.2.3) and was in
the process of removing it. Because I cannot modify CIFS/SAMBA shares or
change the puppet service to run as a domain user, I'm basically reduced to
getting the installers for each package on the machine prior to installi
On Wednesday, 24 July 2013 03:12:10 UTC+10, Ellison Marks wrote:
>
> How are you running puppet? If cron or mcollective, you can add a --noop
> flag to the command line somewhere.
>
We're just using it the standard way running it as a daemon
--
You received this message because you are subsc
So that log looks like the Apache log... Do you have your
puppetmaster logging to syslog as well? There should be more than
just the "GET" lines from Apache. I think when you turn on --debug it
will increase the normal logging of the puppetmaster to syslog. That
is where you should see lines re
On Tue, Jul 23, 2013 at 4:58 PM, Steven Nemetz wrote:
>
> configtimeout = 900
>
> The number is in seconds. Set it to whatever you're comfortable with
>
>
>
Thank you! That fixed it. Now I can go on to fix all the mistakes in the
module I got from the forge.
--
Peter L. Berghold
I apologise, and have though this through, and it was a silly question.
This isn't a Puppet problem at all. And sorry for the horrible script. Got
a much nicer one now (using defines).
Sorry for the noise.
Tim
ps:
- I can either modify the startup service script
- add the var to /etc/environm
Catalog generation took too long. Could be the puppet master is overloaded are
just the puppet module code used. You can increase the timeout on the agents.
On the agent in puppet.conf under the agent section add
configtimeout = 900
The number is in seconds. Set it to whatever you're comfor
Hi All,
I have been searching around for a few hours now, but don't seem to be
using the correct search terms for the answer I need. So please forgive me
if this is a question that has been answered 100 times :( I have seen many
questions regarding enviroment variables, but non seem to be relat
Just added a bunch of forge modules to my mix. If I run from my puppet
master things go OK. Running from another server this is what things look
like:
# time puppet agent --test --debug
Debug: Failed to load library 'selinux' for feature 'selinux'
Debug: Using settings: adding file resource 'run
When I try to connect a new client to this problematic Puppet Master,
here's what I see in the log:
10.103.0.3 - - [23/Jul/2013:15:15:27 -0400] "GET
/production/certificate/ca? HTTP/1.1" 200 1915 "-" "-"
10.103.0.3 - - [23/Jul/2013:15:15:27 -0400] "GET
/production/certificate/new-server.domain.
I'm trying to use a puppet manifest to set up a series of backup jobs on
servers which are each running a variety of mysql databases. My manifest
currently looks something like this, which almost works:
class backups () {
Cron {
ensure => present,
user => root,
}
$r
How are you running puppet? If cron or mcollective, you can add a --noop
flag to the command line somewhere.
On Monday, July 22, 2013 4:29:24 PM UTC-7, Sam Morrison wrote:
>
> I'm trying to set a global noop but it doesn't seem possible,
>
> There are 2 bugs open about this which to me look prett
Hi Timu,
On Tue, Jul 23, 2013 at 3:51 AM, tinu wrote:
> This manifest get the error above.
>
> class services::scomagent (
> $install_source = 'puppet:///modules/services/MOMAgent.msi',
> $msi_source = 'C:\Install\MOMAgent.msi',
> $msi_install_dir = '"C:\\Program Files\\System Cente
Hi,
got the whole list
root@ip-10-55-86-66:/home/ubuntu# gem list
*** LOCAL GEMS ***
builder (3.2.2)
excon (0.25.3)
fog (1.14.0)
formatador (0.2.4)
guid (0.1.1)
mime-types (1.23)
mini_portile (0.5.1)
minitest (1.6.0)
multi_json (1.7.7)
net-scp (1.1.2)
net-ssh (2.6.8)
nokogiri (1.6.0)
rake (0.8.
What is the version of Fog you have ?
When you do "Puppet Help" do you see an exclamation mark next to node_aws ?
On Tuesday, 23 July 2013 16:16:19 UTC+1, Piotr Jasiulewicz wrote:
>
> Hi,
>
> yeap, it;s installed allright:
>
> root@X:/home/ubuntu# gem install guid
> Successfully installed guid-0
It's likely the powershell execution policy that you were seeing errors due
to.
--
Rob Reynolds
Developer, Puppet Labs
*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Final Countdown discount - save
15%!*
On Tue,
Hi,
yeap, it;s installed allright:
root@X:/home/ubuntu# gem install guid
Successfully installed guid-0.1.1
1 gem installed
Installing ri documentation for guid-0.1.1...
Installing RDoc documentation for guid-0.1.1...
getting this every time, not sure if that's correct.
Maybe the version is wron
Did you install guid ?
On Tuesday, 23 July 2013 11:03:14 UTC+1, Piotr Jasiulewicz wrote:
>
> Hi everyone!
>
>
> having a slight problem with the installing the cloud provisioning module
> [code]
> http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html
> [/code]
> everything worked until
You are relying on the functionality of 'yum' to pull in the dependencies,
which is a shortcut, and this is the kind of problem such shortcuts bring.
You should be making new puppet modules for each of the dependencies, and
have the zend package 'require' all of those modules. You can update the
Pete,
do you have any info regarding 2.4 support? Have you been successful with
creating the fork mentioned?
I'm playing with FreeBSD (9.x+) support and wish to have apache 2.4 at once.
W dniu wtorek, 12 lutego 2013 07:19:00 UTC+1 użytkownik Pete napisał:
>
> Just letting people know I have mad
hi,
im trying to update the zend server package the following way:
package { "zend-server-php-5.4-6.1.0:
ensure => present,
require => [Yumrepo["ZendRepo"],Yumrepo["Zend_noarch"]],
notify => File["/etc/ld.so.conf.d/zend_server.conf"]
}
when i install a node from scratch, the lat
Hi,
hope anyone from the establishment will read this.
Wanted to report an issue on puppet cloud provisioning (that does not
install properly) but unfortunately my password that I just wrote
on https://projects.puppetlabs.com doesn work, nor does the password
recovery ...
Thanks,
Piotr
--
Y
Hi,
I think require=>Class[...] works only for class files in module, it does
not work for modules.
You can try this:
node "server.my.fqdn" {
stage{ 'first': }
stage{ 'second': }
Stage[first]->Stage[second]
class { "puppet_agent":
stage => first,
}
I've had many nagios_servicedependency declarations in my manifests for
ages. This morning I added 'target' parameters to these blocks, like this:
@@nagios_servicedependency { "check_uptime_${::fqdn}":
host_name => $::fqdn,
dependent_host_name => $::fqdn,
Hi everyone,
I'm stuck with this error trying to set up inspection reports :
Could not send report: Error 400 on SERVER: Could not intern from yaml:
undefined method `intern' for nil:NilClass
Earlier, I had this one :
Could not run: Could not find catalog for hostname
That I fixed with : c
This manifest get the error above.
class services::scomagent (
$install_source = 'puppet:///modules/services/MOMAgent.msi',
$msi_source = 'C:\Install\MOMAgent.msi',
$msi_install_dir = '"C:\\Program Files\\System Center Operations
Manager 2007"',
$msi_package_name = "System Center
I configured it to use my account and it started working without errors..
probably I did not try this one before...
what kind of configuration could the other account miss? maybe the .net
framework?
anyway thank you for your systematic debugging :D
Il giorno lunedì 22 luglio 2013 16:51:35 UTC+2
Hi everyone!
having a slight problem with the installing the cloud provisioning module
[code]
http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html
[/code]
everything worked until I wanted to actually try to fire it up:
[code]
>puppet node_aws list
Error: Could not autoload puppet/fa
Den mandag den 22. juli 2013 08.58.32 UTC+2 skrev George Brown:
>
> Hi Sneha,
>
> This is for a GPFS (IBM parallel file system) cluster. When a new client
> is added it needs to be added by an node that is already part of the
> cluster. I'm trying to automate this through puppet
>
> E.g. node80
Hi Jacov,
stage is a meta-attribute which you can use when declaring a class.
You added the stage attribute to the class definition.
You can change your code to look like the following:
class yum::repo::pgdg92 (
$exclude = []
) {
…
}
Afterwards you use the stage attribute in the class declara
On 23/07/13 02:50, Pete Brown wrote:
I find it best to not use a target for the nagios resources.
The provider is only able to delete them if you use the default locations.
Yes, I'm aware of the limitations and have avoided setting the target
until now. Unfortunately our Nagios config is so la
Hi Matthew,
Thanks for your response. I know your approach will work, but I'm
reluctant to go through my manifests and change every reference to
nagios_* to include a 'target' parameter. It's not only an effort to
change now, but I also have to remember to add a 'target' every time I
add Nagi
Hi,
I'm currently trying to debug a performance issue I'm having. Therefore I
would need "DEBUG" output. When using one puppetmaster process, this is
fairly easy by starting it like this:
> puppet master --no-daemonize --debug
Now I need to see this debug output when running puppetmaster th
33 matches
Mail list logo
