It looks like the installation of redis is failing because the user 'redis'
already exists; and the directory /home/username/myapp-new/config does not
exist or is not writeable ...
On Friday, 13 January 2017 20:10:00 UTC+2, Steve Button wrote:
>
> Error: Execution of '/usr/bin/apt-get -q -y -o
Thanks for your answer Nick, I will surely try this when 3.7.5 is out
Le mardi 24 mars 2015 13:10:25 UTC+1, Frederic Conrotte a écrit :
>
> Hello
>
> I'm using Puppet Master 3.7 thru Apache/Passenger and I am facing this
> compilation issue:
>
>
> [1;31mError: Could not retrieve catalog from re
On Tuesday, 24 March 2015 12:10:25 UTC, Frederic Conrotte wrote:
>
> Hello
>
> I'm using Puppet Master 3.7 thru Apache/Passenger and I am facing this
> compilation issue:
>
>
> [1;31mError: Could not retrieve catalog from remote server: Error 400 on
> SERVER: assert_type(): Expected type Stri
On Monday, October 27, 2014 1:28:25 PM UTC-5, huhm4n wrote:
>
> When I'm installing some package using puppet, let's say
>
>
> package { "xxx":
> ensure => present,
> }
>
> How do I include if it is running yum install, or apt-get when I'm pushing
> this module on os level?
>
I'm not sure exactly what your trying to achieve by getting the provider
but I give it a shot at it anyway.
In order to get debugging info from puppet you would use a
notice. http://www.puppetcookbook.com/posts/simple-debug-messages.html
So if you wanted to have your EL systems tell you they i
I've just encountered and fixed the exact same error message.
The repo (and the .git directory in it) contained files not owned by the
user specfied in the vcsrepo command. Ensure the ownership of the directory
before vcsrepo-ing it:
file { "/home/myuser/myrepo":
ensure => directory,
Following up to my own post...
Without changing my manifest data, I managed to get this to work by changing my
rpm packages around, from this, which didn't work:
hiera-eyaml 2.0
trollop 2.0
highline 1.6.19
To this, which did:
hiera-eyaml 1.3.4
trollop 1.16
highline 1.6.20
This didn't work eit
Here's a sample value. Apart from the length it looks much like yours. (But
your encrypted value appears on a separate line, but possibly word wrap.)
testing::cwood::param:
ENC[PKCS7,MIIBiQYJKoZIhvcNAQcDoIIBejCCAXYCAQAxggEhMIIBHQIBADAFMAACAQAwDQYJKoZIhvcNAQEBBQAEggEARs4upyGGGEl1Q3HJdh1Rov+IkQO07
What does the actual yaml containing the encrypted value look like? I've
had some trouble simply copy & pasting eyaml output into yaml files. I
found using something like this works best:
mysql::server::root_password:
ENC[PKCS7,MxxZIhvcNAQcDoIIBejCCAXYCAQAxggEhMIIBHQIBAD
On Wednesday, February 12, 2014 4:36:31 PM UTC-6, Joaquin Menchaca wrote:
>
> Alright, I found the source of my problem, at least I think. The
> puppetmaster includes path to modules based on an environment (staging,
> production, qa) and a global path shared by all environments. The
> deplo
Alright, I found the source of my problem, at least I think. The
puppetmaster includes path to modules based on an environment (staging,
production, qa) and a global path shared by all environments. The
deployenv was in both locations, global and the environmental ones. The
module shared by
Is there a way to blow away the cache and refresh? We don't use ENC in
this environment, just a simple site.pp, which references nodes.pp.
Segue, what I like about ENC is that you can call your homegrown script,
get a yaml of params, classes for that node. I wish I could get something
simil
On Tuesday, February 11, 2014 6:05:54 PM UTC-6, Joaquin Menchaca wrote:
>
> I was wondering is there is a way to see what puppet things a node
> resource is, such as classes it includes. Somehow in our environment it is
> picking up a class that we did not specify.
>
I could believe that you
On Wednesday, December 25, 2013 9:47:39 AM UTC-6, Felix.Frank wrote:
>
> Hi,
>
> for what it's worth - the error seems to indicate that su considers
> "/usr/local/bin/git config remote.origin.url" to be the name of an
> executable file that contains a space.
>
I agree that it looks like the
Hi,
for what it's worth - the error seems to indicate that su considers
"/usr/local/bin/git config remote.origin.url" to be the name of an
executable file that contains a space.
I cannot fathom why this is inflicting you now, though.
On 12/23/2013 09:12 PM, Patrick Gibson wrote:
> Error: /Stage[
Does anyone have any advice on simulating the environment and conditions
under which processes are run by Puppet? I'd really like to get the bottom
of this, as other commands I'm running via other classes are working fine.
Thanks,
Patrick
On Monday, 23 December 2013 12:12:40 UTC-8, Patrick Gi
If I manually clone the repo, I get a similarly puzzling error:
Error: /Stage[main]/myuser/Vcsrepo[/home/myuser/myrepo]: Could not
evaluate: Execution of '/usr/bin/su myuser -c "/usr/local/bin/git config
remote.origin.url"' returned 127: -su: /usr/local/bin/git config
remote.origin.url: No such
(I should mention this is on FreeBSD 9.2.)
On Saturday, 21 December 2013 18:33:45 UTC-8, Patrick Gibson wrote:
>
> I'm using the vcsrepo module to clone a git repo as a particular user, and
> I'm getting a puzzling error:
>
> Debug: Executing '/usr/bin/su myuser -c "/usr/local/bin/git clone
> g.
On Friday, February 1, 2013 8:16:12 AM UTC-6, Bernhard Schmidt wrote:
>
> ---
> require 'facter'
> require 'facter/util/ip'
>
> if not FileTest.exists?("/usr/sbin/lldpctl")
> nil
> end
>
That last bit probably doesn't do what you want. That is to say, it
evaluates to nil in every case
Hi Curt, I realize this is 3 year s later, but do you have any idea how one
debugs such an issue in 2012?
Cheers,
Virgil
On Friday, July 3, 2009 2:13:14 PM UTC-7, Curt Micol wrote:
>
> On Fri, Jul 3, 2009 at 12:05 PM, Martin
> Wheldon>
> wrote:
> >
> > Hi Curt,
> >
> > Did you manage to resolv
I just added "node default {}" to the site.pp and LDAP ENC has
"magically" started working. This is not mentioned nowhere in Pulling
strings, I can't comment on Pro Puppet since I don't have it, and
based on my reading of the LDAP_Nodes wiki page I took the "default
nodes" section to mean this was
On Fri, Jul 3, 2009 at 12:05 PM, Martin Wheldon wrote:
>
> Hi Curt,
>
> Did you manage to resolve this issue? If not I think it may be the
> format of your yaml output.
>
>>---
>>classes:
>>- custom
>>- monitoring::base
>
> Should be this
>
> ---
> classes:
> - custom
> - monitoring::base
>
>
Hi Curt,
Did you manage to resolve this issue? If not I think it may be the
format of your yaml output.
>---
>classes:
>- custom
>- monitoring::base
Should be this
---
classes:
- custom
- monitoring::base
Note the indentation. Having said that I have been unable to persuade
the python y
2009/6/29 Nicolas Szalay :
> Le lundi 29 juin 2009 à 01:09 -0700, Curt Micol a écrit :
> Did you try running it as the "puppet" user ? permissions on NODEFILE &
> LOGFILE could be source of errors.
Yes, sorry, I get the same results with running as the puppet user.
Just tested once more to verify
Le lundi 29 juin 2009 à 01:09 -0700, Curt Micol a écrit :
> When I run the script directly:
> [r...@vpsadmins ~]# python /etc/puppet/tools/external_nodes.py dc2-
> vps1-400b.example.com
> ---
> classes:
> - custom
> - monitoring::base
> - ntpd
> - puppetd
> - rpms
> - sshd
> - yum
> - crontab
> -
This is not my original error, I have fixed that. My original error did not
output to stderr (from the script execution) because it was a permissions
issue with the puppet user.
I created this error as an example to show that error outputs from script
execution are being suppressed at trace level.
Le mercredi 24 juin 2009 à 10:28 +0200, Dan Bode a écrit :
> # /etc/puppet/conf/node_classifier HOST.com
> /etc/puppet/conf/node_classifier:26:in `initialize': No such file or
> directory - /etc/puppet/conf/inventory.csv (Errno::ENOENT)
> from /etc/puppet/conf/node_classifier:26:in `new'
>
I just had to solve it the old fashion way. Write statements to a log file,
and find the broken line. The issue was that a file did not have proper read
permissions for the puppet user.
trace is not very helpful
here is the server on trace:
#puppetmasterd --no-daemonize --verbose --debug --trace
Le mercredi 24 juin 2009 à 10:02 +0200, Dan Bode a écrit :
> Hi all,
>
> How can I debug external node script errors? I cant seem to figure out
> what is wrong with my script. It appears to work from the command
> line, but not from puppet.
Run your master with --debug --trace
--~--~-
chris wrote:
> Sorry, I was wrong -- namespaceauth.conf on the client only had a
> [puppetrunner] entry. With the complete list below it works like a
> charm.
No problem man. I'm just happy to hear it worked out.
Regards
Rolf
--~--~-~--~~~---~--~~
You received t
Sorry, I was wrong -- namespaceauth.conf on the client only had a
[puppetrunner] entry. With the complete list below it works like a
charm.
Thanks!
Chris
On Apr 3, 11:15 am, chris wrote:
> Jason -- I'm not using passenger, this happens when we run our server
> with webbrick or with mongrel.
>
Jason -- I'm not using passenger, this happens when we run our server
with webbrick or with mongrel.
Rolf -- namespaceauth.conf on both the client and the server have
[fileserver]
allow *.local
[puppetmaster]
allow *.local
[pelementserver]
allow *.local
[puppetrunner]
allow serv3
chris wrote:
> puppetd -d -v --no-daemonize gives:
Have you tried to run puppetmaster in front ( -d -v --no-daemonize )
for debugging?
How does your /etc/puppet/namespaceauth.conf file look on the client
and on the server?
Regards
Rolf
--~--~-~--~~~---~--~~
You
I think I get this as well when I use puppetrun. Are you by change
using passenger at all?
-Jason
On Apr 1, 2009, at 12:03 PM, chris wrote:
>
>
> Puppet's been super for our installation of ~800 hosts, but I'm trying
> to figure out why puppetrun isn't working for our us. Nodes work fine
> as
kevin wrote:
> I'd like to run puppet and see exactly what it would do, or what it
> tried to do.
>
> Do i need to run puppet or puppetd to get that to happen? I've been
> trying the --verbose --parseonly options, but they have not been
> working as I would expect...
You probably want to use t
Somewhat related when trying to improve performance is doing debugging of
how long operations take.
Puppet already makes some use of this, but it's worth noting that for a
given section of code, you can use the existing Benchmark code to do this.
ie you can surround a code block with something li
On Mon, 2008-09-08 at 10:39 -0600, Andrew Shafer wrote:
>
> I've been using a combination of GDB, DTrace, puts caller and puts
> 'WTF'
>
> GDB can be like staring into the abyss.
>
> DTrace seems the most powerful and promising, but a bit of a learning
> curve.
>
> puts is primitive, but it wo
Nigel Kersten wrote:
> so I've found myself with a few reasons to need to debug
> puppetd/puppetmasterd lately since we upgraded to 0.24.5
>
> I've been doing this by basically throwing Puppet.notice/warning
> statements into the code, which feels rather primitive...
>
> How are people doing deb
I've been using a combination of GDB, DTrace, puts caller and puts 'WTF'
GDB can be like staring into the abyss.
DTrace seems the most powerful and promising, but a bit of a learning curve.
puts is primitive, but it works.
Would love to swap tips and tricks with anyone debugging Ruby in general
39 matches
Mail list logo
