Should this be easier with spooler instead of celery? -V @venkasub <http://about.me/venkasub>
On Mon, May 20, 2013 at 10:39 PM, Łukasz Mierzwa <[email protected]>wrote: > It seems that it takes a lot of time to connect from django node to smtp > server and --harakiri kills your worker. > Verify with django "./manage.py shell" that you can send those emails with > your current code. > After that I would suggest to move smtp handling to background queue using > celery and https://pypi.python.org/pypi/django-celery-email > > > 2013/5/20 Daniel Kopka <[email protected]> > >> Hi, >> >> When I try to send email from Django 1.2 via uWSGI in log I receives >> (uwsgi 1.9.10): >> >> uwsgi_response_write_body_do(): Broken pipe [core/writer.c line 248] >> IOError: write error >> *** HARAKIRI ON WORKER 6 (pid: 30863, try: 1) *** >> HARAKIRI: -- syscall> 42 0x8 0x7fff3d23f710 0x10 0xe 0x1 0x100 >> 0x7fff3d23f6b0 0x7fe481bcb8ad >> HARAKIRI: -- wchan> inet_stream_connect >> *** backtrace of 30863 *** >> xx_uWSGI worker 6(uwsgi_backtrace+0x29) [0x451b49] >> xx_uWSGI worker 6(what_i_am_doing+0x17) [0x451fc7] >> /lib64/libc.so.6(+0x32920) [0x7fe480095920] >> /lib64/libpthread.so.0(__connect+0x2b) [0x7fe481bcb8ab] >> /srv/venvs/xx/lib64/python2.6/lib-dynload/_socketmodule.so(+0x6018) >> [0x7fe47de2c018] >> /srv/venvs/xx/lib64/python2.6/lib-dynload/_socketmodule.so(+0x809c) >> [0x7fe47de2e09c] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4e26) [0x7fe4807025c6] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927) [0x7fe480704657] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304) [0x7fe480702aa4] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927) [0x7fe480704657] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304) [0x7fe480702aa4] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef) [0x7fe480703b8f] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927) [0x7fe480704657] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x5304) [0x7fe480702aa4] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x927) [0x7fe480704657] >> /usr/lib64/libpython2.6.so.1.0(+0x6adad) [0x7fe480697dad] >> /usr/lib64/libpython2.6.so.1.0(PyObject_Call+0x53) [0x7fe480670c63] >> /usr/lib64/libpython2.6.so.1.0(+0x566af) [0x7fe4806836af] >> /usr/lib64/libpython2.6.so.1.0(PyObject_Call+0x53) [0x7fe480670c63] >> /usr/lib64/libpython2.6.so.1.0(PyEval_CallObjectWithKeywords+0x43) >> [0x7fe4806fcc93] >> /usr/lib64/libpython2.6.so.1.0(PyInstance_New+0x76) [0x7fe480682e06] >> /usr/lib64/libpython2.6.so.1.0(PyObject_Call+0x53) [0x7fe480670c63] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x47d4) [0x7fe480701f74] >> /usr/lib64/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x63ef) [0x7fe480703b8f] >> *** end of backtrace *** >> HARAKIRI: --- uWSGI worker 6 (pid: 30863) WAS managing request >> /accounts/register/ since Mon May 20 18:53:54 2013 --- >> *** HARAKIRI ON WORKER 6 (pid: 30863, try: 2) *** >> HARAKIRI: -- wchan> do_exit >> DAMN ! worker 6 (pid: 30863) died, killed by signal 9 :( trying respawn >> ... >> Respawned uWSGI worker 6 (new pid: 30999) >> >> >> Any ideas what is wrong or where to look for the error? >> >> >> >> -- >> Pozdrawiam, >> Daniel Kopka >> Tel: 502276071 >> >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> >> > > > -- > Łukasz Mierzwa > > _______________________________________________ > 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
