Well my directory tree is:
- mainserver
- ap_server
- __init__.py
- ap_server.py
So, I wanted it to ignore the ap_server module and put in
"mainserver.ap_server", which I think is correct.
Here are the logs with the --show-config included:
;uWSGI instance configuration
[uwsgi]
show-config = true
ini = /sites/metrics_dev/development_uwsgi.ini
socket = /run/uwsgi/metrics_dev.sock
master = true
processes = 2
threads = 20
harakiri = 60
harakiri-verbose = true
limit-post = 65536
post-buffering = 8192
daemonize = /var/log/uwsgi/metrics_dev.log
pidfile = /run/uwsgi/metrics_dev.pid
max-requests = 1000
log-slow = true
virtualenv = /sites/metrics_dev/env/
uid = 33
gid = 33
vacuum = False
enable-threads = True
py-auto-reload = 1
py-auto-reload-ignore = mainserver.ap_server
smart-attach-daemon2 = /run/uwsgi/metrics_dev_msg_server.pid
/sites/metrics_dev/env/bin/python
/sites/metrics_dev/mainserver/msg_server.py
/sites/metrics_dev/development.ini
smart-attach-daemon2 = /run/uwsgi/metrics_dev_alert_generator.pid
/sites/metrics_dev/env/bin/python
/sites/metrics_dev/mainserver/alert_generator.py
/sites/metrics_dev/development.ini
smart-attach-daemon2 = /run/uwsgi/metrics_dev_ap_server.pid
/sites/metrics_dev/env/bin/python
/sites/metrics_dev/mainserver/ap_server/ap_server.py
/sites/metrics_dev/development.ini
ini-paste = /sites/metrics_dev/development.ini
vacuum = False
;end of configuration
*** Starting uWSGI 2.0.8 (64bit) on [Fri Nov 14 22:54:34 2014] ***
compiled with version: 4.7.2 on 31 October 2014 17:37:18
os: Linux-3.2.0-4-amd64 #1 SMP Debian 3.2.63-2
nodename: dev
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 2
current working directory: /
writing pidfile to /run/uwsgi/metrics_dev.pid
detected binary path: /sites/metrics_dev/env/bin/uwsgi
uWSGI running as root, you can use --uid/--gid/--chroot options
setgid() to 33
setuid() to 33
your processes number limit is 3700
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /run/uwsgi/metrics_dev.sock fd 3
Python version: 3.4.2 (default, Oct 28 2014, 17:59:33) [GCC 4.7.2]
Set PythonHome to /sites/metrics_dev/env/
Python main interpreter initialized at 0x1243b90
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 1297152 bytes (1266 KB) for 40 cores
*** Operational MODE: preforking+threaded ***
Loading paste environment: config:/sites/metrics_dev/development.ini
/sites/metrics_dev/env/lib/python3.4/site-packages/Twisted-14.0.2-py3.4.egg/twisted/internet/_sslverify.py:184:
UserWarning: You do not have the service_identity module installed. Please
install it from <https://pypi.python.org/pypi/service_identity>. Without
the service_identity module and a recent enough pyOpenSSL tosupport it,
Twisted can perform only rudimentary TLS client hostnameverification. Many
valid certificate/hostname mappings may be rejected.
verifyHostname, VerificationError = _selectVerifyImplementation()
WSGI app 0 (mountpoint='') ready in 3 seconds on interpreter 0x1243b90 pid:
10764 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 10764)
spawned uWSGI worker 1 (pid: 10769, cores: 20)
Python auto-reloader enabled
spawned uWSGI worker 2 (pid: 10790, cores: 20)
[uwsgi-daemons] found valid/active pidfile for
"/sites/metrics_dev/env/bin/python
/sites/metrics_dev/mainserver/msg_server.py
/sites/metrics_dev/development.ini" (pid: 10664)
[uwsgi-daemons] found valid/active pidfile for
"/sites/metrics_dev/env/bin/python
/sites/metrics_dev/mainserver/alert_generator.py
/sites/metrics_dev/development.ini" (pid: 10667)
[uwsgi-daemons] found valid/active pidfile for
"/sites/metrics_dev/env/bin/python
/sites/metrics_dev/mainserver/ap_server/ap_server.py
/sites/metrics_dev/development.ini" (pid: 10669)
!!! uWSGI process 10769 got Segmentation Fault !!!
*** backtrace of 10769 ***
/sites/metrics_dev/env/bin/uwsgi(uwsgi_backtrace+0x2e) [0x48414e]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_segfault+0x21) [0x4842d1]
/lib/x86_64-linux-gnu/libc.so.6(+0x321e0) [0x7f052554b1e0]
/lib/x86_64-linux-gnu/libc.so.6(+0x1146a4) [0x7f052562d6a4]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_python_autoreloader_thread+0xcd)
[0x49a36d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f0526c17b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f05255f57bd]
*** end of backtrace ***
DAMN ! worker 1 (pid: 10769) died, killed by signal 11 :( trying respawn ...
!!! uWSGI process 10790 got Segmentation Fault !!!
*** backtrace of 10790 ***
/sites/metrics_dev/env/bin/uwsgi(uwsgi_backtrace+0x2e) [0x48414e]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_segfault+0x21) [0x4842d1]
/lib/x86_64-linux-gnu/libc.so.6(+0x321e0) [0x7f052554b1e0]
/lib/x86_64-linux-gnu/libc.so.6(+0x1146a4) [0x7f052562d6a4]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_python_autoreloader_thread+0xcd)
[0x49a36d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f0526c17b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f05255f57bd]
*** end of backtrace ***
Respawned uWSGI worker 1 (new pid: 10811)
DAMN ! worker 2 (pid: 10790) died, killed by signal 11 :( trying respawn ...
Python auto-reloader enabled
Respawned uWSGI worker 2 (new pid: 10832)
!!! uWSGI process 10811 got Segmentation Fault !!!
*** backtrace of 10811 ***
/sites/metrics_dev/env/bin/uwsgi(uwsgi_backtrace+0x2e) [0x48414e]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_segfault+0x21) [0x4842d1]
/lib/x86_64-linux-gnu/libc.so.6(+0x321e0) [0x7f052554b1e0]
/lib/x86_64-linux-gnu/libc.so.6(+0x1146a4) [0x7f052562d6a4]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_python_autoreloader_thread+0xcd)
[0x49a36d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f0526c17b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f05255f57bd]
*** end of backtrace ***
DAMN ! worker 1 (pid: 10811) died, killed by signal 11 :( trying respawn ...
!!! uWSGI process 10832 got Segmentation Fault !!!
*** backtrace of 10832 ***
/sites/metrics_dev/env/bin/uwsgi(uwsgi_backtrace+0x2e) [0x48414e]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_segfault+0x21) [0x4842d1]
/lib/x86_64-linux-gnu/libc.so.6(+0x321e0) [0x7f052554b1e0]
/lib/x86_64-linux-gnu/libc.so.6(+0x1146a4) [0x7f052562d6a4]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_python_autoreloader_thread+0xcd)
[0x49a36d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f0526c17b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f05255f57bd]
*** end of backtrace ***
Respawned uWSGI worker 1 (new pid: 10853)
DAMN ! worker 2 (pid: 10832) died, killed by signal 11 :( trying respawn ...
worker respawning too fast !!! i have to sleep a bit (2 seconds)...
Python auto-reloader enabled
!!! uWSGI process 10853 got Segmentation Fault !!!
*** backtrace of 10853 ***
/sites/metrics_dev/env/bin/uwsgi(uwsgi_backtrace+0x2e) [0x48414e]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_segfault+0x21) [0x4842d1]
/lib/x86_64-linux-gnu/libc.so.6(+0x321e0) [0x7f052554b1e0]
/lib/x86_64-linux-gnu/libc.so.6(+0x1146a4) [0x7f052562d6a4]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_python_autoreloader_thread+0xcd)
[0x49a36d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f0526c17b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f05255f57bd]
*** end of backtrace ***
SIGINT/SIGQUIT received...killing workers...
Respawned uWSGI worker 2 (new pid: 10876)
worker 1 buried after 0 seconds
!!! uWSGI process 10876 got Segmentation Fault !!!
*** backtrace of 10876 ***
/sites/metrics_dev/env/bin/uwsgi(uwsgi_backtrace+0x2e) [0x48414e]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_segfault+0x21) [0x4842d1]
/lib/x86_64-linux-gnu/libc.so.6(+0x321e0) [0x7f052554b1e0]
/lib/x86_64-linux-gnu/libc.so.6(+0x1146a4) [0x7f052562d6a4]
/sites/metrics_dev/env/bin/uwsgi(uwsgi_python_autoreloader_thread+0xcd)
[0x49a36d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f0526c17b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f05255f57bd]
*** end of backtrace ***
worker 2 buried after 0 seconds
goodbye to uWSGI.
On Fri, Nov 14, 2014 at 3:04 PM, Roberto De Ioris <[email protected]> wrote:
>
> > I noticed the "py-auto-reload-ignore" option today and was trying to get
> > it
> > to work. However, when I tried to use it I get the following repeated
> > over
> > and over again:
> >
> > !!! uWSGI process 10145 got Segmentation Fault !!!
> > *** backtrace of 10145 ***
> > /sites/metrics_dev/env/bin/uwsgi(uwsgi_backtrace+0x2e) [0x48414e]
> > /sites/metrics_dev/env/bin/uwsgi(uwsgi_segfault+0x21) [0x4842d1]
> > /lib/x86_64-linux-gnu/libc.so.6(+0x321e0) [0x7f84bc50b1e0]
> > /lib/x86_64-linux-gnu/libc.so.6(+0x11405a) [0x7f84bc5ed05a]
> > /sites/metrics_dev/env/bin/uwsgi(uwsgi_python_autoreloader_thread+0xcd)
> > [0x49a36d]
> > /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50) [0x7f84bdbd7b50]
> > /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f84bc5b57bd]
> > *** end of backtrace ***
> > DAMN ! worker 1 (pid: 10145) died, killed by signal 11 :( trying respawn
> > ...
> >
> > The setting is being done in an ini file with the following value:
> >
> > py-auto-reload-ignore = mainserver.ap_server
> >
> > I'm not really sure the proper syntax for this option, but as it mentions
> > "module" I tried using the python import syntax for specifying a module.
> >
> >
>
> It is the name of the module like written in sys.modules.
>
> The segfault is a bit strange, can you report your full config (with
> --show-config) and the startup logs ?
>
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
