From owner-freebsd-ports@freebsd.org Tue Jul 3 10:09:17 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AABBD1031BE7 for ; Tue, 3 Jul 2018 10:09:17 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (unknown [IPv6:2a01:4f8:d12:604::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 29BB97871F for ; Tue, 3 Jul 2018 10:09:16 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w63A8w5G085507 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 3 Jul 2018 12:08:58 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: fbl@aoek.com Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id w63A8llJ058323; Tue, 3 Jul 2018 17:08:47 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Passenger not working any more after Base System upgrade: can you reproduce? To: =?UTF-8?B?Sm9zw6kgUMOpcmV6?= , freebsd-ports@freebsd.org References: <00d6257dc47d35f24a1e3e8e414cc537@mail.yourbox.net> From: Eugene Grosbein X-Enigmail-Draft-Status: N1110 Message-ID: <5B3B4B2F.1060904@grosbein.net> Date: Tue, 3 Jul 2018 17:08:47 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <00d6257dc47d35f24a1e3e8e414cc537@mail.yourbox.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, SPF_PASS,T_DATE_IN_FUTURE_96_Q autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * 0.0 T_DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: * date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 10:09:17 -0000 On 02.07.2018 03:19, José Pérez via freebsd-ports wrote: > Hi, > after a Base System upgrade Passenger fails on > startup with this error: > nginx: [alert] Unable to start the Phusion Passenger watchdog: it seems > to have been killed with signal SIGABRT during startup (-1: Unknown > error) > > Can please someone try and reproduce and/or > suggest a workaround/fix? > > How to reproduce: > - stable 11.2 > - install nginx or apache (same problem with > both) > - install (almost) any passenger version (I > could reproduce with 5.2.1, 5.3.2 (current > in ports) and 5.3.3 (latest)) > > What you get: > # service nginx start > Performing sanity check on nginx configuration: > nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is > ok > nginx: configuration file /usr/local/etc/nginx/nginx.conf test is > successful > Starting nginx. > nginx: [alert] Unable to start the Phusion Passenger watchdog: it seems > to have been killed wit > > Further error details in log: > [ pid=57456, timestamp=1530359790 ] Process aborted! signo=SIGABRT(6), > reason=#65543, si_addr=0x0, randomSeed=1530359790 Have your tried to google this? Search for "reason=" "65543" gives https://github.com/phusion/passenger/issues/987 as second link that mentiones very similar problem pointing to some C++ compiler incompatibility and FreeBSD 11.2 got new clang version 6.0.0, so that may be a culprit. You should try to deinstall all dependent ports including nginx and the application itself and rebuild them all from scratch to eliminate possible C++ mangling/runtime problems.