#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: | |||
| Internal 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)
follow-up: 2 comment:1 by , 17 years ago
| Keywords: | needinfo added |
|---|
comment:2 by , 17 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.
follow-up: 4 comment:3 by , 17 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).
comment:4 by , 17 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
follow-up: 6 comment:5 by , 17 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.
comment:6 by , 17 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
follow-up: 8 comment:7 by , 17 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
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?
comment:8 by , 17 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.
0W ?
Please have a look at TracTroubleshooting#DebuggingSegmentationFaults