Edgewall Software
Modify

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#8147 closed defect (worksforme)

Crashing tracd

Reported by: anonymous Owned by:
Priority: normal Milestone:
Component: web frontend Version: 0.11.3
Severity: normal Keywords: needinfo
Cc: Branch:
Release Notes:
API Changes:

Description

Hi!

I'm starting a tracd as standalone web server and using 0W as a front-end. Sometimes tracd is crashing and I can't find in logs any errors.

/usr/local/bin/tracd -b 127.0.0.1 -p 9090 -r -s —pidfile /var/run/tracd.pid —basicauth=*,<path_to_htpasswd>,test /<path_to_trac_project>

Where I can get more information about crashes. I tried all log levels in Trac logging module.

URL where tracd is crashing: /admin/general/perm

Attachments (0)

Change History (8)

comment:1 by Christian Boos, 10 years ago

Keywords: needinfo added

in reply to:  1 comment:2 by anonymous, 10 years ago

Replying to cboos:

0W ?

Please have a look at TracTroubleshooting#DebuggingSegmentationFaults

Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x638d49c0 (LWP 100044)] 0x0000000000435c1c in PyDict_Contains ()

0W httpd - http://0w.ru/httpd/index-en.html

Thanks.

comment:3 by Christian Boos, 10 years ago

Please attach the output from a full backtrace.

Ideally, you should also be able to get the Python backtrace (pystack), using the Misc/gdbint macros (see http://wiki.python.org/moin/DebuggingWithGdb).

in reply to:  3 comment:4 by anonymous, 10 years ago

Replying to cboos:

Please attach the output from a full backtrace.

Ideally, you should also be able to get the Python backtrace (pystack), using the Misc/gdbint macros (see http://wiki.python.org/moin/DebuggingWithGdb).

bt: http://pastebin.com/m36819260 pystack: http://pastebin.com/m2c88066b

comment:5 by Christian Boos, 10 years ago

It might be a stack overflow (see http://mail.python.org/pipermail/python-dev/2007-July/074034.html).

Besides the workaround mentioned in that mail, you could try to upgrade to Genshi:source:trunk, which doesn't use the compiler package anymore, so this might(?) save you some stack depth.

in reply to:  5 comment:6 by anonymous, 10 years ago

Replying to cboos:

It might be a stack overflow (see http://mail.python.org/pipermail/python-dev/2007-July/074034.html).

Besides the workaround mentioned in that mail, you could try to upgrade to Genshi:source:trunk, which doesn't use the compiler package anymore, so this might(?) save you some stack depth.

Thanks. It works

comment:7 by Christian Boos, 10 years ago

Resolution: worksforme
Status: newclosed

Great!

I'd like to know if the switch to Genshi trunk was enough, or did you have to also increase the per-thread stack size?

in reply to:  7 comment:8 by anonymous, 10 years ago

Replying to cboos:

Great!

I'd like to know if the switch to Genshi trunk was enough, or did you have to also increase the per-thread stack size?

I just checkout version of Genshi from svn.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.