The quick way is to apply a pair of exec resources on the client machine:
- One that downloads the sql file and the other one (that requires the first
one) that applies it.
Something like:
exec {
Retrieve $url:
cwd = $work_dir,
command = wget $url,
Personally I don't think using puppet for this would not be the best
solution. However here is what I would do. Write a shell script to do what
you need, and than use puppet's EXEC statement to launch this command as
needed.
You could also use custom Fact for this.
For instance have you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
same problem for me.. I've notice the problem on modules using
autoloading...
I think I will stick to version 2.6.9...
can you at least file a detailed bug report? Thanks! Otherwise the
situation can't be really improved...
~pete
-BEGIN PGP
Hi,
Maybe I'm going nuts, but I could have sworn reading about a trick or
new feature which allowed to have a definition parameter get a default
value of the definition's own $title (instead of having the hack around
the limitation with selectors and intermediate variables later on).
Basically
- Original Message -
Hi,
Maybe I'm going nuts, but I could have sworn reading about a trick or
new feature which allowed to have a definition parameter get a
default value of the definition's own $title (instead of having the hack
around the limitation with selectors and
R.I.Pienaar wrote :
Maybe I'm going nuts, but I could have sworn reading about a trick or
new feature which allowed to have a definition parameter get a
default value of the definition's own $title (instead of having the hack
around the limitation with selectors and intermediate variables
On Jul 14, 2011, at 4:01 PM, Craig White wrote:
same user/password as I have configured in puppet.conf
It does happen to work if I comment out the username password
It doesn't work even if I use rootbinddn and rootbinddn password
Well, then it’s probably a bug in Puppet or (more likely)
On Jul 14, 6:48 pm, Darrell Fuhriman darr...@garnix.org wrote:
[...]
So your scenario wouldn't affect me anyway. But I'm anal-rententive that way.
I can't imagine why you *wouldn't* do that if you're going to be running on
more than one platform.
It's fine to *wish* for a feature that
On Jul 14, 11:57 am, PBWebGuy pbweb...@gmail.com wrote:
You bring up a good point and I wanted to ask this question anyways.
To the best of my knowledge, functions run on the master and facts run
on the node. If that is the case, it perplexes me that functions get
sync'd to the node in the
- Original Message -
On Jul 14, 11:57 am, PBWebGuy pbweb...@gmail.com wrote:
You bring up a good point and I wanted to ask this question
anyways.
To the best of my knowledge, functions run on the master and facts
run
on the node. If that is the case, it perplexes me that
Did anyone ever post a bug, or find a solution for this? I've just upgraded
some of our Solaris boxes (using OpenCSW) to 2.6.9 and I'm seeing the same
behaviour.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the
After I ran that manifest, with this only
#Package to install
package { 'Bindscript20100601.dmg':
provider= pkgdmg,
ensure = installed,
source = '/etc/puppet/bindscript/files/
Bindscript20100601.dmg',
I am now receiving these errors and on the second error,
Bindscript.dmg
the errors are:
err: //Package[Bindscript20100601.dmg]/ensure: change from absent to
present failed: Execution of '/usr/bin/hdiutil mount -plist -nobrowse -
readonly -noidme -mountrandom /tmp /Users/vella1tj/Desktop/
Bindscript2010601.dmg' returned 1: hdiutil: mount failed - Resource
temporarily
I've been using:
scope.lookupvar('puppet::params::certdnsnames')
On Thu, Jul 14, 2011 at 8:45 PM, lurdan lur...@gmail.com wrote:
hi,
What's the best way to refer variables which pass as defined resource
parameter
from template erbs?
I've been made many modules which has resource
Justin,
What would the syntax be along those lines when looking up custom facts?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/BB3TAoW6PVEJ.
To post to
try commenting out the line genconfig in puppet.conf
Craig
On Jul 14, 2011, at 5:05 PM, Anton wrote:
Hello
Im following this guide
http://aaronwalrath.wordpress.com/2010/09/03/installing-and-configuring-puppet-on-centos-linux/
(running centos 5.6). But when i try puppetmasterd --verbose
OK, I think this is probably something that is entirely my fault, but I
cannot access a facter fact that I need. It evaluates only on certain
clients, and is dependent upon the creation and value of another fact.
Client and server are puppet 2.6.6 and facter 1.5.9.
Custom fact defined in
Yes Marek, it does make sense and thanks for this help, lemme try what
Al @ Lab42 has suggested first as I have been told to do things by
Puppet. In case I fail then I will look in to your suggestion.
Thanks anyways
On Jul 14, 11:43 pm, Marek Dohojda chro...@gmail.com wrote:
Personally I don't
done!
http://projects.puppetlabs.com/issues/8433
Gus
On Fri, Jul 15, 2011 at 7:59 AM, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
same problem for me.. I've notice the problem on modules using
autoloading...
I think I will stick to version
Hey
Thanks for the help, I was able to download the dump file successfully
but when I try to execute the mysql command I get the following error:
Could not run Puppet configuration client: 'mysql -uroot -pring
parasol download.php?i=hV0wsTfa' is both unqualifed and specified no
search path at
On Fri, Jul 15, 2011 at 10:37 AM, newguy aimanparv...@gmail.com wrote:
Hey
Thanks for the help, I was able to download the dump file successfully
but when I try to execute the mysql command I get the following error:
Could not run Puppet configuration client: 'mysql -uroot -pring
parasol
Facts are top scope, so simply ::factname such as
scope.lookupvar('::operatingsystem')
On Fri, Jul 15, 2011 at 8:26 AM, Greg Etling getl...@stern.nyu.edu wrote:
Justin,
What would the syntax be along those lines when looking up custom facts?
--
You received this message because you are
Nan, that's exactly what I thought. I posted another thread with more
details on the issue I'm seeing though, so I won't go into my issues here.
On Friday, July 15, 2011 1:42:23 PM UTC-4, Nan Liu wrote:
Facts are top scope, so simply ::factname such as
scope.lookupvar('::operatingsystem')
Well, whatever problem I'm seeing is due to the nested Facter.add
statements...when I pulled the ldap_rid one out and ran it separately, it
worked.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
I have it working, but I'm curious if this might be a bug with nested
Facter.add statements?
I simply un-nested them and used a 'confine' statement to make things work.
New facts posted below:
Facter.add(is_ldap_server) do
setcode do
if FileTest.exists?(/usr/sbin/slapd)
%x{echo
IMHO I don't think I want nested facts to work :-). The evaluation
order alone is trouble some ... ie. the inner fact wouldn't get added
until the enclosed fact is evaluated ... doesn't sound like something
you would want in ordinary circumstances :-). Remember sometimes fact
information is gather
Yes I did that and got the following error:
change from notrun to 0 failed: /usr/bin/mysql -uroot -pring parasol
download.php?i=hV0wsTfa returned 1 instead of one of [0] at /etc/
puppet/environments/ss/modules/vim/manifests/init.pp:29
This is my exec:
exec {Get db:
command =
Yes I did that and got the following error:
change from notrun to 0 failed: /usr/bin/mysql -uroot -pring parasol
download.php?i=hV0wsTfa returned 1 instead of one of [0] at /etc/
puppet/environments/ss/modules/vim/manifests/init.pp:29
This is my exec:
exec {Get db:
command =
I tried the path /usr/bin but it showed the following error:
change from notrun to 0 failed: /usr/bin/mysql -uroot -proot papa
filedump.sql returned 1 instead of one of [0] at /etc/puppet/ping/
modules/vim/manifests/init.pp:29
exec {Get db:
command = /usr/bin/mysql -uroot -proot
I scrapped the idea and just gonna go with using activemq and
connecting to the DB directly. I think this may scale better in the
long run anyway ;-)
On Thu, Jul 14, 2011 at 10:09 PM, Scott Smith sc...@ohlol.net wrote:
I personally couldn't get it to work (no facts in Dashboard), but only spent
On 2011 7 15 22:22, Glenn Bailey replic...@dallaslamers.org wrote:
I scrapped the idea and just gonna go with using activemq and
connecting to the DB directly. I think this may scale better in the
long run anyway ;-)
Not to hijack the thread, but multiple puppetmasters facts, rest etc is
I'd like to reorganize yum.puppetlabs.com.
As it is, it's a little cluttered, and it's unclear what each folder
and such are for.
Here's what I'd like to do:
yum.puppetlabs.com/
/el
/4
/5
/6
/fedora
/14
/15
/sles
/11
Under each of those we'll have
products -- stuff we
On Thu, Jul 14, 2011 at 8:55 AM, PBWebGuy pbweb...@gmail.com wrote:
I have a Chicken and Egg scenario here and trying to come up with a
way to solve it.
I have a mount definition that manages mount points. The problem
arises when the mount point changes after it is in use. Case in
point,
Seems like the command /usr/bin/mysql -uroot -proot papa filedump.sql
returns an error when executed.
Try to run it directly to understand why and note that you have to eecute it
only once and not at every Puppet runs, that is achieved with
refreshonly = true,
or
unless = a command that
34 matches
Mail list logo
