Here's a run taken from a shell in which scheduler was run manually with
'-D 0' option enabled.
DEBUG:Tool: lines are loggers from within my models file tasks.py.
At the end I hit Ctrl-C to quit the scheduler process.
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:Tool:tasks.py:CB:runcmd: Output:[]
DEBUG:Tool:tasks.py:CB:createStack: Created Stack ID [47568150164590751]
DEBUG:Tool:tasks.py:deploy_project: Stack:[47568150164590751] created
DEBUG:Tool:tasks.py:insert_application_state Id:[47568150164590751]
DEBUG:Tool:tasks.py:CB:runcmd: Output:[]
DEBUG:Tool:tasks.py:deploy_project: Done
DEBUG:Tool:tasks.py:deploy: Done
DEBUG:Tool:tasks.py: new task report: COMPLETED
DEBUG:Tool:tasks.py: result: null
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814: freeing workers that have not
sent heartbeat
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814: freeing workers that have not
sent heartbeat
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814: freeing workers that have not
sent heartbeat
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814: freeing workers that have not
sent heartbeat
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814: freeing workers that have not
sent heartbeat
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814: freeing workers that have not
sent heartbeat
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
DEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat (RUNNING)
^CDEBUG:web2py.scheduler.centos-63#6814:........recording heartbeat
(RUNNING)
^CINFO:web2py.scheduler.centos-63#6814:catched
INFO:web2py.scheduler.centos-63#6814:die!
^CError in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib64/python2.6/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/lib64/python2.6/multiprocessing/util.py", line 269, in
_exit_function
p.join()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 119, in join
res = self._popen.wait(timeout)
File "/usr/lib64/python2.6/multiprocessing/forking.py", line 122, in wait
return self.poll(0)
File "/usr/lib64/python2.6/multiprocessing/forking.py", line 107, in poll
pid, sts = os.waitpid(self.pid, flag)
KeyboardInterrupt
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib64/python2.6/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/lib64/python2.6/multiprocessing/util.py", line 269, in
_exit_function
p.join()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 119, in join
res = self._popen.wait(timeout)
File "/usr/lib64/python2.6/multiprocessing/forking.py", line 122, in wait
return self.poll(0)
File "/usr/lib64/python2.6/multiprocessing/forking.py", line 107, in poll
pid, sts = os.waitpid(self.pid, flag)
KeyboardInterrupt
Here is the process list too.
[root@centos-63 databases]# ps -ef | grep web
root 6814 6782 0 05:24 pts/0 00:00:00 python web2py.py -K
APITool2 -D 0
root 6827 6814 0 05:25 pts/0 00:00:00 python web2py.py -K
APITool2 -D 0
root 6882 6864 0 05:26 pts/1 00:00:00 grep web
[root@centos-63 databases]#
After I Ctrl-C'd the manually started scheduler process, which would have
been 6814, the 6827 process continued to run.
I had to manually kill the 6827 process with a -9 to end it. A regular kill
6827 would not interrupt whatever it was doing...
Here are the final lines of the deploy method in the tasks.py file:
#
# Done
#
logger.debug('deploy: Done')
return
Thanks!
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
