Debugging Daemons

To activate debug mode, add debug: true in the daemon configuration file). The output will be available in the daemon’s log file.

It is also possible to run the Wazo daemon, in command line. This will allow to run in foreground and debug mode. To see how to use it, type:

xivo-{name} -h

Note that it’s usually a good idea to stop monit before running a daemon in foreground:

systemctl stop monit.service


twistd -no -u xivo-confgend -g xivo-confgend --python=/usr/bin/xivo-confgend --logger xivo_confgen.bin.daemon.twistd_logs

No debug mode in confgend.


twistd -no -u xivo-provd -g xivo-provd -r epoll --logger provd.main.twistd_logs xivo-provd -s -v
  • -s for logging to stderr
  • -v for verbose


sudo -u consul /usr/bin/consul agent -config-dir /etc/consul/xivo -pid-file /var/run/consul/

Consul logs its output to /var/log/syslog to get the output of consul only use consul monitor:

consul monitor -ca-file=/usr/share/xivo-certs/server.crt -http-addr=https://localhost:8500
2015/08/03 09:48:25 [INFO] consul: cluster leadership acquired
2015/08/03 09:48:25 [INFO] consul: New leader elected: this-xivo
2015/08/03 09:48:26 [INFO] raft: Disabling EnableSingleNode (bootstrap)
2015/08/03 11:04:08 [INFO] agent.rpc: Accepted client:


The ca-file can be different when using custom HTTPS certificates


echo "{loglevel, 5}." >> /etc/mongooseim/wazo.cfg
systemctl restart mongooseim

Log file: /var/log/mongooseim/ejabberd.log. This file contains almost nothing before the loglevel is set.

You should not leave the loglevel enabled in production for too long. To disable it:

sed -i '/loglevel, 5/d' /etc/mongooseim/wazo.cfg
systemctl restart mongooseim