Peter K:
What version of the module are you using? On the forge is 1.1.0
If that is the case you will need to include ::ssh::server (You can do this
using roles and profiles)
This link to Gary Larizza will help you understand what they are and how to
do them - http://garylarizza.com/blog/2014/0
Good Morning:
I've started using puppetlabs/splunk module and I'm having a Dependency
Cycle Issue. Can someone help
Error: Could not apply complete catalog: Found 1 dependency cycle:
(File[/opt/staging/splunk/splunkforwarder-6.3.3-f44afce176d0-linux-2.6-x86_64.rpm]
=> Staging::File[splunkforwa
Ok...so I'm trying to get the puppetlabs/splunk module to work with Roles
and Profiles via Hiera. This is what I have.
*hieradata file*
splunk::params::version: '6.3.3'
splunk::params::build: 'f44afce176d0'
splunk::params::src_root: 'puppet:///software/splunk' <- Mapped on
Puppetmaster using f
Thanks everyone for the suggestionsFelix thank you for reminding me of
the --debug on the end of a puppet run. This allowed me to find in php.ini
that a developer added an extension line of code that is handled else where.
RESOLVED!
On Tuesday, February 9, 2016 at 3:51:09 PM UTC-5, Joseph
Hello All:
I started getting failed resources from augeas and I'm hoping someone can
help.
The errors:
Warning: Augeas[php_ini-php-error_reporting](provider=augeas): Loading
failed for one or more files, see debug for /augeas//error output
Error:
/Stage[main]/Oit_php::Augeas/Php::Augeas[php-e
Hello Sergiu:
The Puppet Labs MySQL Module creates the sql statements and runs them
against the mysql server, but does not maintain them persistently. So to
remove a database run the following
mysql -u -p -h -e "DROP DATABASE "
Thanks
Joey
On Thursday, December 10, 2015 at 9:20:46 AM UTC-5,
Hello Martin:
To enforce declaration you should be able to do
onevnet_addressrange { '':
ensure => present,
require => Onevnet['testnet'],
....
}
Thanks
Joseph Karns
--
You received this message because you are subscribed to the Google Groups
"Puppet Us
reach out to myself if you have any questions on setting any of the
pieces up.
Thanks
Joseph Karns
jm...@psu.edu
--
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, sen
the module’s documentation i see:
>> default_vhost
>>
>> Sets up a default virtual host. Defaults to 'true', set to 'false' to set
>> up customized virtual hosts
>> <https://forge.puppetlabs.com/puppetlabs/apache#configure-a-virtual-host>
>&
Hello Latina:
on your line where you have include apache, change to something like this
class{ 'apache':
default_mods => true,
default_vhost => false,
default_ssl_vhost => false,
}
This will trigger the apache class and allow you to pass param's to it.
Thanks
Joseph
On Sunday, April 1
Leam:
Can you reply with your code up too this point. Please include your heira
file, so I can see the hash.
Thanks
Joey
On Wednesday, February 11, 2015 at 4:49:38 PM UTC-5, leam hall wrote:
>
> On Wed, Feb 11, 2015 at 4:18 PM, Joseph Karns > wrote:
> > Hello Leam:
> &
Hello Leam:
I think your looking for something like this:
-
define sysusers::setup(
$hash
) {
case $::osfamily {
'redhat': {
$user_home = '/home'
}
'solaris': {
$user_home = '/export/home'
}
Leam:
The reason you are getting the 400 Error is because you don't have
$osfamily defined.
You can write your case statement as such:
case $::osfamily {
'redhat': {
# do something RHEL specific
}
'debian': {
# do something Debian specific
}
default: {
# ...
}
Hello Lean:
The way to handle this the best is exactly what you did. OS level
specifications should be made at the module level.
I have seen some try to handle mixed environments with the heira hierarchy, but
this makes the modules you build less portable. you would also need to create
multipl
Hello Aries:
The root user would execute this or standard user using sudo.
This also depends on how its run. If ran during a Kickstart it would be run
by the root user.
If you setup the machine, then ssh into the server, it would be run by your
user you ssh'd into the box with. If that is the c
ll its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/be07cc95-df74-43a9-be3d-1ff754dbf46e%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/be07cc95-
Hello Aries:
Puppet Enterprise provides a single line command to complete the same
thing. It would look something like this, "curl -k https://:8140/packages/current/install.bash | sudo bash"
You could add that to a cloud_init file if using AWS or add it to a
kickstart file for local OS loading.
Hello Tim:
Just like you would when manually adding a cronjob you should have '*/30',
so your resource should look like this.
cron { "facts-cron":
command => "/usr/bin/facter -y > /etc/mcollective/facts.yaml",
user=> 'root',
hour=> 0,
minute => '*/30'
}
Hope this helps!
Joey
18 matches
Mail list logo
