Google.
On Thu, Feb 28, 2013 at 5:13 PM, Cody Robertson c...@hawkhoststatus.comwrote:
Clearly I have a firm grasp on YAML. That'd be the issue - thanks!
For the record I tried all of the possible values (True, true, 1) -
obviously it was failing as it was an array as previously mentioned
the
syslog? And are there any other *files* in the /var/log/puppetdb directory?
On Wednesday, January 9, 2013 5:30:03 PM UTC-8, Cody Robertson wrote:
I have no core dumps however I need to make sure I have it set to allow
them. It literally just goes kaput - very strange. I've yet to have time
Hello folks! I hope everyone is having a great Wednesday!
I think I may have come across a bug / a use case which isn't working
properly however I wanted to run it by some eyes on the mailing list before
I filed a bug report. I'm attempting to use Hiera with Puppet exported
resources (a Nagios
, 2013 6:11:19 AM UTC-5, Matthew Burgess wrote:
On Wed, Jan 9, 2013 at 1:37 AM, Cody Robertson
codyha...@gmail.comjavascript:
wrote:
Hello! How is everyone this splendid evening?
I've recently migrated to the latest Puppet and PuppetDB (using the
build in
database) however I'm
wrote:
Do you get a core dump? Does it seriously just silently 'stop' with no
SEGV or anything - even in the forground?
On Wed, Jan 9, 2013 at 11:07 PM, Cody Robertson
codyha...@gmail.comjavascript:
wrote:
There is nothing in the logs as previously noted. It simply crashed
quietly
Hello! How is everyone this splendid evening?
I've recently migrated to the latest Puppet and PuppetDB (using the build
in database) however I'm noticing PuppetDB keeps crashing without any
errors that I can find in the logs. I've ran it in the foreground using the
puppetdb-foreground command
I've ran into a strange issue today while using my development environment I
was receiving some errors about modules that shouldn't have been used. After
looking it looks like my agent (or master) isn't respecting the environment
I specify and is actually using the main (master) environment.
I've downgraded a few nodes showing these issues to agent 2.6.9 and they're
working properly. I suspect it's something introduced in 2.7.x branch. If I
have time later I'll see if I can pinpoint where exactly.
--
You received this message because you are subscribed to the Google Groups
Puppet
Sorry for the spam. I've opened an issue for this
http://projects.puppetlabs.com/issues/9388
--
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/-/3AL0gLCrEMYJ.
You might want to look into tagmail which can mail all errors to you
(amongst other things). Alternatively there are dashboards you can use which
prettify things quite a bit (puppet-dashboard, Foreman).
It might be worth noting that at least Foreman supports tagmail type
functionality - I'm
Although I don't know the answer I'm curious as to why you're worried about
using HTTPS when you're sending the reports locally? There is no need to
encrypt the ports if you're just sending them to the same machine /
localhost.
--
You received this message because you are subscribed to the
On 04/11/2011 05:03 AM, Ohad Levy wrote:
git bisect is a great way to figure out which commit broke it.
Ohad
On Mon, Apr 11, 2011 at 9:45 AM, Cody Robertson c...@hawkhost.com
mailto:c...@hawkhost.com wrote:
I'll test it on more versions tomorrow to see if I can pinpoint
exactly
Did you manually install the gem? I believe Todd's RPMS are built to work
with EPEL so you might want to look for the mysql-ruby RPM and see if that
works.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
Can you invoke any custom facts at all? I suspect it facter might not be
looking in the right directory for your puppet facts and thus it's not
finding them when run it locally.
I've confirmed no issue with defining multiple facts in a single file /
calling them with facter locally:
Strange - in the example I used the file is named lvemanager_versions.rb
while the facts are lvemanager_version and lvecpanel_version. Although it's
highly unlikely this is the problem I'm running facter 1.5.8 which is one
version you're not running..
--
You received this message because you
It looks like it's a bug in 1.5.9. I upgraded this particular node to the
latest (rc4) and now the multiple facts don't work as you initially
described. I'd recommend opening a bug report as something changed across
versions to cause this.
--
You received this message because you are
Er, I upgraded to Facter rc5*
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more
I've only tested this on 1.5.8 where it worked. Upgraded to 1.5.9rc5 and it
appears broken.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send
The spec file specifies two packages - a client server. I'm not sure how
PE updates work however.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this
Try running the client with --trace and running the master in the foreground
/ see if any traffic is reaching the master. Also are you behind a firewall
/ iptables?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send
It looks like the `user` portion is overriding the original resource? I
haven't checked if this would work but maybe you can do something along
these lines:
Ssh_authorized_key | title == test.user.key |{
user = [test.user,studio_app],
}
--
You received this
No that's not normal - you shouldn't have to manually start the start the
master like that.. it sounds like your setup is goofy - can you provide logs
from the actual server? The portion you provided us is simple the result of
the web server saying there is no backend / the backend crashed /
there you should be
able to figure out a way to have the files re-created once you've pruned
them (albeit no good way that I know of).
http://dev.mysql.com/doc/refman/5.0/en/innodb-multiple-tablespaces.html
--
Cody Robertson
1-800-859-8803 ext. 5
--
You received this message because you
On 03/24/2011 06:49 PM, Cody Robertson wrote:
On 03/24/2011 06:32 PM, Arnau Bria wrote:
Hi again,
I'm cleaning my DB (which was 15GB) following:
https://github.com/puppetlabs/puppet-dashboard
I did:
rake RAILS_ENV=production reports:prune upto=1 unit=wk
rake RAILS_ENV=development
proxy like Nginx.
--
Cody Robertson
1-800-859-8803 ext. 5
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr
at
http://groups.google.com/group/puppet-users?hl=en.
Check http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel
however I'm not sure how dated. There are passenger instructions near
the bottom (or use Mongrel).
--
Cody Robertson
1-800-859-8803 ext. 5
--
You received this message
On 03/22/2011 03:41 PM, elliott wrote:
Hi guys,
I've had separate development/testing environments partially working
for a while, in that modules get pulled from the correct per-
environment path. However, something that has never seemed to work
was a per-environment manifest. I have more
of rubygem-rest-client in EPEL is 1.3.1 however the the new
version requires 1.4.0. Maybe update the spec file / RPM to reflect this?
--
Cody Robertson 1-800-859-8803 ext. 5
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group
On 03/22/2011 04:32 PM, Ohad Levy wrote:
On Tue, Mar 22, 2011 at 10:28 PM, Cody Robertson c...@hawkhost.com
mailto:c...@hawkhost.com wrote:
On 03/22/2011 04:23 PM, Ohad Levy wrote:
On Tue, Mar 22, 2011 at 10:04 PM, Eduardo S. Scarpellini
scarpell...@gmail.com mailto:scarpell
), and that your local firewall is blocking the port (both
TCP and UDP).
Doesn't puppetd listen on 8139?
-Cody Robertson
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com
On Mar 16, 11:27 am, Dennis Jacobfeuerborn djacobfeuerb...@gmail.com
wrote:
Wow, apparently running a tcpdump -nn port 8140 un-wedges puppet and
brings things back to normal. Problem is that I have no clue how or why
running a tcpdump could possibly matter here even though it apparently does.
31 matches
Mail list logo
