I don't know where the script was tested on. Header reports centos 5. My approach on the ubuntu script is to install uwsgi is retrieve the dependencies and let pip compile it, then run uwsgi in emperor mode. This scrips follows a different path but it's not that different. The issue you're describing as "get me the binary" is non-existant. If you want to use the script then you have to follow its lead. If you are not ok with it, just install everything you prefer. If you installed a minimal distro for whatever reason, you're going to suffer the "assumptions" made from who probably tested this script in a non-minimal environment.
PS: these are the prerequisites for compiling uwsgi yum install python python-devel libxml2 libxml2-devel python-setuptools zlib-devel wget openssl-devel pcre pcre-devel sudo gcc make autoconf automake Try installing these and then re-running the script. I assume that adding packages at the start of the script would fix the issue "working on full-install" vs "not working on minimal" On Monday, January 28, 2013 3:14:37 PM UTC+1, Arnon Marcus wrote: > > ? > Isn't sudo an ubuntu command? This is centos... > I'm having problems compiling ruby on another vm, I think this might have > to do with the fact that this is a minimal install... > I didn't even have 'make' installed there... > Why is this script compiling anything? > This seems redundant... > Isn't there a yum package of uwsgi for centos ? I found it hard to > believe... > I would really love to avoid having to compile anything, because you get > to infinite dependance nightmares then... > > On Monday, January 28, 2013 4:01:48 PM UTC+2, Richard wrote: >> >> Not sure, but previously uwsgi was using emperor mode and the way to >> start it was : sudo start uwsgi-emperor >> >> Richard >> >> >> On Mon, Jan 28, 2013 at 8:44 AM, Niphlod <nip...@gmail.com> wrote: >> >>> so basically the script apparently didn't build the uwsgi binary from >>> source >>> >>> https://github.com/web2py/web2py/blob/master/scripts/setup-web2py-nginx-uwsgi-on-centos.sh#L77 >>> is the line used to build it. can you run it again inside the >>> /opt/uwsgi-python dir and see what happens ? >>> >>> >>> >>> On Monday, January 28, 2013 2:06:16 PM UTC+1, Arnon Marcus wrote: >>>> >>>> The folder /opt/uwsgi-python exists, and it has many files and folders, >>>> but no uwsgi file... >>>> There are: >>>> uwsgi.c >>>> uwsgi.h >>>> uwsgi.xml >>>> uwsgi_API.txt >>>> uwsgi_for_nginx.conf >>>> uwsgi_handlers.c >>>> uwsgibuild.lastprofile >>>> uwsgibuild.log >>>> uwsgiconfig.py >>>> uwsgidecorators.py >>>> uwsgidsl.rb >>>> uwsgirouter.py >>>> uwsgirouter2.py >>>> uwsgirouter3.py >>>> uwsgirouter4.py >>>> uwsgirouter5.py >>>> uwsgistatus.py >>>> ... >>>> >>>> And there is a folder: >>>> uwsgicc >>>> >>>> But not: "uwsgi" file/folder as such... >>>> >>>> On Monday, January 28, 2013 2:59:11 PM UTC+2, Arnon Marcus wrote: >>>>> >>>>> uwsgi.log is empty... >>>>> >>>>> On Monday, January 28, 2013 2:57:50 PM UTC+2, Arnon Marcus wrote: >>>>>> >>>>>> Here is something: >>>>>> >>>>>> [root@harmonica2 ~]# service uwsgi start >>>>>> Starting uwsgi: /bin/bash: /opt/uwsgi-python/uwsgi: No such file or >>>>>> directory >>>>>> ** [FAILED] >>>>>> >>>>>> >>>>>> On Monday, January 28, 2013 1:48:33 PM UTC+2, Niphlod wrote: >>>>>>> >>>>>>> >>>>>>> If I recall correctly, uwsgi is launched by the nginx server. >>>>>>>> >>>>>>> >>>>>>> it's configured as a service ... nginx can't start other external >>>>>>> processes. >>>>>>> >>>>>>> @arnon: check if uwsgi is running correctly. you should have a >>>>>>> /var/run/uwsgi.pid holding the pid of the current uwsgi process, and >>>>>>> the >>>>>>> log of uwsgi itself should be at /var/log/uwsgi.log >>>>>>> >>>>>>> >>>>>>> -- >>> >>> >>> >>> >> >> --
