#1236 closed defect (invalid)
Getting Can't Create/get interpreter from time to time when using XmlRpcPlugin
| Reported by: | mailtolanger-at googlemail-dot-com | Owned by: | Alec Thomas |
|---|---|---|---|
| Priority: | normal | Component: | XmlRpcPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.10 |
Description
Using Suse 9.3, Python 2.4, Apache 2.0.53, Trac 0.10.3, XmlRpcPlugin 0.1 (used download zipped sources). I also have the WebAdminPlugin installed.
Webfrontend works fine and haven't seen any errors but when I use Mylar 2.0M1 through the XmlRpcPlugin I get the following error in the apache logs: "python_handler: Can't get/create interpreter." The changes I made to the ticket get submitted and the error occurs on the following synchronisation. When I start the synchronisation some time later again all works fine.
Attachments (0)
Change History (3)
comment:1 Changed 17 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 Changed 17 years ago by
Is there a mailing list I can get this worked out on? I don't see how apache can be the problem if everything works ok for trac. What is XmlRpcPlugin doing which the webfront does not do? This only happens through the XmlRpcPlugin interface.
comment:3 Changed 17 years ago by
The only difference is that it handles and returns XML rather than HTML. Apart from that, it uses exactly the same mechanism as all other Trac plugins.
If you Google for this error, you'll see lots of people with the same problem. Presumably there is an answer.
Is this even an XmlRpcPlugin problem? This sounds like an Apache configuration problem or a bug in Apache. If you think it's not, feel free to reopen the ticket with more evidence ;)