Your logs contain this:
IOError: write error
However, more information is needed in order to understand what is going on. A simple "write error" on its own is insufficient—is it a hardware error? Too many open files? Out of disk space? Something else? If your system writes nothing else in /var/log/syslog at the time the error occurs, it may be the fault of uwsgi that it doesn't show more information about the error. Try to increase error message verbosity, if there is an option to do that.
Incidentally, the reason I migrated from uwsgi to gunicorn a few years ago was that every once in a while I was having a different problem with uwsgi, which was taking me hours to solve, largely because of insufficient documentation. After I switched to gunicorn I never looked back.
Regards,
Antonis
Antonis Christofides http://djangodeployment.com
On 03/01/2017 05:33 PM, carlos wrote:
Hello, Antonis i have debug = false, yesuwsgi dont write anything in the log :/When i see the syslog i see error but not understand!i share this output
thak for you help--
On Wed, Mar 1, 2017 at 12:58 AM, Antonis Christofides <antonis@djangodeployment.com> wrote:
--Hello,
502 usually means the backend isn't running. After you finish the test, has the backend stopped running? Does it continue to throw 502s? If that is the case, I'm wildly guessing that processes might be growing and growing in memory and being eventually killed, but I don't really know. Do you have DEBUG = False? Does uwsgi write something in its log? Does the system write something in the syslog?
Regards,
Antonis
Antonis Christofides http://djangodeployment.com
On 02/28/2017 10:49 PM, carlos wrote:
--Hi, alli have one vps for one application,
vps description
16GB RAM8 core processor160 GB SSD6TB Transfer
ok, i am using, uwsgi(2.0.14), nginx(1.10), mysql(5.6 )and ubuntu 16.04 LTSthis site working well when is visited or hits 1k even 6k, but when visited 10k or 12kraiser error 502,
When I do a test of ab like these command line
ab -k -c 350 -n 20000 mydomain.com/
again raiser the error 502 in almost pages
these are configs all, wsgi, nginx
---- uwsgi script in /etc/uwsgi/app-availabre/website.ini -----
---- nginx conf in /etc/nginx/nginx.conf ------
----- nginx vhost for my website mydpmain --------
How can I do so that the site does not throw the error?
Are the settings correct?
How can i know the layer support the vps?
In nginx how to stop the ab test, if many people do the test the web site throws the error 502 ngixn
I would appreciate it if someone gave me an idea or advice to configure better when there is high traffic or are doing ab test or another benchmarking test
cheers--
att.Carlos Rocha
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAM-7rO1u- .ih5pd9b2AEEDLBJRL7DUvhVDs9hfZj pyGH_fHKJbQ%40mail.gmail.com
For more options, visit https://groups.google.com/d/optout .
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7624c177- .e769-5fd6-496e-5ab07a927783% 40djangodeployment.com
For more options, visit https://groups.google.com/d/optout .
--
att.Carlos Rocha
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAM-7rO31bj6O8L_s-hoVn13zV11UFuV9Wtd4EbJBS9EcFz%3DDtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment