-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Yes, my clients run with listen option.
Already saw this bug repote and that's why I've restarted puppet agent
without this option yesterday to see what happen.
Will see results when arriving at work :)
JB
On 12/04/2012 01:38, Jason Antman
Hi,
On Apr 11, 2012, at 7:38 PM, Jason Antman wrote:
Sorry I missed this thread until now.
Are you running with --listen? If so, try:
echo | nc localhost 8139
and see if that helps.
https://projects.puppetlabs.com/issues/12185
is tracking an issue where puppetd, running with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Because all my recipes are not fully 2.7 compatible yet :-/
And I won't be able to rewrite them fast enough.
And finally, since the hang issue also occurs with some 2.7 release,
I'm not sure it'll be worth the upgrade
JB
On 10/04/2012 23:41, Jeff
I have the same issue I think. With 2.7.6 and 2.7.11.
https://projects.puppetlabs.com/issues/13000
--
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,
Forgot to mention:
I see this misbehaviour on many servers with:
- puppet 2.6.14,
- facter 1.6.5
- Ubuntu 10.04 with 2.6.32-317-ec2 kernel
See it also with other kernels, but less often.
Puppet facter are home backported (ie, not using apt.puppetlabs.com)
JB
On 4/10/12 11:35 PM, Jean
Hi,
Thanks for all of the replies so far.
On Apr 10, 2012, at 5:37 PM, Jean Baptiste FAVRE wrote:
Seems to be the same as described here:
https://groups.google.com/forum/?fromgroups#!topic/puppet-users/N1XcMTth7mE
Yes it does.
On Apr 11, 2012, at 3:16 AM, Elias Abacioglu wrote:
I have the
Hi,
On Apr 10, 2012, at 5:43 PM, Jeff McCune wrote:
Hey Dave, is this running the stock Ruby that comes with EL6 ?
Yup:
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
This seems to be the same as:
https://projects.puppetlabs.com/issues/13000
...dave
--
You received this message
Sorry I missed this thread until now.
Are you running with --listen? If so, try:
echo | nc localhost 8139
and see if that helps.
https://projects.puppetlabs.com/issues/12185
is tracking an issue where puppetd, running with --listen, gets stuck in
a socket read loop. Any data whatsoever
Hi,
I've recently started to have a problem where some of my clients puppetd
processes are locking up (the puppetdlock file is several hours old). My server
is running puppet 2.7.12 on Centos 6.2 and my clients are running puppet 2.7.12
on Scientific Linux 6.2. If I check the puppetdlock
On Tue, Apr 10, 2012 at 2:24 PM, David Alden d...@alden.name wrote:
If I look at what puppet is running:
# ps -elfw | grep 10726
5 S root 10726 1 0 81 1 - 61549 poll_s 15:15 ?00:00:17
/usr/bin/ruby /usr/sbin/puppetd --debug --verbose
0 Z root 11429 10726 0 81 1 -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Seems to be the same as described here:
https://groups.google.com/forum/?fromgroups#!topic/puppet-users/N1XcMTth7mE
Got the same issue with puppet 2.6.14 and various kernels version.
Can't find what's going rong, so I guess I'll have to
On Tue, Apr 10, 2012 at 2:35 PM, Jean Baptiste FAVRE
jean.baptiste.fa...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Seems to be the same as described here:
https://groups.google.com/forum/?fromgroups#!topic/puppet-users/N1XcMTth7mE
Got the same issue with puppet
12 matches
Mail list logo
