First of all, I apologize for the rather short title but until we figure out
what's going on it's hard to make it more specific

So uwsgi from 42.3 occasionally segfaults with the following error

Apr 17 17:23:07 keystone1 uwsgi[15049]: !!! uWSGI process 15052 got
Segmentation Fault !!!                                                          
Apr 17 17:23:07 keystone1 uwsgi[15049]: *** backtrace of 15052 ***              
Apr 17 17:23:07 keystone1 uwsgi[15049]: /usr/sbin/uwsgi(uwsgi_backtrace+0x2e)
[0x465eee]                                                            
Apr 17 17:23:07 keystone1 uwsgi[15049]: /usr/sbin/uwsgi(uwsgi_segfault+0x21)
[0x4662b1]                                                             
Apr 17 17:23:07 keystone1 uwsgi[15049]: /lib64/libc.so.6(+0x34fe0)
[0x7f595cf25fe0]                                                                
Apr 17 17:23:07 keystone1 uwsgi[15049]: /lib64/libc.so.6(strlen+0x2a)
[0x7f595cf73f2a]                                                              
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyString_FromFormatV+0x206) [0x7f595b900036]     
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyErr_Format+0x8f) [0x7f595b93a14f]              
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyObject_Call+0xcb) [0x7f595b8bdc5b]             
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x2d9c) [0x7f595b928fec]      
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x244) [0x7f595b930fa4]        
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(+0x9a97e) [0x7f595b8d497e]                       
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyObject_Call+0x46) [0x7f595b8bdbd6]             
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x2d9c) [0x7f595b928fec]      
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x51e4) [0x7f595b92b434]      
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x51e4) [0x7f595b92b434]      
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x244) [0x7f595b930fa4]        
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x59cc) [0x7f595b92bc1c]      
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x244) [0x7f595b930fa4]        
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(+0x9a97e) [0x7f595b8d497e]                       
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyObject_Call+0x46) [0x7f595b8bdbd6]             
Apr 17 17:23:07 keystone1 uwsgi[15049]:
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x2d9c) [0x7f595b928fec]

Moreover, when starting the application the following rather strange warning is
observed

Apr 17 17:14:27 keystone1 uwsgi[15049]: [uWSGI] getting INI configuration from
/etc/uwsgi/keystone-wsgi-public.ini                                  
Apr 17 17:14:27 keystone1 uwsgi[15049]: open("/usr/lib64/uwsgi/_plugin.so"): No
such file or directory [core/utils.c line 3684]                     
Apr 17 17:14:27 keystone1 uwsgi[15049]: !!! UNABLE to load uWSGI plugin:
/usr/lib64/uwsgi/_plugin.so: cannot open shared object file: No such file or
directory

Note the strange (_plugin.so) name.

Using uwsgi (2.0.17) from pip seems to work fine (at least there is no such
scary warning)