[Bug 225811] www/py-searx in jail segfault

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225811

            Bug ID: 225811
           Summary: www/py-searx in jail segfault
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: zaphod at berentweb.com
                CC: loic.blot at unix-experience.fr
             Flags: maintainer-feedback?(loic.blot at unix-experience.fr)
                CC: loic.blot at unix-experience.fr

Two apparent problems with py-searx.
This is possibly due to update 0.12.0, as this problem exists since around
2017-06.

1. service searx onestop
searx not running?
ls /var/run/sear* > -rwxr-xr-x  1 www  wheel /var/run/searx.pid
Has to be shut down with kill.

2. Searx in a jail segfaults.
# service searx onestart > dies silently
# python2 /usr/local/lib/python2.7/site-packages/searx/webapp.py  > segfault
tcpdump shows normal outgoing request and answer from 52.222.164.125:443
Enabling debug True in settings.yml shows last output as (then it's killed):
DEBUG:searx.webapp:templates directory is
/usr/local/lib/python2.7/site-packages/searx/templates
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): soundcloud.com

Jail settings:
securelevel = 3;
allow.set_hostname = 0;
exec.start = "/bin/sh /etc/rc";
exec.stop = "/bin/sh /etc/rc.shutdown";
path = /jails/searx;
interface = vlan1;
ip4.addr = 192.168.5.80/32;
devfs_ruleset = 11;
mount.devfs;
mount.fstab = /etc/jail/fstab.searx;

Relaxing jail parameters (raw sockets, etc) has no effect.

-- 
You are receiving this mail because:
You are the assignee for the bug.