Opened 5 years ago

Closed 5 years ago

#20402 closed Uncategorized (fixed)

Remove or at least reevaluate the suggestion of as-limit-128

Reported by: django@… Owned by: nobody
Component: Documentation Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


On Ubuntu 12 LTS, as-limit-128 causes uwsgi to fail with misleading errors like: must be installed for pthread_cancel to work
DAMN ! worker 1 (pid: 29232) died, killed by signal 6 :( trying respawn ...

I wasted hours recompiling uwsgi, looking for path issues with and LD, etc.

I removed as-limit=128 and the problem went away. I probably could have increased as-limit as well.

Attachments (1)

django_docs_howto_deployment_wsgi_uwsgi.diff (814 bytes) - added by alextreme 5 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 5 years ago by Russell Keith-Magee

Needs documentation: set
Triage Stage: UnreviewedAccepted

Changed 5 years ago by alextreme

comment:2 Changed 5 years ago by alextreme

Has patch: set

The option isn't required and the uWSGI documentation doesn't seem to recommend it:

In my opinion it is best to not have the option in the example, we shouldn't provide an example that won't work for projects >128MB without a clear reason.

Added a patch to remove the 'limit-as' option from the uWSGI example in the documentation.

comment:3 Changed 5 years ago by Aymeric Augustin

Since many people will just copy-paste the example it's best to keep it as minimal as possible.

One might argue that as-limit is a security requirement; I'm not sure.

Anyway, removing that line appears to be a reasonable step at this point.

comment:4 Changed 5 years ago by Aymeric Augustin <aymeric.augustin@…>

Resolution: fixed
Status: newclosed

In be826aafacb9fe266209604116efe128a0b4cdc0:

Fixed #20402: removed as-limit from uWSGI example.

It can fail in hard-to-diagnose ways.

Note: See TracTickets for help on using tickets.
Back to Top