I found a solution!
I created a file /tmp/django.pid with the PID of the UWSGI master-process,
then I executed in the shell the command uwsgi-core --reload
/tmp/django.pid and the UWSGI process has restarted and the urls.py changes
are working now.
Thanks a lot for the help!
El sábado, 9 de
I have launched a "/etc/init.d/uwsgi restart" but the application is still
not loading the changes in urls.py file.
I think I have to kill the process because after restarting the uwsgi
process the PID is still the same:
*root@miami ~ # ps -fea|grep uwsgi
uwsgi11916 1 0 Jan22 ?
The problem is that I am administrating this server where the Django
application was already installed and deployed so I don't have this
information.
However I have execute "ps -e" to view all the processes running on my
server and I got this:
PID TTY TIME CMD
1 ?00:00:2
On Fri, Mar 8, 2013 at 6:14 PM, Asier Hernández Juanes
wrote:
> When I type "locate *.fcgi" I get no results at all
that searches for files. no relation to processes.
to help you, first we need to know a bit about your deployment
architecture, specially which WSGI server you're using behind ng
I understand but I cannot locate the FastCGI process to stop it. When I type
"locate *.fcgi" I get no results at all so unfortunatelly I don't know how to
stop the Django (or fastCGI) process itself.
Can anyone help me, please?
--
You received this message because you are subscribed to the Goo
Well, nginx is a proxy to the fastCGI application. So you can't access it
from the usual URL when
nginx is stopped, but that doesn't mean that the process to which you
proxy, which is running
Django, has stopped.
On Fri, Mar 8, 2013 at 3:11 PM, Asier Hernández Juanes <
asiertxo...@gmail.com> wrot
Maybe fastCGI but when I stop the nginx server with /etc/init.d/nginx stop
the application is not loading.
I have seen some fastCGI configuration inside nginx server but I don't know
how to restart fastCGI process or Django process itself.
How can I do that?
El viernes, 8 de marzo de 2013 20:0
On Sun, Mar 3, 2013 at 8:16 AM, Asier Hernández Juanes
wrote:
> i have a remote Linux server with a Django application running in a nginx
> server
Django application's don't run in the nginx server. There must be
some other process running your app. Either uWSGI, gunicorn, FastCGI,
etc.
On Fr
I have removed the .py and the .pyc files, restart the nginx server and the
application is still working.
I think the alication is being cached or I have the application duplicated
but I am not able to find the solution.
Some ideas?
Thanks!
El lunes, 4 de marzo de 2013 19:30:32 UTC+1, ke1g es
Yes. So it is best to select transfer mechanisms that set the modified
time of the .py file to the target machine's current time at the moment
that the newly written copy is closed, rather than caring about the
modified time on the source machine.
Most mechanisms do this by default (cp, mercurial
Well, it so happens that when you ftp the file from your local box to a
remote machine the timezones are mostly different. For eg. i am in India
and we are 'ahead' of the US, so when i push my code to a server in US
timezone, i see this problem most often.
On Mon, Mar 4, 2013 at 8:26 PM, Bill Free
This should not be a .pyc problem, since upon startup python compares the
modified time of the .pyc to that of the .py, if available.
python will use the .pyc if it can't see the .py . I don't know what it
will do if the .py is there, but it doesn't have permission to read it
(possible permission
That's good to know.
On Monday, March 4, 2013 8:12:15 AM UTC-5, Venkatraman.S. wrote:
>
> Always prefer to delete the .pyc fie for issues such as these wherein
> changes are not reflected despite server restart.
>
> On Sun, Mar 3, 2013 at 9:59 PM, Serge G. Spaolonzi
>
> > wrote:
>
>> Maybe the
Always prefer to delete the .pyc fie for issues such as these wherein
changes are not reflected despite server restart.
On Sun, Mar 3, 2013 at 9:59 PM, Serge G. Spaolonzi wrote:
> Maybe the server is loading an old .pyc file. try to delete the urls.pyc
> file and restart the server.
>
>
> On Sun,
Maybe the server is loading an old .pyc file. try to delete the urls.pyc
file and restart the server.
On Sun, Mar 3, 2013 at 11:16 AM, Asier Hernández Juanes <
asiertxo...@gmail.com> wrote:
> Hi everyone,
>
> i have a remote Linux server with a Django application running in a nginx
> server but w
Hi everyone,
i have a remote Linux server with a Django application running in a nginx
server but when I make a change in urls.py like adding a new urlpattern the
server is not applying the changes. I have restarted nginx server but the
new url is not loading.
Does anyone know what may be the
16 matches
Mail list logo
