[Fab-user] Missing Stacktrace on error

[Thomas Güttler]

Hi,

sometimes it is hard to debug where a fabric task has stopped, since you
only see an error message.

Please forgive me, if I am blind, but I could not find a way to enable tracebacks
on errors.

Is there a way to see stacktraces if a task has failed?

Thank,
Thomas

[Jeff Forcier]

Yup, just turn on 'debug' output in whichever way is most convenient
for you: http://docs.fabfile.org/en/1.10/usage/output_controls.html#hiding-and-or-showing-output-levels

E.g. `fab --show=debug <tasks>`

Post by Thomas Güttler
Hi,
sometimes it is hard to debug where a fabric task has stopped, since you
only see an error message.
Please forgive me, if I am blind, but I could not find a way to enable tracebacks
on errors.
Is there a way to see stacktraces if a task has failed?
Thank,
Thomas
--
Thomas Güttler
http://thomas-guettler.de/
_______________________________________________
Fab-user mailing list
https://lists.nongnu.org/mailman/listinfo/fab-user

[Thomas Güttler]

Post by Jeff Forcier
Yup, just turn on 'debug' output in whichever way is most convenient
for you: http://docs.fabfile.org/en/1.10/usage/output_controls.html#hiding-and-or-showing-output-levels
E.g. `fab --show=debug <tasks>`

On our servers several hundred tasks get executed on one day.

Sometimes (less then 99.9%) there is an unusual error and the scripts aborts.

The current error message does not help us: We want a stacktrace.

Running the task again does to reproduce the error. It works.

How to debug something like this?

If we turn on --show=debug on our production servers, the logs get unreadable since
there is way too much output.

Can you understand what makes me unhappy?

It would be very nice to see stacktraces without running fabric in debug mode.

Thomas Güttler

[Jeff Forcier]

For the record, all you had to say was "Yes, debug output shows
tracebacks, but is there a way to enable the tracebacks without other
debug level output? We have intermittent errors and separating these
concerns would be very useful".

To which the answer is, unfortunately not at present, though we
acknowledge the validity of the feature request.

I could not find open tickets about this so I just made one,
https://github.com/fabric/fabric/issues/1200

Best,
Jeff

Post by Thomas Güttler

Post by Jeff Forcier
Yup, just turn on 'debug' output in whichever way is most convenient
http://docs.fabfile.org/en/1.10/usage/output_controls.html#hiding-and-or-showing-output-levels
E.g. `fab --show=debug <tasks>`

On our servers several hundred tasks get executed on one day.
Sometimes (less then 99.9%) there is an unusual error and the scripts aborts.
The current error message does not help us: We want a stacktrace.
Running the task again does to reproduce the error. It works.
How to debug something like this?
If we turn on --show=debug on our production servers, the logs get unreadable since
there is way too much output.
Can you understand what makes me unhappy?
It would be very nice to see stacktraces without running fabric in debug mode.
Thomas Güttler
--
Thomas Güttler
http://thomas-guettler.de/
_______________________________________________
Fab-user mailing list
https://lists.nongnu.org/mailman/listinfo/fab-user