For what its worth the bug in openssl-1.0.1e-15 has been fixed in
upstream by openssl-1.0.1e-16:
http://rhn.redhat.com/errata/RHBA-2013-1751.html
On Mon, Dec 2, 2013 at 12:33 PM, Ken Barber wrote:
> So this seems to be a regression in openssl-1.0.1e-15.el6.x86_64. The
> reason why this works for
So this seems to be a regression in openssl-1.0.1e-15.el6.x86_64. The
reason why this works for JDK 7, is because we've had issues with the
ECC based ciphers in the past, and had to pin JDK 7 to non-ECC
ciphers.
However we had the anticipation that this might be something that
would come back, so
Okay, so this problem seems prolific now. Would you mind raising a
redmine ticket on this?
http://projects.puppetlabs.com/projects/puppetdb
On Thu, Nov 28, 2013 at 3:59 PM, Matthias Saou wrote:
> On Wed, 27 Nov 2013 09:48:52 -0700
> Deepak Giridharagopal wrote:
>
>> On Nov 27, 2013, at 9:11 AM
On Wed, 27 Nov 2013 09:48:52 -0700
Deepak Giridharagopal wrote:
> On Nov 27, 2013, at 9:11 AM, Jonathan Gazeley
> wrote:
>
> > Hmm, well I removed java-1.6.0-openjdk and installed
> > java-1.7.0-openjdk. Reinstalled puppetdb, which pulled
> > java-1.6.0-openjdk back in again, so the two javas w
On Nov 27, 2013, at 9:11 AM, Jonathan Gazeley
wrote:
> Hmm, well I removed java-1.6.0-openjdk and installed java-1.7.0-openjdk.
> Reinstalled puppetdb, which pulled java-1.6.0-openjdk back in again, so the
> two javas were installed simultaneously. Restarted puppetdb and puppetmaster
> and ev
Hmm, well I removed java-1.6.0-openjdk and installed java-1.7.0-openjdk.
Reinstalled puppetdb, which pulled java-1.6.0-openjdk back in again, so
the two javas were installed simultaneously. Restarted puppetdb and
puppetmaster and everything works again I have no idea what was wrong.
--
You
Oops, I was a bit premature firing off my previous response. Here are
the responses to your questions - and thanks very much for your help.
Sorry for the massive email...
On 27/11/13 14:55, Ken Barber wrote:
* What_exact_ version of the JDK is PuppetDB using? The output of
'jinfo ' (pid of th
On 27/11/13 14:55, Ken Barber wrote:
This all sounds pretty serious, but something isn't quite right here
with the information you have provided. This error:
>puppetdb.resnet.bris.ac.uk:8081: Connection refused - connect(2)
Its very rare that a bug in a running piece of code/framework whatever
On Wed, Nov 27, 2013 at 9:55 AM, Ken Barber wrote:
>> I run all my Puppetised servers on CentOS 6.4. Overnight there were a load
>> of updates for CentOS including an update to openssl-1.0.1e-15.el6. Since
>> installing the updates, PuppetDB is no longer working and seems to be having
>> troubles
> I run all my Puppetised servers on CentOS 6.4. Overnight there were a load
> of updates for CentOS including an update to openssl-1.0.1e-15.el6. Since
> installing the updates, PuppetDB is no longer working and seems to be having
> troubles with SSL.
>
> All my puppet nodes show:
>
> Error: Could
10 matches
Mail list logo