From owner-freebsd-ports@freebsd.org Sun Jul 1 20:19:24 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 BAD4AFDAA2F for ; Sun, 1 Jul 2018 20:19:24 +0000 (UTC) (envelope-from fbl@aoek.com) Received: from mail.yourbox.net (mail.yourbox.net [IPv6:2001:41d0:1:767d::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.yourbox.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5456A7C570 for ; Sun, 1 Jul 2018 20:19:24 +0000 (UTC) (envelope-from fbl@aoek.com) Received: from mail.yourbox.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail.yourbox.net (8.15.2/8.15.2) with ESMTP id w61KJMeK040429 for ; Sun, 1 Jul 2018 22:19:22 +0200 (CEST) (envelope-from fbl@aoek.com) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 01 Jul 2018 22:19:17 +0200 From: =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez?= To: freebsd-ports@freebsd.org Subject: Passenger not working any more after Base System upgrade: can you reproduce? Message-ID: <00d6257dc47d35f24a1e3e8e414cc537@mail.yourbox.net> X-Sender: fbl@aoek.com User-Agent: Roundcube Webmail/1.2.0 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: Sun, 01 Jul 2018 20:19:25 -0000 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 [ pid=57456 ] Crash log dumped to /var/tmp/passenger-crash-log.1530359790 [ pid=57456 ] Date, uname and ulimits: Sat Jun 30 13:56:30 CEST 2018 FreeBSD 11.2-STABLE FreeBSD 11.2-STABLE #0: Fri Jun 29 13:39:48 CEST 2018 root@myhost:/usr/obj/usr/src/sys/GENERIC amd64 amd64 cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 33554432 stack size (kbytes, -s) 524288 core file size (512-blocks, -c) unlimited max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) 131072 max user processes (-u) 8499 open files (-n) 116847 virtual mem size (kbytes, -v) unlimited swap limit (kbytes, -w) unlimited socket buffer size (bytes, -b) unlimited pseudo-terminals (-p) unlimited kqueues (-k) unlimited umtx shared locks (-o) unlimited [ pid=57456 ] Phusion Passenger version: 5.3.2 [ pid=57456 ] libc backtrace not available. -------------------------------------- [ pid=57456 ] Open files and file descriptors: *** ERROR: cannot execute lsof: No such file or directory (errno=2) Falling back to another mechanism for dumping file descriptors. ls: illegal option -- v usage: ls [-ABCFGHILPRSTUWZabcdfghiklmnopqrstuwxy1,] [-D format] [file ...] ERROR: Could not run 'ls' to dump file descriptor information! -------------------------------------- [ pid=57456 ] Dumping a backtrace with crash-watch... Found gdb at: /usr/bin/gdb /usr/bin/gdb is broken on FreeBSD. Looking for an alternative... *** ERROR ***: '/usr/bin/gdb' is broken on FreeBSD. Please install the one from the devel/gdb port instead. If you want to use another gdb I already tried: - on another hardware, just in case - virtual / real metal, no difference - gdb reports the SIGABRT is actually raised by boost when spawning the watchdog I had the module working on 11.1 stable: FreeBSD 11.1-STABLE FreeBSD 11.1-STABLE #0: Tue Feb 20 15:11:50 CET 2018 root@myotherhost:/usr/obj/usr/src/sys/GENERIC amd64 Any suggestion is also very welcome. Thank you. Regards, -- José Pérez