From debbugs-submit-bounces@debbugs.gnu.org Mon Mar 05 02:43:37 2018 Received: (at 30706) by debbugs.gnu.org; 5 Mar 2018 07:43:37 +0000 Received: from localhost ([127.0.0.1]:45005 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eskmW-0005ir-P7 for submit@debbugs.gnu.org; Mon, 05 Mar 2018 02:43:36 -0500 Received: from hera.aquilenet.fr ([185.233.100.1]:34818) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eskmU-0005ii-Jz for 30706@debbugs.gnu.org; Mon, 05 Mar 2018 02:43:35 -0500 Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id 52BA611862; Mon, 5 Mar 2018 08:43:33 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at aquilenet.fr Received: from hera.aquilenet.fr ([127.0.0.1]) by localhost (hera.aquilenet.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8UVF6qxJGXSH; Mon, 5 Mar 2018 08:43:32 +0100 (CET) Received: from jurong (unknown [IPv6:2001:910:103f::c1e]) by hera.aquilenet.fr (Postfix) with ESMTPSA id 910A210CB1; Mon, 5 Mar 2018 08:43:31 +0100 (CET) Date: Mon, 5 Mar 2018 08:43:24 +0100 From: Andreas Enge To: Ricardo Wurmus Subject: Re: bug#30706: Nginx service fails Message-ID: <20180305074324.GA7822@jurong> References: <20180304222749.GA23799@jurong> <20180304230637.GA24077@jurong> <87tvtvyoih.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87tvtvyoih.fsf@elephly.net> User-Agent: Mutt/1.9.3 (2018-01-21) X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 30706 Cc: guix-devel@gnu.org, 30706@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.0 (/) On Mon, Mar 05, 2018 at 08:23:18AM +0100, Ricardo Wurmus wrote: > I had the same error when updating my i686 netbook after a long while. > After a reboot everything seemed to be fine, though. Ah, thanks for the information! A reboot made things worse in my case - I rebooted the virtual machine, and now I cannot ssh into it any more. So it looks like I will have to set it up from scratch again... In my case, the problem occurred between February 28 and March 4. Andreas