W dniu 10.12.2010 21:29, Łukasz Wróblewski pisze:
> $ uwsgi -s /tmp/tmp.sock -M -p3 -C --chdir /home/ddarko/Pulpit/t1 -w start
> *** Starting uWSGI 0.9.6.5 (32bit) on [Fri Dec 10 21:24:25 2010] ***
> compiled with version: 4.4.5
> Python version: 2.6.6 (r266:84292, Sep 15 2010, 16:02:57)
> [GCC 4.4.5]
> your memory page size is 4096 bytes
> allocated 412 bytes (0 KB) for 1 request's buffer.
> binding on UNIX socket: /tmp/tmp.sock
> chmod() socket to 666 for lazy and brave users
> your server socket listen backlog is limited to 64 connections
> initializing hooks...done.
> ...getting the applications list from the 'start' module...
> uwsgi.applications dictionary is not defined, trying with the
> "applications" one...
> applications dictionary is not defined, trying with the "application"
> callable.
> application 0 () ready
> setting default application to 0
>
> # kill -HUP 2358
>
> spawned uWSGI master process (pid: 2358)
> spawned uWSGI worker 1 (pid: 2359)
> spawned uWSGI worker 2 (pid: 2360)
> spawned uWSGI worker 3 (pid: 2361)
> ...gracefully killing workers...
> Gracefully killing worker 2360...
> Gracefully killing worker 2361...
> Gracefully killing worker 2359...
> binary reloading uWSGI...
> closing all fds>  2 (_SC_OPEN_MAX = 1024)...
> running uwsgi
> execve(): No such file or directory [uwsgi.c line 1411]
>
> :/
> the same version compiled with ptyhon 3.1 works correctly.
>

I already know what's going on.
Problem occurs when I put uWSGI in /usr/sbin and run it without 
specifying the absolute path. From the directory where the file is not 
uwsgi.

Maybe in this case could take advantage of "which". It can be dangerous, 
for example:
$ ls (from dir A)
./uwsgi (version 0.9.7)

$ which uwsgi
/usr/sbin/uwsgi (version 0.9.6.5)

$ uwsgi .... (in dir A, starting 0.9.6.5 from /usr/sbin/uwsgi)
after reload starting version 0.9.7 !!

-- 
Łukasz Wróblewski
www.nri.pl  - Nowoczesne Rozwiązania Internetowe
www.hostowisko.pl  - Profesjonalny i tani hosting
www.katalog-polskich-firm.pl  - Najlepszy darmowy katalog firm
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to