Submitted by : koegler at: 2004-08-12T03:22:50+00:00 (13 years ago)
Name :
Category : Severity : Status :
Optional subject :  
Optional comment :

(Zope 2.6.1 , python 2.1.3, openbsd3), ZWiki-0-33-0, allow_dtml==True in Wiki root, Proxy via Apache 1.3 mod_rewrite

I get a 502 proxy error (first visit 'Document contains no data', immediate relod: 'Bad file descriptor') after running SOMEPAGE/setupTracker?pages=1 on an existing issue tracker (contains about 20 issues). After restarting Zope everything works fine again, except /setupTracker?pages=1 (same effect).

The Zope crash doesn't show any exception while running in '-D' mode, it just restarts. This could also be a Zope bug, but I don't know how to narrow down the problem. Any hints?

(new) --Simon Michael, Thu, 12 Aug 2004 08:51:27 -0700 reply

Not even a signal 10 or 11 in the event log ?

Still, this might be the *bsd python insufficient stack size problem. See IssueNo0395? - you can try rebuilding python with a 1Mb stack and see if it fixes this. And/or, one way to debug it further is to putting debug print statements in zwiki (BLATHER()) until you narrow down exactly where python dies. If it's the stack size issue, it's probably in a call to the re library. Another way is to arrange for python/zope to run under gdb, then you can examine the python stack afterwards.

(new) --=?ISO-8859-1?Q?Kai_K=F6gler?=, Fri, 13 Aug 2004 10:20:40 -0700 reply

No sig 10/11, no core. I don't think it's the stack size problem, but I'm currently not able to build a customized python, because I've at the moment no dedicated development machine at hand and don't want to risk interference with existing apps.

If I'm the only one experiencing this, you could set this issue to pending and I report back sometimes, if I can tell you anything useful.

(new) --Simon Michael, Fri, 13 Aug 2004 10:25:49 -0700 reply

Kai K�gler wrote:

> No sig 10/11, no core. I don't think it's the stack size problem,

Why do you say so ?

The only other thing I can think of is RestructuredText can do a system exit (see recent issue) - is the page in RST mode ?

I'd use logging statements to narrow it down. Server dying silently is annoying.

(new) --=?ISO-8859-1?Q?Kai_K=F6gler?=, Fri, 13 Aug 2004 13:46:53 -0700 reply

>>No sig 10/11, no core. I don't think it's the stack size problem, > Why do you say so ?

As I understand this problem results in a stack overflow? So I should get at least an entry in /var/log/messages, at least I get this for stack overflows in other applications. Together with the name of the offending function.

> The only other thing I can think of is RestructuredText can do a system > exit (see recent issue) - is the page in RST mode ?

no, STX+DMTL. I get the same result with other page types.

> I'd use logging statements to narrow it down. Server dying silently is > annoying.

It is (annoying but not evil - this is more or less a "development" zope instance) and I will do so, but be patient....

(new) --Simon Michael, Fri, 13 Aug 2004 13:47:21 -0700 reply

Ok-doke. I will try. :)

some more info now: --koegler, Mon, 30 Aug 2004 05:30:28 -0700 reply

Zope dies in Tracker.py:369:

for p in self.pageObjects():
    n = n + 1
    try:
        BLATHER('indexing page #%d %s in %s'%(n,p.id(),cid))
        p.index_object(log=0)  <---- HERE --- line 369------------
        BLATHER('success')
    except:
        BLATHER('failed to index page #%d %s: %s' \
                % (n,p.id(),formattedTraceback()))

but only, if pages==1. I hope I'll find more later.

it's weird --koegler, Mon, 30 Aug 2004 08:04:05 -0700 reply

I think I'm at the end of my debugging skills. I plastered CatalogAwareness?.index_object() with BLATHER()s, and it runs through the whole method. and dies before BLATHERing? 'success'.

At the moment I rather believe this is a python bug (or whatever)

it works with Python2.3 --koegler, Mon, 30 Aug 2004 08:13:03 -0700 reply

this very same Zope-Installation doesn't run very smoothly on Python2.3 (no surprise), but no problem with /setupTracker?pages=1.

So I'm very sorry for having bothered you, this doesn't seem to be a bug.

alright, assuming an incompatible python/zope --SimonMichael, Thu, 02 Sep 2004 16:55:55 -0700 reply

Status: open => closed