Software /
code /
prosody-modules
File
mod_debug_traceback/README.md @ 6195:886c985ece61
mod_lastlog2: Skip initializing internal API (and storage) in prosodyctl
Initializing storage in the global context under prosodyctl causes the
module.command to fail to execute because the storage module has already
been loaded.
Introduced in 7b722955c59b
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sat, 08 Feb 2025 14:12:18 +0100 |
parent | 6003:fe081789f7b5 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Generate tracebacks on-demand --- # Introduction This module writes out a traceback to a file when a chosen signal (by default `SIGUSR1`) is received. It can be useful to diagnose cases where Prosody is unresponsive. # Configuration `debug_traceback_filename` : The name of the file to write the traceback to. Some variables are supported, see [mod_log_ringbuffer] docs for more info. Defaults to `{paths.data}/traceback-{pid}-{count}.log`. `debug_traceback_signal` : The name of the signal to listen for. Defaults to `SIGUSR1`. # Compatibility Prosody 0.12 or later.