Hi,
I am using web2py as framework for my web application and using the
built-in scheduler for the user tasks. They are working fine for more than
one years.
During the recent several days, I found that whenever I start a task to
scheduler, the apache web server is not working, it is stuck in
Hi,
I have a web application hosted on AWS EC2 with Apache2. I plan to use
web2py scheduler for some heavy tasks with user input files. Now I only use
some small tasks like "wc -c" to test the functions of scheduler. It seems
that the submitted tasks are always QUEUED and the status never chang
; On Monday, September 29, 2014 4:37:53 PM UTC+2, Pengfei Yu wrote:
>>
>> Hi,
>>
>> I have a web application hosted on AWS EC2 with Apache2. I plan to use
>> web2py scheduler for some heavy tasks with user input files. Now I only use
>> some small tasks like &
://stackoverflow.com/questions/23916413/celery-parallel-distributed-task-with-multiprocessing),
Are those features also included in Scheduler?
Thanks!
On Wednesday, October 1, 2014 3:16:57 AM UTC-4, Niphlod wrote:
>
> On Tuesday, September 30, 2014 3:42:41 PM UTC+2, Pengfei Yu wrote:
>
>
single command like scheduler.delete_task(uuid) to do that. I am
not sure if scheduler.terminate(), scheduler.stop_task() or scheduler.kill
can do that.
On Friday, October 3, 2014 2:23:22 AM UTC-4, Niphlod wrote:
>
>
>
> On Wednesday, October 1, 2014 4:34:08 PM UTC+2, Pengfei Yu wro
D)
db(db.project.processID==processID).delete()
task = db.scheduler_task(db.scheduler_task.uuid==processID)
db(db.scheduler_run.task_id==task.id).delete()
db(db.scheduler_task.uuid==processID).delete()
On Saturday, October 4, 2014 2:51:42 PM UTC-4, Niphlod wrote:
>
> On Friday, October
Hi,
I am using the SOAP service provided by web2py to create a simple web
service for my web application. The document provide a example of using
"pysimplesoap" to consume the created SOAP web service. The code is like
below:
>>> from gluon.contrib.pysimplesoap.client import SoapClient
>>> cli
good enough.
Thanks!
On Friday, November 21, 2014 6:16:45 PM UTC-5, Dave S wrote:
>
>
>
> On Thursday, November 20, 2014 6:49:18 AM UTC-8, Pengfei Yu wrote:
>>
>> Hi,
>>
>> I am using the SOAP service provided by web2py to create a simple web
>> service
: No subject alternative names
present while opening stream from
https://aa.bb.cc.dd//default/call/soap?WSDL.
Here aa.bb.cc.dd is a public ip address. The web2py application is host on
amazon EC2.
Thanks!
On Monday, November 24, 2014 3:24:25 PM UTC-5, Pengfei Yu wrote:
>
> H
Cool! Thanks very much for sharing, Dave!
On Tuesday, November 25, 2014 2:26:47 PM UTC-5, Dave S wrote:
>
>
>
> On Monday, November 24, 2014 12:24:25 PM UTC-8, Pengfei Yu wrote:
>>
>> Hi Dave,
>>
>> Thanks very much for your reply! Could you give a more detail
Hi Niphlod,
Thanks for your reply! The problem is the 5681 is taking the task 1 and it
is RUNNING (See the worker stats of worker 1). But at the same time, the
task is still assigned to 5681, but not two other ACTIVE workers, 5685 and
5690. I previously thought the reason might be in the status
Hi Niphlod,
I found a strange situation even using the "testtask".
Here are two different scenarios. In the first scenario, the two test tasks
can be run concurrently as in my last reply. In the second scenario, the
two test tasks will be assigned to the same worker, although the worker is
alr
Wow! Thanks Niphlod for your kind and efficient helps. And I appreciate
your praise words to me. This is very encouraging for an amateur python-er.
In my real-word application, I used MySQL database from AWS RDS. Do you
think if it will also cause "concurrent" issue?
I see in the gist that onl
Yeah, I just made it work. Since I used Apache2 to host web2py in EC2
instance, after updating the scheduler.py file, I need to restart the
Apache2 server by:
sudo service apache2 restart
and then restart the web2py-scheduler by:
sudo stop web2py-scheduler
sudo start web2py-scheduler
(th
Hi I am using web2py scheduler. I have a project saved in git and then I
cloned this git repository to another new instance (server). In the new
server, five scheduler workers (known from the ip address in the
worker_name) from the old server are always there. When never I delete
them, they wil
Hi,
I am using "auth.enable_record_versioning" to track the version of each
record's update for my database tables. It works great now to keep
different previous versions of a record in the "*_archive" tables. For my
application, I also need features to allow some users to revert one record
ba
t records on the scheduler_worker
> table. watch the last_heartbeat column and see if it changes. If it's
> changing, the workers are still running somewhere and accessing your
> database.
>
> On Friday, April 24, 2015 at 9:24:59 PM UTC+2, Pengfei Yu wrote:
>>
>>
Hi,
I have a scheduler problem after transferring our web2py server in another
region. We used EC2 for the server and RDS for the mySql database. It works
fine in original region. Right now we move the server and the database to
another region with new AWS EC2 and new RDS. I used the web2py-sch
Hi Niphlod and Dave,
I think the worker is deleted because the the last heartbeat doesn't change
for a while. When I comment out the line "#dead_workers.delete()" in
gluon/schdeuler.py, the task is stuck as QUEUED without new run record
created. And the worker supposed to be deleted with the la
15277: task completed or failed
DEBUG:web2py.scheduler.ip-20-20-10-190#15277: recording task report in db
(COMPLETED)
INFO:web2py.scheduler.ip-20-20-10-190#15277:task completed (COMPLETED)
DEBUG:web2py.scheduler.ip-20-20-10-190#15277:looping...
Thanks very much!
On Thursday, April 30, 2015 at 8:47:
il 30, 2015 at 8:47:48 AM UTC-4, Niphlod wrote:
>
>
>
> On Wednesday, April 29, 2015 at 11:53:56 PM UTC+2, Pengfei Yu wrote:
>>
>> Hi Niphlod and Dave,
>>
>> I think the worker is deleted because the the last heartbeat doesn't
>> change for a while. Whe
go on travis-ci: glad
> you worked it out, but I'm really unsure why different regions should carry
> different versions of the same operating system.
>
> On Thursday, April 30, 2015 at 6:57:08 PM UTC+2, Pengfei Yu wrote:
>>
>> Hi Niphlod,
>>
>> I think I
Hi,
I am trying to access a web service which requires windows NTLM
authorization. I am able to successfully implement it using suds python
library with following code:
from suds.transport.http import *
from suds.transport.https import WindowsHttpAuthenticated
from suds.client import *
import
source/browse/pysimplesoap/client.py?r=6ed06397b4f0c1894156ee5d0a1c165f80ed6a68
>
>
> On Monday, June 8, 2015 at 7:28:39 AM UTC-7, Pengfei Yu wrote:
>>
>> Hi,
>>
>> I am trying to access a web service which requires windows NTLM
>> authorization. I am able
uot;https://mywebservice";
>
> curl = pycurl.Curl()
> curl.setopt(pycurl.URL, url)
> curl.setopt(pycurl.SSL_VERIFYPEER, 0)
>
> curl.setopt(pycurl.HTTPAUTH, pycurl.HTTPAUTH_NTLM)
> curl.setopt(pycurl.USERPWD, "{}:{}".format(name, pwd))
>
> curl.perform()
>
ent(wsdl=URL,proxy=proxy)
On Tuesday, June 9, 2015 at 3:32:03 PM UTC-4, Derek wrote:
>
> alright, well you are going to have to modify the client.py for
> pysimplesoap then in order to achieve this.
> I'd suggest you add a variable to the class like 'USERPWD' and popula
Hi,
I want to change the target namespace to "http://tempuri.org/"; in the SOAP
WSDL xml file.
>From the pysimplesoap's server.py, I see that I can specify it in
>SoapDispatcher
class with namespace parameter. But I wonder how can I specify it in web2py
controller's "@service.soap" decorator
; isn't a simple
>
> def what_you_serve():
> ..foo bar
> response.namespace = 'http://tempuri.org/'
> return dict(a=1)
>
> working ?
>
> On Thursday, June 11, 2015 at 6:36:31 PM UTC+2, Pengfei Yu wrote:
>>
>> Hi,
>>
>&g
enough.
>
> On Thursday, June 11, 2015 at 9:39:32 PM UTC+2, Pengfei Yu wrote:
>>
>> Yeah, you are right. Stupid question. I am not familiar with how response
>> works.
>>
>> def call():
>> response.namespace = 'http://tempuri.org/'
>>
29 matches
Mail list logo
