开发者

trac-admin with svn post-commit hook causes segmentation fault

开发者 https://www.devze.com 2023-02-22 05:55 出处:网络
I jus开发者_如何学运维t set up trac 0.12.2 over sqlite on my Fedora box and trac is working fine through the web browser and command line. My issue is with implementing svn hooks where the post-commit

I jus开发者_如何学运维t set up trac 0.12.2 over sqlite on my Fedora box and trac is working fine through the web browser and command line. My issue is with implementing svn hooks where the post-commit hook dies on a segmentation fault when running this command:

/usr/bin/trac-admin /var/trac/myproject changeset added "$1" "$2"

Where $1 is the svn repository path on the local file system and $2 is the revision.

The output of this command is this:

/path/to/svn/hooks/post-commit: line 9: 3874 Segmentation fault /usr/bin/trac-admin /var/trac/myproject changeset added "$1" "$2"

How would I go about debugging this? Does anyone know why this might be happening on a fresh install (I did not upgrade, it's clean)?

I did some basic checking with regards to the user running this command which is apache. I also tried running this command as apache to see if it would fail, but this works just find from the command line:

sudo -u apache /usr/bin/trac-admin /var/trac/ujaweb changeset added /path/to/svn/repo 750

I'm somewhat out of ideas here. Does anyone have any ideas why this might be happening?

Here is some further information in case it's useful:

Linux: Linux hostname.com 2.6.18-028stab069.5 #1 SMP Tue May 18 17:26:16 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux

Apache: 2.2.17 w/ mod_wsgi

Python: 2.6.4

Trac: 0.12.2 (over Apache w/ mod_wsgi)


You could try running trac-admin under strace, and save the output:

/usr/bin/strace -o /var/trac/myproject/log/trace.log /usr/bin/trac-admin /var/trac/myproject changeset added "$1" "$2"

Then, have a look at the generated log in /var/trac/myproject/log/trace.log.

Another option would be to have your system generate a core dump (you may have to enable it in your /etc/limits and/or /etc/security/limits.conf), and open the dump with gdb.


My first try would be to turn off the selinux for a while and test if it still happens. If not - you have to figure out how to configure selinux to allow opening /proc/mount by that process failing with segmentation fault.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号