[Cubicweb] How to debug cubicweb withoutdebug mode?

Dimitri Papadopoulos Orfanos dimitri.papadopoulos at cea.fr
Mon Apr 11 16:23:06 CEST 2016

Hi Nicolas,

Sentry looks nice, but we don't have the financial resources for it -
and the IT security guys will probably not like it either.

I believe messages are being emitted by the docutils crash (probably to
stderr) but are somehow eaten before we get a chance to see them
(probably the effect of daemonize()). I would like such messages output
to the log or some other file. Is that possible at all?


Le 09/04/2016 01:21, Nicolas Chauvat a écrit :
> Hi Dimitri,
> On Thu, Apr 07, 2016 at 12:30:04PM +0200, Dimitri Papadopoulos Orfanos wrote:
>> Dear all,
>> CubiWeb's debug mode (cubicweb-ctl start -D) is not very useful because
>> [...]
>> I need to see as much error message as possible, without using CuicWeb's
>> debug mode. How do I get as much error output as possible.? For example
>> I need to see the error messages related to the docutils crash.
>> Patching CubicWeb would be acceptable while debugging.
> We have been using https://getsentry.com/ and integrated it into
> CubicWeb with https://www.cubicweb.org/project/cubicweb-sentry
> Basically, you get to see all the errors thru a web interface instead
> of having to read the logs. And you can also put there the errors/logs
> from your database, web server and cache if you want.

Dimitri Papadopoulos
DRF, I2BM, NeuroSpin
F-91191 Gif-sur-Yvette cedex, France

More information about the Cubicweb mailing list