That's fine. But it makes your opinion irrelevant. Very few program in
isolation.
On Monday, January 10, 2011 6:36:18 AM UTC+2, Anthony wrote:
On Sunday, January 9, 2011 1:24:02 AM UTC-5, Graham Dumpleton wrote:
You guys really just got to learn to do your own thing and not treating
it like a crusade where you have to convert the world.
But that's exactly the
On Friday, July 8, 2011 3:25:45 AM UTC-4, cjrh wrote:
On Monday, January 10, 2011 6:36:18 AM UTC+2, Anthony wrote:
On Sunday, January 9, 2011 1:24:02 AM UTC-5, Graham Dumpleton wrote:
You guys really just got to learn to do your own thing and not treating
it like a crusade where you
On Friday, 8 July 2011 16:05:54 UTC+2, Anthony wrote:
On Friday, July 8, 2011 3:25:45 AM UTC-4, cjrh wrote:
On Monday, January 10, 2011 6:36:18 AM UTC+2, Anthony wrote:
On Sunday, January 9, 2011 1:24:02 AM UTC-5, Graham Dumpleton wrote:
You guys really just got to learn to do your own
On Friday, July 8, 2011 3:47:09 PM UTC-4, cjrh wrote:
*Why* should we care how many users we have?
Again, this is not the most important thing, but the number of users is
not entirely without consequence either. Generally, more users will
translate into more expert contributors and
Sorry cjrh, but the number of users and the perception of the project DO
matter. Some of us are building businesses around Web2py and need to feel
comfortable that the project has longevity, that we can hire and retain
engineers, that we can find resources if we need them, etc. Not everyone is
Have I missed some new controversial reddit thread?
On Jul 8, 4:18 pm, pbreit pbreitenb...@gmail.com wrote:
Sorry cjrh, but the number of users and the perception of the project DO
matter. Some of us are building businesses around Web2py and need to feel
comfortable that the project has
No, or rather, not that I am aware. We are discussing, I think, the
principal of the matter.
On Friday, 8 July 2011 23:18:57 UTC+2, pbreit wrote:
You need to think slightly bigger than your own personal projects.
Why should I? The bigger community does not concern me. I contribute to
web2py for entirely selfish reasons, because it want it to be the best tool
for me to use for my
For some reason I missed the rest of this discussion. Just a quick follow
up.
+ I upgraded psycopg2 from 2.0.7 (default in Debian 5) to the latest
version, 2.4. This manual installation was smoother than I thought.
+ Result: preliminary stress tests show that the problem *disappeared*.
On Mar 4, 2011, at 9:31 AM, VP wrote:
For some reason I missed the rest of this discussion. Just a quick follow
up.
+ I upgraded psycopg2 from 2.0.7 (default in Debian 5) to the latest version,
2.4. This manual installation was smoother than I thought.
+ Result: preliminary stress
To be precise, RSS started with about 32MB (with an apache restart)
and starts crawling up to 80MB/process with aforementioned testing.
And If I remember correctly, it stayed that way over night and did not
get released.
As I said, I will do further testing with this toy example and with my
real
On Mar 4, 2011, at 9:46 AM, VP wrote:
To be precise, RSS started with about 32MB (with an apache restart)
and starts crawling up to 80MB/process with aforementioned testing.
And If I remember correctly, it stayed that way over night and did not
get released.
As I said, I will do further
oops, it looks like that last post was supposed to be for the other
thread (potential memory leaks).
On Mar 4, 12:28 pm, Jonathan Lundell jlund...@pobox.com wrote:
On Mar 4, 2011, at 9:46 AM, VP wrote:
To be precise, RSS started with about 32MB (with an apache restart)
and starts
Question: Could provide you provide an app that generates the error?
Answer: Check Appliance Customer Relationship Management.
db = DAL(postgres://postgres:
Error Snapshot :
type 'exceptions.RuntimeError'(Failure to connect, tried 5 times: global
name 'psycopg2' is not defined)
The problem here is that you did not install the psycopg2 driver for
postgresql.
On Feb 16, 2:28 am, Ahmed Bani taz...@gmail.com wrote:
Question: Could provide you provide an app that generates the error?
Answer: Check Appliance Customer Relationship Management.
db =
Problem solved:
# Download : hg clone https://web2py.googlecode.com/hg/ web2py# Follow the
instructions:
Title : Using psycopg2 with virtualenv on UbuntuLink:
http://www.saltycrane.com/blog/2009/07/using-psycopg2-virtualenv-ubuntu-jaunty/
Check your syntax :
# *db* =
Looks like Jonathan may be the winner here. I think VP raised the
issue so he should decide whether the issue is solved.
Is anybody else having problems after upgrade to the latest psycopg2?
If this problem was dear to you any symbolic contribution towards the
prize will be appreciated.
Massimo
On Feb 16, 2011, at 3:07 PM, Massimo Di Pierro wrote:
Looks like Jonathan may be the winner here. I think VP raised the
issue so he should decide whether the issue is solved.
Is anybody else having problems after upgrade to the latest psycopg2?
If this problem was dear to you any symbolic
Greetings.
I have tried to replicate the error and have had no
exicto.
Environment:
virtual server 1: debian ssl web2py
virtual server 2: debian ssl postgresql
Application:
simple queries and throwing 2
results.
tool:
Jmeter:
Threads 1200
0.2 seconds upload
Díaz Luis
TSU Analisis de Sistemas
On Feb 14, 2011, at 9:48 AM, Luis Díaz wrote:
Greetings.
I have tried to replicate the error and have had no
exicto.
Thanks. What version of psycopg2 are you using?
Environment:
virtual server 1: debian ssl web2py
virtual server 2: debian ssl postgresql
Application:
simple
I have installed:
python-psycopg2/lenny update 2.0.7-4
Question:
What is the funsion of psycopg2?
Díaz Luis
TSU Analisis de Sistemas
Universidad de Carabobo
Facultad de
Odontologíahttp://www.odontologia.uc.edu.ve/index.php?option=com_contentview=articleid=102Itemid=85
2011/2/14 Jonathan
ready to investigate:
psycopg2
http://wiki.postgresql.org/wiki/Using_psycopg2_with_PostgreSQL
The error could be caused by a bad query
developed?
Could provide an app that generates the error?
Díaz Luis
TSU Analisis de Sistemas
Universidad de Carabobo
Facultad de
On Feb 14, 2011, at 10:24 AM, Luis Díaz wrote:
ready to investigate:
psycopg2
http://wiki.postgresql.org/wiki/Using_psycopg2_with_PostgreSQL
The error could be caused by a bad query
developed?
Could provide an app that generates the error?
I'm not using it myself; I'm not sure what
In any case, please check whether upgrading postgresql for you solves
the problem. It is possible that mysqldb has/had the same issue.
I am very skeptical this is a web2py issue. So we should try isolate
the problem.
Massimo
On Feb 12, 12:12 am, Anthony abasta...@gmail.com wrote:
On Saturday,
On Feb 11, 2011, at 10:12 PM, Anthony wrote:
On Saturday, February 12, 2011 1:03:48 AM UTC-5, Jonathan Lundell wrote:
On Feb 10, 2011, at 6:19 AM, Massimo Di Pierro wrote:
I offer $300 to whoever can identify within 3 weeks and without
ambiguity the cause of this problem. The bounty
Greetings.
I could create a web2py.app.error.w2p
and detail the specifications of the environment,
I will try to put him eye to the issue.
I am a rookie .. but I would try
Díaz Luis
TSU Analisis de Sistemas
Universidad de Carabobo
Facultad de
FWIW I am on Ubuntu 10.04 with all patches applied and could not reproduce
the above problem when I tried. The version of python-psycopg2 from the
standard repository is 2.0.13. Not an iron-clad guarantee because something
else could be at play but at least a data point. I also drove the
On Feb 12, 2011, at 8:33 AM, Luis Díaz wrote:
I could create a web2py.app.error.w2p
and detail the specifications of the environment,
I will try to put him eye to the issue.
I am a rookie .. but I would try
Thanks, Luis.
On Feb 12, 2011, at 8:46 AM, ron_m wrote:
FWIW I am on Ubuntu 10.04 with all patches applied and could not reproduce
the above problem when I tried. The version of python-psycopg2 from the
standard repository is 2.0.13. Not an iron-clad guarantee because something
else could be at play but
Translation error .. sorry.
I could not ..
might wonder if any of you?
Díaz Luis
TSU Analisis de Sistemas
Universidad de Carabobo
Facultad de
Odontologíahttp://www.odontologia.uc.edu.ve/index.php?option=com_contentview=articleid=102Itemid=85
2011/2/12 Jonathan Lundell jlund...@pobox.com
On Feb 10, 2011, at 6:19 AM, Massimo Di Pierro wrote:
I offer $300 to whoever can identify within 3 weeks and without
ambiguity the cause of this problem. The bounty applies even if the
problem turns out to be not in web2py but in one of the Python
modules, in Apache or in the mod_wsgi
On Saturday, February 12, 2011 1:03:48 AM UTC-5, Jonathan Lundell wrote:
On Feb 10, 2011, at 6:19 AM, Massimo Di Pierro wrote:
I offer $300 to whoever can identify within 3 weeks and without
ambiguity the cause of this problem. The bounty applies even if the
problem turns out to be not
Great!!
I also had threads=25 and changed this to threads=1 processes=5,
so it makes sense that I was encountering the same problem. It sounds
like something in web2py might not be thread-safe. The next time I
run a production test I will report if this fixes the problem.
On Feb 10, 2:38 pm,
This is a very important test. I believe web2py to be thread safe and
in fact we thread.lock every access to shared objects even if
operations are atomic, yet I will review it in detail.
Massimo
On Feb 10, 12:38 am, VP vtp2...@gmail.com wrote:
Alright people short answer: I think I figured
I offer $300 to whoever can identify within 3 weeks and without
ambiguity the cause of this problem. The bounty applies even if the
problem turns out to be not in web2py but in one of the Python
modules, in Apache or in the mod_wsgi implementation. It does not
apply if the problem is due to known
Good work.
You mentioned that you're using Debian Lenny. What version of Python? 2.5.2?
And what version of psycopg2?
On Feb 9, 2011, at 10:38 PM, VP wrote:
Alright people short answer: I think I figured this out (at least
with my configuration)
After testing various
The modules I used are all standard via installation with apt-get.
Python is 2.5.2, and psycopg2 is 2.0.7
On Feb 10, 9:58 am, Jonathan Lundell jlund...@pobox.com wrote:
Good work.
You mentioned that you're using Debian Lenny. What version of Python? 2.5.2?
And what version of psycopg2?
On
On Feb 10, 2011, at 11:18 AM, VP vtp2...@gmail.com wrote:
The modules I used are all standard via installation with apt-get.
Python is 2.5.2, and psycopg2 is 2.0.7
Upgrade psycopg2 to at least 2.0.8 and see if that doesn't fix the fault.
On Feb 10, 9:58 am, Jonathan Lundell
Alright people short answer: I think I figured this out (at least
with my configuration)
After testing various configurations, here's the result with: ab -kc
100 -t 20 https://domain.com/imageblog/default/index/ (same
imageblog app, 100 connections, 20 seconds stress test).
Two
Massimo:
Have you gotten a chance to look into this issue (related to
scalability)?
Thanks.
Not yet. I do not have the problem on my production server. I need to
setup a new VM to test this. Hopefully tomorrow.
Massmimo
On Jan 22, 1:13 pm, VP vtp2...@gmail.com wrote:
Massimo:
Have you gotten a chance to look into this issue (related to
scalability)?
Thanks.
UPDATE: I am able to reproduce this Premature end of script headers:
wsgihandler.py error with a slightly modified app based on the image
blog in the web2py book. I modified it so that images are shown in
the index page, instead of having just the titles listed.
Testing using: ab -kc 100 -t 20
What is curious is that RAM is still available, with this error.
Monitoring CPU (using top) shows CPU % is about 70% for apache2 (70%
is probably capped by my VPS host, given to each VPS slice).
And this occurs for a very simple app. I hope Massimo or someone else
can reproduce this error with
I forgot to mention that in this imageblog app, I only have 10 images,
and no comment. I.e. a very small database.
Here are the 10 images:
http://imgur.com/u6gwulkJNwjDsjQxHIIN99AqEII5Pvh1gxagEcoJru2ucY3583C
Thanks this is very helpful and I will try reproduce it.
Are you running the trunk version or which other version?
Massimo
On Jan 19, 12:45 pm, VP vtp2...@gmail.com wrote:
UPDATE: I am able to reproduce this Premature end of script headers:
wsgihandler.py error with a slightly modified app
Yes, this echos my experiences exactly! Using apache ab benchmark
alone would NOT trigger the error. I had plenty of RAM available.
Seems to be a concurrency bug.
On Jan 19, 10:53 am, VP vtp2...@gmail.com wrote:
What is curious is that RAM is still available, with this error.
Monitoring CPU
I am running the official version 1.91.6.
On Jan 19, 1:24 pm, Massimo Di Pierro massimo.dipie...@gmail.com
wrote:
Thanks this is very helpful and I will try reproduce it.
Are you running the trunk version or which other version?
Massimo
On Jan 19, 12:45 pm, VP vtp2...@gmail.com wrote:
It seems the links to the images don't work anymore. You can just
picked any 10 images, but again the ones I used are:
http://i.imgur.com/u6gwu.jpg
http://i.imgur.com/kJNwj.jpg
http://i.imgur.com/DsjQx.jpg
http://i.imgur.com/HIIN9.jpg
http://i.imgur.com/9AqEI.jpg
http://i.imgur.com/I5Pvh.jpg
Are you using connection pooling? Can I see the line db = DAL(...)?
On Jan 16, 2:24 pm, VP vtp2...@gmail.com wrote:
Kenneth (see post above) had the same problem with MySQL.
On Jan 16, 3:55 am, ron_m ron.mco...@gmail.com wrote:
Is there any chance to try another server based database
Here it is with private information replaced with generic information.
if request.env.web2py_runtime_gae:# if running on Google
App Engine
db = DAL('gae') # connect to Google
BigTable
session.connect(request, response, db = db) # and store sessions
You should really have
db = DAL('postgres://name:password@localhost:5432/db',pool_size=20)
The reason is that client-server databases may set a max to number of
open connections and it takes time to perform the 3-way handshake to
establish a new connection at every http request. Without pooling
Thanks. I fixed this. The performance seems to be a little better
(requests/second), but the error is still there.
On Jan 17, 2:20 pm, Massimo Di Pierro massimo.dipie...@gmail.com
wrote:
You should really have
db = DAL('postgres://name:password@localhost:5432/db',pool_size=20)
The reason
I have pool_size=100, and get the error.
On Jan 17, 12:20 pm, Massimo Di Pierro massimo.dipie...@gmail.com
wrote:
You should really have
db = DAL('postgres://name:password@localhost:5432/db',pool_size=20)
The reason is that client-server databases may set a max to number of
open connections
Can you share any more info you have about the errors?
Does it happen with every action? Is there one in particular? What
does it do? Do you use session? Do you use cache? Can you show us any
code? Can you build a minimalist app to reproduce it? Are there a
minimum number of steps to reproduce
The problem for me is that this occurs on a webapp used by mechanical
turk, and it fails when I have hundreds of mechanical turkers using my
app... which only happens when I pay them hundreds of dollars. So
it's hard to reproduce right now without hundreds of dollars.
I am excited to try using
How old web2py? We have had bugs in the past that may cause your
problem.
You should try upgrade.
Massimo
On Jan 17, 6:58 pm, Michael Toomim too...@gmail.com wrote:
The problem for me is that this occurs on a webapp used by mechanical
turk, and it fails when I have hundreds of mechanical
1.74.5. I will upgrade when I can reproduce the problem locally.
On Jan 17, 5:13 pm, Massimo Di Pierro massimo.dipie...@gmail.com
wrote:
How old web2py? We have had bugs in the past that may cause your
problem.
You should try upgrade.
Massimo
On Jan 17, 6:58 pm, Michael Toomim
Is there any chance to try another server based database such as MySQL.
Since SQLite did not exhibit a problem that is a valid data point but it is
an embedded database so called directly by the web2py server code instead of
using a driver. There is a possibility there is a problem with the
I can't seem to get it to generate an error running on PostgreSQL and the
apache logs show nothing. I upped the ab time ( -t ) to 100 and then used
the application. It wasn't very responsive but then the ab average was 8+sec
on the home page which just displays a message. I am using the default
Kenneth (see post above) had the same problem with MySQL.
On Jan 16, 3:55 am, ron_m ron.mco...@gmail.com wrote:
Is there any chance to try another server based database such as MySQL.
Since SQLite did not exhibit a problem that is a valid data point but it is
an embedded database so called
To follow up on this issue, I think it might be related to db and/or
DAL.
+ I don't think it relates to exhausting RAM or too many open files.
Using lsof to monitor open files during stress test, with 200
concurrent channels (ab), I witnessed up to 11,000 open files (most
are apache2). There are
I can´t be sure which application it is. But Iĺl do some stresstests
later today and report more.
Kenneth
could this be a timeout issue? Could it be the app causes a deadlock
in the db? What app is this?
On Jan 11, 10:58 am, Kenneth Lundströmkenneth.t.lundst...@gmail.com
wrote:
I'm getting
Can I see the error? Is there a traceback? Is the db server on the
machine?
Massimo
On Jan 9, 11:30 am, VP vtp2...@gmail.com wrote:
It is indeed the case that there was a segmentation fault, reported in
apache error log.
Perhaps, it's not clear, but this problem occurs under posgres under
Update:
+ There seems to be no web2py error. Thus, no traceback.
+ I don't remember if I got this error Premature end of script
headers: wsgihandler.py ) with sqlite, but having just tested again
with sqlite, I didn't get this error. At the moment, this error only
occurred with postgres
I'm getting the same Premature end of script on a CentOS 5.?, MySQL, WSGI and
Apache.
Never done any stresstests, I'll try later to day.
Kenneth
- Ursprungsmeddelande -
Update:
+ There seems to be no web2py error. Thus, no traceback.
+ I don't remember if I got this error
could this be a timeout issue? Could it be the app causes a deadlock
in the db? What app is this?
On Jan 11, 10:58 am, Kenneth Lundström kenneth.t.lundst...@gmail.com
wrote:
I'm getting the same Premature end of script on a CentOS 5.?, MySQL, WSGI and
Apache.
Never done any stresstests, I'll
I'm still having this problem too (previous posts linked below). I
would love to find a solution. I'm not sure how to debug.
VP: Can you provide instructions for reproducing this bug using ab? I
had trouble using ab in the past. I am also on a VPS.
Since my last post (linked below), I have
I don't know if it is worth mentioning but as a Ubuntu 10.04.1 user, I
noticed the 8.4.6 update to PostgreSQL was pushed by Ubuntu near the end of
December.
http://www.postgresql.org/docs/8.4/static/release-8-4-6.html
first item of the release notes mention the database can fail on some file
Thanks, I just investigated this, but it looks like it did not fix the
problem.
In 8.4.6 Postgres changed the default wal_sync_method to fdatasync,
because the old default open_datasync failed on ext4. I use ext3 (on
ubuntu 9.10), but I tried changing this option in my postgres database
For the record. I do not think I never said my viewpoint is the best.
I do not recall other people of this list doing it either. I just
state my viewpoint. I usually limit myself to one of the follow:
- mention web2py in a thread related to web frameworks
- provide an example of how web2py does
It is indeed the case that there was a segmentation fault, reported in
apache error log.
Perhaps, it's not clear, but this problem occurs under posgres under
debian lenny, not sqlite. I am not running web2py as a CGI script. I
am using the web2py deployment script (for setting up apache and
On Sunday, January 9, 2011 1:24:02 AM UTC-5, Graham Dumpleton wrote:
You guys really just got to learn to do your own thing and not treating
it like a crusade where you have to convert the world.
But that's exactly the problem -- web2py is trying to do its own thing, and
there is a vocal
I came to Web2py recently and I can definitely see how the promotion of
Web2py in places like Reddit would rub people the wrong way. Much of the
hostility seems related to how Web2py is promoted, not to its technical
merits.
You were possibly using a an old version of sqlite which isn't safe to use
in a multithreaded configuration.
The MPM settings are not going to help in this case as that error could only
come about because you are using mod_wsgi daemon mode and so application is
running in distinct process and
Graham, welcome. Careful, though -- we might
converthttp://twitter.com/GrahamDumpleton/status/23120780938190848you. ;-)
http://twitter.com/GrahamDumpleton/status/23120780938190848
On Saturday, January 8, 2011 10:59:37 PM UTC-5, Graham Dumpleton wrote:
You were possibly using a an old
On Sunday, January 9, 2011 3:54:37 PM UTC+11, Anthony wrote:
Graham, welcome. Careful, though -- we might
converthttp://twitter.com/GrahamDumpleton/status/23120780938190848you. ;-)
http://twitter.com/GrahamDumpleton/status/23120780938190848
I have been posting here for quite a long
Graham. We all appreciate your expertise here and appreciate people
who say what they think. Perhaps diplomacy is not our strength. You do
not need to justify your tweet. I though it was funny because - in my
view - it would apply equally well to some of the other frameworks.
On Jan 9, 12:24 am,
On Sunday, January 9, 2011 6:05:16 PM UTC+11, Massimo Di Pierro wrote:
Graham. We all appreciate your expertise here and appreciate people
who say what they think. Perhaps diplomacy is not our strength. You do
not need to justify your tweet. I though it was funny because - in my
view -
79 matches
Mail list logo
