Is it possible to use a Service resource, but not have puppet start or
start the service? I want to declare service resources so that I can
easily make sure that puppet will restart them when packages are
upgraded, etc., but I do not want puppet to restart them if a sysadmin
shuts the down for some
Is there a way to shutdown a running service before a package is
upgraded? This seems like a pretty basic thing to do, but I can't
figure it out.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@g
The package I am trying to update is running under monit, which will
start it back up if not shut down via monit, which the package itself
cannot do. Is there a recommended way to handle this sort of
situation?
-Byron
On Nov 16, 5:35 pm, Daniel Pittman wrote:
> byron appelt writes:
>
I am using a fact inside of a template. The problem I am running into
is that the bootstrap run of puppet fails with the following error:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Failed to parse template base_gateway/ublip_gw.monitrc.erb:
Could not find value for 'g
on subsequent runs.
Here is the fact, in case it is relevant:
Facter.add("gw_init_script_exists") do
setcode do
FileTest.exist?("/etc/init.d/ublipgw.sh")
end
end
On Nov 17, 8:48 pm, Nigel Kersten wrote:
> On Wed, Nov 17, 2010 at 1:05 PM, byron appelt wrote:
>
problem.
-Byron
On Nov 18, 10:59 am, Nigel Kersten wrote:
> On Thu, Nov 18, 2010 at 6:46 AM, byron appelt wrote:
> > I am delivering the fact with pluginsync, but that will not have
> > occurred yet on bootstrap because puppet has yet to run for the first
> > time and del
well now.
Thanks for all your help Nigel, I would not have figured it out alone.
-Byron
On Nov 18, 1:03 pm, Nigel Kersten wrote:
> On Thu, Nov 18, 2010 at 10:04 AM, byron appelt wrote:
> > I'm sure I don't understand something here, but when I look at the
> > value of the
I am trying to use the package class to manage a gem and I need to
specify the source. I tried doing the following:
package { "gateway_install_support":
ensure => installed,
provider => gem,
source => "http://gems.ublip.com:8808";,
require => Exec["ruby setup.rb"]
}
but this cau
Answering my own question here. As it turns out, the source parameter
does work as I was expecting it to, but only in puppet versions 0.24.5
and greater. I was trying with 0.24.4.
On Dec 24, 1:00 pm, byron appelt wrote:
> I am trying to use the package class to manage agemand I need to
> s
I am trying to get a custom fact to sync and have tried just about
everything. I am trying to follow this:
http://reductivelabs.com/trac/puppet/wiki/PluginsInModules
I have put my custom fact in /etc/puppet-dev/manifests/classes/custom/
lib/facter
puppet.conf on my puppetmaster looks like this
there is no idea where to find them?
>
> Thanks,
> derek
>
> On 2/4/10 10:06 AM, byron appelt wrote:
>>
>> I am trying to get a custom fact to sync and have tried just about
>> everything. I am trying to follow this:
>>
>> http://reductivelabs.com/trac/
I have been running puppet v0.24.5 installed via a debian package on
Ubuntu. I am trying to upgrade to 0.25.4 installed via rubygem. Now
when I try to run it I get the following error:
(Puppet::Error)puppet.conf:[main]ings.rb:1028:in `parse_file': Could
not match line [main]
from /usr/lib/
I am trying to get a custom fact to sync. The fact is in a module. It
will sync if I run puppet with "--pluginsync" but not otherwise. I
have "pluginsync=true" in my puppet.conf. Shouldn't the command line
option and puppet.conf option have the same results?
--
You received this message because y
and sync works fine.
>
> Can you post your full configuration? Both client and server? Can you
> confirm your other settings are working when you adjust them in
> puppet.conf?
>
> On Apr 5, 10:43 pm, byron appelt wrote:
>
> > I am trying to get a custom fact to sync. The fact
I found the problem. My puppet.conf somehow got checked into SVN with
CR/LF line endings. Apparently this causes puppet to fail to read it,
quite silently even with --debug unfortunately.
On Apr 6, 11:59 am, byron appelt wrote:
> Thanks, testing other settings was an excellent suggestion.
is already an open ticket here:
>
> http://projects.puppetlabs.com/issues/3119
>
> ken.
>
> On Apr 6, 9:52 pm, byron appelt wrote:
>
> > I found the problem. My puppet.conf somehow got checked into SVN with
> > CR/LF line endings. Apparently this causes puppet to fail to re
I have just made my first attempt at using a module from puppetforge,
so this is probably a newbie question.
I used the puppet module tool to grab the camptocamp-apt module, it
created a directory called "camptocamp-apt" with the structure
expected for a module.
However, the only way I could get
I have the following code:
class numerex_ruby::mysql_gem {
include numerex_common_packages
Package['libmysqlclient-dev'] -> Package['mysql_gem']
package { 'mysql':
ensure => '2.8.1',
provider => gem,
alias => 'mysql_gem',
}
}
Which results in an erro
I have an application package that needs to be installed on certain
application servers but before it can be installed, database access has to
be setup on a database server.
I have figured out how to export a resource on the app server that gets
collected and realized on the database server, b
I want to recursively set the mode of files in a directory to '0750' but
set the permissions of the directory itself to '2750'. I cannot figure out
a way to accomplish this. Is it possible?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To un
I am trying to use puppet to create and manage mysql instances running
under Ubuntu, probably using the puppetlabs-mysql module.
I am running into the issue that if you change the innodb_log_file_size
parameter, mysql will complain and fail to start unless you delete the
existing ib_logfiles be
21 matches
Mail list logo
