From owner-freebsd-stable@FreeBSD.ORG Mon Mar 23 22:26:14 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EED6E2CD for ; Mon, 23 Mar 2015 22:26:14 +0000 (UTC) Received: from mail.xtaz.uk (tao.xtaz.uk [IPv6:2001:8b0:202::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B06D9877 for ; Mon, 23 Mar 2015 22:26:14 +0000 (UTC) Received: by mail.xtaz.uk (Postfix, from userid 1001) id A8D14209B03D; Mon, 23 Mar 2015 22:26:10 +0000 (GMT) Date: Mon, 23 Mar 2015 22:26:10 +0000 From: Matt Smith To: Gerhard Schmidt , freebsd-stable@freebsd.org Subject: Re: Problems with openssl 1.0.2 update Message-ID: <20150323222610.GB1258@xtaz.uk> Mail-Followup-To: Matt Smith , Gerhard Schmidt , freebsd-stable@freebsd.org References: <550FEBE6.5090804@ze.tum.de> <20150323113632.GA1258@xtaz.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20150323113632.GA1258@xtaz.uk> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 22:26:15 -0000 On Mar 23 11:36, Matt Smith wrote: >On Mar 23 11:33, Gerhard Schmidt wrote: >>Hi, >> >>we experiencing a problem after upgrading the openssl port to openssl >>1.0.2. >> >>/usr/bin/vi started to crash after some seconds with segfault. >>/rescue/vi works just fine. Deleting the openssl 1.0.2 package >>everything works just fine again. Installing the old openssl 1.0.1_18 >>package it still works just fine. >> >>it seams that besides vi the bash also has this problem. Anybody >>experiencing the same or is this something specific to my system. >> >>I'm running FreeBSD 10.1 updated tonight. >> > >There is definitely something not right. See this too https://forums.freebsd.org/threads/postfix-does-not-start-build-anymore-since-upgrade-to-openssl-1-0-2.50959/ > >I haven't had a chance yet to test it again in more detail, but >someone reported that postfix was broken, and I had PHP-FPM racing and >taking up 50+ load average on my box which I guess was probably nginx >hitting it with tons of requests. Mine is 10.1-STABLE amd64. > I've just reinstalled openssl 1.0.2, and recompiled all ports that link to openssl. And I'm still getting huge problems. PHP-FPM races and starts loads of processes and uses 50+ load average making the machine unresponsive. And trying to run a /bin/sh shell script gives this: sh: environment corrupt; missing value for USERNAME This is clearly very dangerous and broken. Backing out to openssl 1.0.1 fixes everything. -- Matt