While uwsgi thinks that the reload file has been "touch"-ed, I tried to "stat" it myself and found that the file did not change
myserver@localhost:/sample-app/current/bin$ stat uwsgi-restart File: `uwsgi-restart' Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: ca00h/51712d Inode: 194994 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1003/myserver) Gid: ( 1004/myserver) Access: 2012-04-24 11:23:43.000000000 +0000 Modify: 2012-03-06 13:07:19.000000000 +0000 Change: 2012-04-24 11:23:43.000000000 +0000 myserver@localhost:/sample-app/current/bin$ stat uwsgi-restart File: `uwsgi-restart' Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: ca00h/51712d Inode: 194994 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1003/myserver) Gid: ( 1004/myserver) Access: 2012-04-24 11:23:43.000000000 +0000 Modify: 2012-03-06 13:07:19.000000000 +0000 Change: 2012-04-24 11:23:43.000000000 +0000 myserver@localhost:/sample-app/current/bin$ stat uwsgi-restart File: `uwsgi-restart' Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: ca00h/51712d Inode: 194994 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1003/myserver) Gid: ( 1004/myserver) Access: 2012-04-24 11:23:43.000000000 +0000 Modify: 2012-03-06 13:07:19.000000000 +0000 Change: 2012-04-24 11:23:43.000000000 +0000 myserver@localhost:/sample-app/current/bin$ stat uwsgi-restart File: `uwsgi-restart' Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: ca00h/51712d Inode: 194994 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1003/myserver) Gid: ( 1004/myserver) Access: 2012-04-24 11:23:43.000000000 +0000 Modify: 2012-03-06 13:07:19.000000000 +0000 Change: 2012-04-24 11:23:43.000000000 +0000 Same access time and modification time when uWSGI restarts its workers. Nothing changes. Any idea? PS: Or it is a bug on Xen-based Linux instance? On Tue, Apr 24, 2012 at 8:12 PM, Dinh <[email protected]> wrote: > Oh no. That issue comes back. Again > > Not sure why I dont get that issue when I deploy my code on a dedicated > server (Ubuntu). But after I moved to a Linode instance, I got that > annoying issue > > > On Tue, Apr 24, 2012 at 7:10 PM, Dinh <[email protected]> wrote: > >> Hi all, >> >> I just upgraded from uWSGI 1.1.2 to 1.2 RC2 and got the following errors >> >> + The uwsgi processes restarted continuously. Log file grew very fast >> >> Tue Apr 24 11:37:36 2012 - *** Starting uWSGI 1.2-rc2 (64bit) on [Tue Apr >> 24 11:37:36 2012] *** >> Tue Apr 24 11:37:36 2012 - compiled with version: 4.6.1 on 22 April 2012 >> 09:37:20 >> Tue Apr 24 11:37:36 2012 - current working directory: >> /sample-app/0.1.0-dev >> Tue Apr 24 11:37:36 2012 - writing pidfile to /sample-app/uwsgi.pid >> Tue Apr 24 11:37:36 2012 - detected binary path: >> /usr/local/uwsgi-1.2-rc2/uwsgi >> Tue Apr 24 11:37:36 2012 - your memory page size is 4096 bytes >> Tue Apr 24 11:37:36 2012 - building mime-types dictionary from file >> /etc/mime.types...Tue Apr 24 11:37:36 2012 - 530 entry found >> Tue Apr 24 11:37:36 2012 - detected max file descriptor number: 1024 >> Tue Apr 24 11:37:36 2012 - lock engine: pthread robust mutexes >> Tue Apr 24 11:37:36 2012 - *** Cache subsystem initialized: 64MB (key: >> 2096 bytes, keys: 2096000 bytes, data: 65536000 bytes) preallocated *** >> Tue Apr 24 11:37:36 2012 - uwsgi socket 0 bound to TCP address >> 127.0.0.1:9999 fd 3 >> Tue Apr 24 11:37:36 2012 - Python version: 2.7.2+ (default, Oct 4 2011, >> 20:41:12) [GCC 4.6.1] >> Tue Apr 24 11:37:36 2012 - Python main interpreter initialized at 0xf18850 >> Tue Apr 24 11:37:36 2012 - your server socket listen backlog is limited >> to 100 connections >> Tue Apr 24 11:37:36 2012 - *** Operational MODE: preforking *** >> Tue Apr 24 11:37:37 2012 - WSGI app 0 (mountpoint='') ready in 1 seconds >> on interpreter 0xf18850 pid: 5335 (default app) >> Tue Apr 24 11:37:37 2012 - *** uWSGI is running in multiple interpreter >> mode *** >> Tue Apr 24 11:37:37 2012 - spawned uWSGI master process (pid: 5335) >> Tue Apr 24 11:37:37 2012 - spawned uWSGI worker 1 (pid: 5340, cores: 1) >> Tue Apr 24 11:37:37 2012 - spawned uWSGI worker 2 (pid: 5341, cores: 1) >> Tue Apr 24 11:37:37 2012 - cache sweeper thread enabled >> Tue Apr 24 11:37:38 2012 - *** /sample-app/current/bin/uwsgi-restart has >> been touched... grace them all !!! *** >> Tue Apr 24 11:37:38 2012 - ...gracefully killing workers... >> Tue Apr 24 11:37:38 2012 - Gracefully killing worker 2 (pid: 5341)... >> Tue Apr 24 11:37:38 2012 - Gracefully killing worker 1 (pid: 5340)... >> Tue Apr 24 11:37:39 2012 - binary reloading uWSGI... >> Tue Apr 24 11:37:39 2012 - chdir() to /sample-app/0.1.0-dev >> Tue Apr 24 11:37:39 2012 - closing all non-uwsgi socket fds > 2 (max_fd = >> 1024)... >> Tue Apr 24 11:37:39 2012 - found fd 3 mapped to socket 0 (127.0.0.1:9999) >> Tue Apr 24 11:37:39 2012 - running /usr/local/uwsgi-1.2-rc2/uwsgi >> [uWSGI] getting INI configuration from /sample-app/current/bin/uwsgi.ini >> Tue Apr 24 11:37:39 2012 - *** Starting uWSGI 1.2-rc2 (64bit) on [Tue Apr >> 24 11:37:39 2012] *** >> Tue Apr 24 11:37:39 2012 - compiled with version: 4.6.1 on 22 April 2012 >> 09:37:20 >> Tue Apr 24 11:37:39 2012 - current working directory: >> /sample-app/0.1.0-dev >> Tue Apr 24 11:37:39 2012 - detected binary path: >> /usr/local/uwsgi-1.2-rc2/uwsgi >> Tue Apr 24 11:37:39 2012 - your memory page size is 4096 bytes >> Tue Apr 24 11:37:39 2012 - building mime-types dictionary from file >> /etc/mime.types...Tue Apr 24 11:37:39 2012 - 530 entry found >> Tue Apr 24 11:37:39 2012 - detected max file descriptor number: 1024 >> Tue Apr 24 11:37:39 2012 - lock engine: pthread robust mutexes >> Tue Apr 24 11:37:39 2012 - *** Cache subsystem initialized: 64MB (key: >> 2096 bytes, keys: 2096000 bytes, data: 65536000 bytes) preallocated *** >> Tue Apr 24 11:37:39 2012 - uwsgi socket 0 inherited INET address >> 127.0.0.1:9999 fd 3 >> Tue Apr 24 11:37:39 2012 - Python version: 2.7.2+ (default, Oct 4 2011, >> 20:41:12) [GCC 4.6.1] >> Tue Apr 24 11:37:39 2012 - Python main interpreter initialized at 0xd1b3b0 >> Tue Apr 24 11:37:39 2012 - your server socket listen backlog is limited >> to 100 connections >> Tue Apr 24 11:37:39 2012 - *** Operational MODE: preforking *** >> Tue Apr 24 11:37:39 2012 - WSGI app 0 (mountpoint='') ready in 0 seconds >> on interpreter 0xd1b3b0 pid: 5335 (default app) >> Tue Apr 24 11:37:39 2012 - *** uWSGI is running in multiple interpreter >> mode *** >> Tue Apr 24 11:37:39 2012 - gracefully (RE)spawned uWSGI master process >> (pid: 5335) >> Tue Apr 24 11:37:39 2012 - spawned uWSGI worker 1 (pid: 5352, cores: 1) >> Tue Apr 24 11:37:39 2012 - spawned uWSGI worker 2 (pid: 5353, cores: 1) >> Tue Apr 24 11:37:39 2012 - cache sweeper thread enabled >> Tue Apr 24 11:37:40 2012 - *** /sample-app/current/bin/uwsgi-restart has >> been touched... grace them all !!! *** >> Tue Apr 24 11:37:40 2012 - ...gracefully killing workers... >> Tue Apr 24 11:37:40 2012 - Gracefully killing worker 1 (pid: 5352)... >> Tue Apr 24 11:37:40 2012 - Gracefully killing worker 2 (pid: 5353)... >> Tue Apr 24 11:37:41 2012 - binary reloading uWSGI... >> Tue Apr 24 11:37:41 2012 - chdir() to /sample-app/0.1.0-dev >> Tue Apr 24 11:37:41 2012 - closing all non-uwsgi socket fds > 2 (max_fd = >> 1024)... >> Tue Apr 24 11:37:41 2012 - found fd 3 mapped to socket 0 (127.0.0.1:9999) >> Tue Apr 24 11:37:41 2012 - running /usr/local/uwsgi-1.2-rc2/uwsgi >> [uWSGI] getting INI configuration from /sample-app/current/bin/uwsgi.ini >> Tue Apr 24 11:37:41 2012 - *** Starting uWSGI 1.2-rc2 (64bit) on [Tue Apr >> 24 11:37:41 2012] *** >> Tue Apr 24 11:37:41 2012 - compiled with version: 4.6.1 on 22 April 2012 >> 09:37:20 >> Tue Apr 24 11:37:41 2012 - current working directory: >> /sample-app/0.1.0-dev >> Tue Apr 24 11:37:41 2012 - detected binary path: >> /usr/local/uwsgi-1.2-rc2/uwsgi >> Tue Apr 24 11:37:41 2012 - your memory page size is 4096 bytes >> Tue Apr 24 11:37:41 2012 - building mime-types dictionary from file >> /etc/mime.types...Tue Apr 24 11:37:41 2012 - 530 entry found >> Tue Apr 24 11:37:41 2012 - detected max file descriptor number: 1024 >> Tue Apr 24 11:37:41 2012 - lock engine: pthread robust mutexes >> Tue Apr 24 11:37:41 2012 - *** Cache subsystem initialized: 64MB (key: >> 2096 bytes, keys: 2096000 bytes, data: 65536000 bytes) preallocated *** >> Tue Apr 24 11:37:41 2012 - uwsgi socket 0 inherited INET address >> 127.0.0.1:9999 fd 3 >> Tue Apr 24 11:37:41 2012 - Python version: 2.7.2+ (default, Oct 4 2011, >> 20:41:12) [GCC 4.6.1] >> Tue Apr 24 11:37:41 2012 - Python main interpreter initialized at >> 0x15403b0 >> Tue Apr 24 11:37:41 2012 - your server socket listen backlog is limited >> to 100 connections >> Tue Apr 24 11:37:41 2012 - *** Operational MODE: preforking *** >> Tue Apr 24 11:37:41 2012 - WSGI app 0 (mountpoint='') ready in 0 seconds >> on interpreter 0x15403b0 pid: 5335 (default app) >> Tue Apr 24 11:37:41 2012 - *** uWSGI is running in multiple interpreter >> mode *** >> Tue Apr 24 11:37:41 2012 - gracefully (RE)spawned uWSGI master process >> (pid: 5335) >> Tue Apr 24 11:37:41 2012 - spawned uWSGI worker 1 (pid: 5359, cores: 1) >> Tue Apr 24 11:37:41 2012 - spawned uWSGI worker 2 (pid: 5360, cores: 1) >> Tue Apr 24 11:37:41 2012 - cache sweeper thread enabled >> Tue Apr 24 11:37:42 2012 - *** /sample-app/current/bin/uwsgi-restart has >> been touched... grace them all !!! *** >> Tue Apr 24 11:37:42 2012 - ...gracefully killing workers... >> Tue Apr 24 11:37:42 2012 - Gracefully killing worker 1 (pid: 5359)... >> Tue Apr 24 11:37:42 2012 - Gracefully killing worker 2 (pid: 5360)... >> >> >> uWSGI processes have been launched as follows: >> >> /usr/local/uwsgi-1.2-rc2/uwsgi --ini /sample-app/current/bin/uwsgi.ini >> --wsgi-file /sample-app/current/webapp/app.py --touch-reload >> /sample-app/current/bin/uwsgi-restart --pidfile /sample-app/uwsgi.pid >> --daemonize /sample-app/var/log/out.log >> >> I sent "touch /sample-app/current/bin/uwsgi-restart" ONCE after moving >> code to the server to ask for a restart. But I dont understand why uWSGI >> 1.2 can not keep track of that action correctly >> >> >> When I downgraded wWSGI to 1.1.2, I found that the issue disappeared. >> >> I deployed uWSGI server on an Ubuntu 11 Oneiric VM (a Linode instance) >> >> Is this a bug? >> >> Thanks >> >> Dinh >> >> > > > -- > Spica Framework: http://code.google.com/p/spica > http://www.twitter.com/pcdinh > http://groups.google.com/group/phpvietnam > -- Spica Framework: http://code.google.com/p/spica http://www.twitter.com/pcdinh http://groups.google.com/group/phpvietnam
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
