The current default configuration starts uwsgi in emperor mode but runs as the uwsgi user which prevents uwsgi from setuid/setgid'ing and only allows to run all vassals as the same user which is rather limiting and insecure. uwsgi can be built with support for POSIX capabilities which can allow for setuid/setgid use without running the emperor with full root privileges. See https://github.com/gber/uwsgi/commit/a2e686d5fbfef370fbe50b46588e2313ad30375e for a suggested fix.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
uwsgi-1.9.17-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/uwsgi-1.9.17-1.fc20
Package uwsgi-1.9.17-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing uwsgi-1.9.17-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18427/uwsgi-1.9.17-1.fc20 then log in and leave karma (feedback).
uwsgi-1.9.17-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/uwsgi-1.9.17-2.fc20
uwsgi-1.9.17-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.