On Friday, November 4, 2016 at 10:44:31 PM UTC+1, Niphlod wrote:
>
> BTW: do your task write a lot on stdout/stderr and/or return huge results ?
>
Probably. I wrote into the log more than usual. :( Mostly DEBUGs - it's
possible to switch off them.
--
Resources:
- http://web2py.com
- http://web2
BTW: if I use os.kill(p.pid,signal.SIGKILL) instead of p.termiate()
everithing is fine.
11-04 08:40:59.521 [13556] web2py.Scheduler - DEBUG - MD: terminating (os
> kill)
> 11-04 08:40:59.521 [13556] web2py.Scheduler - DEBUG - MD: terminated
> 11-04 08:40:59.522 [13556] web2py.Scheduler - DEBUG
Sorry for using the term 'zombie'. In the context of unix it is misleading.
On Thursday, November 3, 2016 at 9:25:41 PM UTC+1, Niphlod wrote:
>
> From where I stand, if the result is the task being labelled as TIMEOUT
> (with the corresponding "task timeout" debug line), it can only be
> origina
@Niphlod: I decided one year ago to use web2py for our projects. And now I
have a problem and I have to solve it (shortly) - with or without the
group. You are so focused on the scheduler code itself. I search for any
hint to understand the problem. It doesn't helps me to know that the
mankind
That's all what I know. I have different RHEL systems (RH6,RH5) with
python 2.7.12 and MariaDB. Not realy exotic.
Thank you for your endurance
Erwn
>
> On Wednesday, November 2, 2016 at 10:53:58 AM UTC+1, Erwn Ltmann wrote:
>>
>> Dear all,
>>
>> I'
Dear all,
I'm astonished about a lot of processes as sub process of scheduler worker
are not finished.
pstree -p 16731
>
> bash(16731)---python2.7(24545)-+-python2.7(24564)---{python2.7}(24565)
>|-python2.7(24572)-+-python2.7(1110)
>
phlod wrote:
>
> sorry, but it doesn't really make sense.
> You're executing twice the same command (the call enclosed in len() and
> the actual .delete() call), which is the counter-arg for relaxing a
> pressured database environment.
>
> On Monday, October 31, 2016 at
Hi,
thank you for your reply.
@Pierre: MariaDB (in my case) handled deadlocks automaticly too. Good to
known, I don't have to be worry about that.
@Niphlod: I tried to beef up my database host. No effects. Another
suggestion is to prevent the cases for such situation. I did it by an
another e
Hi,
I have a deadlock after a while of running more than one worker, e.g.
output for both appearences:
10:29:07,903 [31505] Scheduler - ERROR - Error cleaning up
> 10:29:07,904 [31505] Scheduler - ERROR - (1213, u'Deadlock found when
> trying to get lock; try restarting transaction')
> 10:29:07
UTC+2, Dave S wrote:
>
>
>
> On Wednesday, September 7, 2016 at 5:30:49 PM UTC-7, Erwn Ltmann wrote:
>>
>> Hi,
>>
>> I'm used to create a new task for example:
>>
>> scheduler.queue_task(
>> "a_task",
>> pvars
Hi,
I'm used to create a new task for example:
scheduler.queue_task(
"a_task",
pvars = dict(csid=row.id, csname=row.name, action=row.action),
...
)
In the past (version 2.10.1), everything was fine. Within the current version
(2.14.6) I have some trouble. See this code for exa
hi everybody,
been starting with web2py weeks ago and now my first unsolved issue appears.
There is an action to handle a custom form (as skeleton code here):
form = FORM()
for row in some_data_source:
if row in relevant_data_source:
form.append( INPUT(...var...) )
if form.accepts(...):
12 matches
Mail list logo
