you have very weird logging prefixes.... it doesn't seem you're doing
something wrong (that's just because you didn't past ANY code to support
you) but I'd like to see the "surrounding" lines of the scheduler log. If
it's too long just attach it.
On Wednesday, August 20, 2014 3:33:41 PM UTC+2, Stephen Weiss wrote:
>
>
> I have a scheduled task firing off that goes through its process and
> finishes.
> The following is output from the web2py-scheduler log file, which
> indicates that the task should be marked completed.
>
> 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
>
> The "deploy:Done" output is the last line prior to the return of the
> deploy task.
> The deploy method is that which is submitted to the scheduler to run.
>
> However, I still see the forked process still running
>
> root 5133 1 0 07:35 pts/4 00:00:05 /usr/bin/python
> /opt/web-apps/web2py/web2py.py -K APITool2
> root 5540 5133 0 08:25 pts/4 00:00:00 /usr/bin/python
> /opt/web-apps/web2py/web2py.py -K APITool2
>
> and the record from the scheduler_task table:
>
> 126|Tool/default|deploy|main|RUNNING|deploy|2f0c430b-5649-4c59-8442-e8bfbd2e472e|[]|{"environment":
>
> "1", "project": "2", "deployment_name": "testing"}|T|2014-08-20
> 08:25:17|2014-08-20 08:25:17||1|0|60|F|3600|0|0|0|2014-08-20
> 08:25:21|centos-63#5133
>
> What would prevent the process from completing? Is it not being "reaped"
> by the original scheduler process? Am I doing something wrong?
>
> 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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
