Ick. Ack. I've switched from zope's standalone webserver to apache + fastcgi + zope and so far it looks stable and doesn't go wild with that accept error. But I stumbled on another problem -- images do not upload correctly at all. Then stared apache at port 80 and zope at 8080. If I upload image through site:8080/manage interface it uploads fine. But if I upload image through site/manage (or my own cgi form), image corrupts on the way! When I export both good and bad images into xml format and diff them, these files are slightly different in binary part. What can corrupt image on its way through apache and fastcgi? Of couse, it's easy to say use 8080 port to update the site. Unfortunately, I can't run zope at 8080 port, because of previous bug with accept :( I can't find that bug because it happens only once in two or three days, only under normal conditions (i.e. I ran httperf and put a big load on the site... everything worked okay, only to hang several hours later). And since my boss is very unhappy with webserver going down at odd hours when I'm unavailable, I can't really debug this situation :( -- Roman V. Isaev http://www.aroma.ru System Administrator P.S. My configuration is: Apache/1.3.20 mod_fastcgi/2.2.10 zope 2.4.0 python 2.1.1 openbsd 2.7
Hi Roman, I believe the "accept" bug you're referring to may be due to a potential problem in the asyncore module that ships with Python 2.1. In the past, Zope shipped with its own asyncore module, but when asyncore was updated in the Python core (in 2.1, I believe), we dropped our updated copy from 2.4. If possible, I'd try placing a revision of the asyncore.py file into Zope's ZServer/medusa directory. I'd try this one: http://cvs.zope.org/Zope/ZServer/medusa/Attic/asyncore.py?only_with_tag=Zope... Run for a while with that to see if the problem disappears. Please let us know if it does or doesn't if you try it! - C Roman V. Isaev wrote:
Ick. Ack. I've switched from zope's standalone webserver to apache + fastcgi + zope and so far it looks stable and doesn't go wild with that accept error. But I stumbled on another problem -- images do not upload correctly at all. Then stared apache at port 80 and zope at 8080. If I upload image through site:8080/manage interface it uploads fine. But if I upload image through site/manage (or my own cgi form), image corrupts on the way! When I export both good and bad images into xml format and diff them, these files are slightly different in binary part. What can corrupt image on its way through apache and fastcgi?
Of couse, it's easy to say use 8080 port to update the site. Unfortunately, I can't run zope at 8080 port, because of previous bug with accept :( I can't find that bug because it happens only once in two or three days, only under normal conditions (i.e. I ran httperf and put a big load on the site... everything worked okay, only to hang several hours later). And since my boss is very unhappy with webserver going down at odd hours when I'm unavailable, I can't really debug this situation :(
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
As I said in my first post about this problem, it happened both under zope 2.3.3 python 1.5.2 and zope 2.4.0 python 2.1.1. Actually, it was the bug that forced me to move to 2.4.0 in hope to get rid of it... On 08/24, Chris McDonough wrote:
Hi Roman,
I believe the "accept" bug you're referring to may be due to a potential problem in the asyncore module that ships with Python 2.1. In the past, Zope shipped with its own asyncore module, but when asyncore was updated in the Python core (in 2.1, I believe), we dropped our updated copy from 2.4.
If possible, I'd try placing a revision of the asyncore.py file into Zope's ZServer/medusa directory. I'd try this one: http://cvs.zope.org/Zope/ZServer/medusa/Attic/asyncore.py?only_with_tag=Zope...
Run for a while with that to see if the problem disappears. Please let us know if it does or doesn't if you try it!
- C
Roman V. Isaev wrote:
Ick. Ack. I've switched from zope's standalone webserver to apache + fastcgi + zope and so far it looks stable and doesn't go wild with that accept error. But I stumbled on another problem -- images do not upload correctly at all. Then stared apache at port 80 and zope at 8080. If I upload image through site:8080/manage interface it uploads fine. But if I upload image through site/manage (or my own cgi form), image corrupts on the way! When I export both good and bad images into xml format and diff them, these files are slightly different in binary part. What can corrupt image on its way through apache and fastcgi?
Of couse, it's easy to say use 8080 port to update the site. Unfortunately, I can't run zope at 8080 port, because of previous bug with accept :( I can't find that bug because it happens only once in two or three days, only under normal conditions (i.e. I ran httperf and put a big load on the site... everything worked okay, only to hang several hours later). And since my boss is very unhappy with webserver going down at odd hours when I'm unavailable, I can't really debug this situation :(
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
-- Roman V. Isaev http://www.aroma.ru System Administrator
On Fri, 24 Aug 2001, Roman V. Isaev wrote:
images do not upload correctly at all. Then stared apache at port 80 and zope at 8080. If I upload image through site:8080/manage interface it uploads fine. But if I upload image through site/manage (or my own cgi form), image corrupts on the way!
This is Russian Apache issue. See FAQ, question N5: http://apache.lexa.ru/faq.html#5 http://zope.net.ru/Zope/FAQ/FlexQuestion963314451 Oleg. ---- Oleg Broytmann http://www.zope.org/Members/phd/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
On 08/24, Oleg Broytmann wrote:
images do not upload correctly at all. Then stared apache at port 80 and zope at 8080. If I upload image through site:8080/manage interface it uploads fine. But if I upload image through site/manage (or my own cgi form), image corrupts on the way! This is Russian Apache issue. See FAQ, question N5: http://apache.lexa.ru/faq.html#5 http://zope.net.ru/Zope/FAQ/FlexQuestion963314451
Yep. It did the trick. Thanks. -- Roman V. Isaev http://www.aroma.ru System Administrator
participants (3)
-
Chris McDonough -
Oleg Broytmann -
Roman V. Isaev