Passenger not working any more after Base System upgrade: can you reproduce?

José Pérez fbl at aoek.com
Tue Jul 3 09:56:35 UTC 2018


El 2018-07-03 09:59, Eugene Grosbein escribió:
> On 02.07.2018 03:19, José Pérez via freebsd-ports wrote:
> 
> [skip]
> 
> Have you actually read the log?
> 
>> 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
> 
> [skip]
> 
>> *** ERROR: cannot execute lsof: No such file or directory (errno=2)
> 
> Make sure your lsof binary is present (installed by port or package)
> and your application has correct search path for it.

Hi,
this is completely irrelevant because lsof is needed to
handle the aborting Passenger application.

Even if you have lsof in path, Passenger still fails!

Furthermore there is a bug in Passenger source when it tries to
use ls -v option which is absent in BSDs, but the source reads:
// The '-v' is for natural sorting on Linux. On BSD -v means something 
else but it's harmless.

Well, not so harmless as we can see:
ls: illegal option -- v
usage: ls [-ABCFGHILPRSTUWZabcdfghiklmnopqrstuwxy1,] [-D format] [file 
...]
ERROR: Could not run 'ls' to dump file descriptor information!


The problem is difficult to dig because is independent from Passenger
version and dependent on FreeBSD Base System version.

Regards,

-- 
José Pérez


More information about the freebsd-ports mailing list