Are you using the redmine script or the script of Niphold? I use to compile stuff because the ubuntu packages are not up to date. I think the better you version you can have with the ubuntu package was Redmine 1.4.3, and with my script you get the latest stable 2.2.0. I had to compile rails because there were a security issue with the ubuntu package and if I remember ruby was the ubuntu dev package to get the a decent version of Ruby...
Compiling is not a big deal. Richard On Mon, Jan 28, 2013 at 9:14 AM, Arnon Marcus <a.m.mar...@gmail.com> 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<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 >>>>>>> >>>>>>> >>>>>>> -- >>> >>> >>> >>> >> >> -- > > > > --
