Thank you David.
On Tue, Jan 13, 2015 at 11:29 AM, David Trowbridge
wrote:
> Nilesh,
>
> I can't comment about whether it will cause serious problems beyond the
> warning, because I don't know. However, it looks scary and I wouldn't be
> surprised if you have issues or corruption.
>
> As far as
Nilesh,
I can't comment about whether it will cause serious problems beyond the
warning, because I don't know. However, it looks scary and I wouldn't be
surprised if you have issues or corruption.
As far as migrating to mod_wsgi, I'd suggest doing a deployment of Review
Board on a new server and
Thanks David,
I have read the document about the deprecation of mod_python. Could you
please help me know if this error create any issue in future, considering
we stick to mod_python and RB release version 1.7.5 ( which still support
mod_python) and the error message we see would cause incorrect b
It looks like there's a problem with your mod_python.
mod_python is deprecated and unmaintained. The recommended way to deploy
Python applications with Apache (including Review Board) is mod_wsgi.
-David
On Mon Jan 12 2015 at 7:36:32 AM Nilesh Jaiswal
wrote:
> Dear All,
>
> I am using RB versi
Dear All,
I am using RB version 1.7.5, I see exception in the error.log.
I am wanted to know if this is harmful for the application?
How to fix it?
please advise and help
except apache.PROG_TRACEBACK, traceblock:
Fatal Python error: PyEval_AcquireThread: NULL new thread state
[Mon Jan 12 02:4
