Forum OpenACS Q&A: Re: naviserver signal 11 core backtrace (revproxy)

Collapse
4: Re: naviserver signal 11 core backtrace (revproxy) (response to 1)
Posted by Gustaf Neumann on 04/19/22 01:06 PM
The second crash look at the first sight strange to me: a client callback tries to allocate an interpreter, ... and the callback is registered as
::revproxy::spool conn829545 conn829544 client {-timeout 0 -sendtimeout 0.0 -receivetimeout 0.5} 0 r

The trailing single "r" flag makes me wonder, the upstream code uses the "rex" flags.

Are you using a modified version of the revproxy module?

Collapse
8: Re: naviserver signal 11 core backtrace (revproxy) (response to 4)
Posted by Marty Israelsen on 04/20/22 01:24 AM
To answer your question: I don't believe we are using a modified version of the revproxy module.
Collapse
9: Re: naviserver signal 11 core backtrace (revproxy) (response to 8)
Posted by Tony Kirkham on 04/20/22 09:21 PM
That is correct. We are using the revproxy ver. 0.15