Log Files
Every XiVO service has its own log file, placed in /var/log.
asterisk
The Asterisk log files are managed by logrotate.
It’s configuration files /etc/logrotate.d/asterisk and /etc/asterisk/logger.conf
The message log level is enabled by default in logger.conf and contains notices, warnings
and errors. The full log entry is commented in logger.conf and should only be enabled when
verbose debugging is required. Using this option in production would produce VERY large log files.
Files location:
/var/log/asterisk/*Number of archived files: 15
Rotation frequence: Daily
postgresql
File location:
/var/log/postgresql/postgresql-17-main.logRotate configuration:
/etc/logrotate.d/xivo-manage-dbNumber of archived files: 15
Rotation frequence: Daily
xivo-agentd
File location:
/var/log/xivo-agentd.logRotate configuration:
/etc/logrotate.d/xivo-agentdNumber of archived files: 15
Rotation frequence: Daily
xivo-agid
File location:
/var/log/xivo-agid.logRotate configuration:
/etc/logrotate.d/xivo-agidNumber of archived files: 15
Rotation frequence: Daily
xivo-amid
File location:
/var/log/xivo-amid.logRotate configuration:
/etc/logrotate.d/xivo-amidNumber of archived files: 15
Rotation frequence: Daily
xivo-auth
File location:
/var/log/xivo-auth.logRotate configuration:
/etc/logrotate.d/xivo-authNumber of archived files: 15
Rotation frequence: Daily
xivo-call-logd
File location:
/var/log/xivo-call-logd.logRotate configuration:
/etc/logrotate.d/xivo-call-logdNumber of archived files: 15
Rotation frequence: Daily
xivo-confd
File location:
/var/log/xivo-confd.logRotate configuration:
/etc/logrotate.d/xivo-confdNumber of archived files: 15
Rotation frequence: Daily
xivo-confgend
The xivo-confgend daemon output is sent to the file specified with the --logfile parameter when
launched with twistd.
The file location can be changed by customizing the xivo-confgend.service unit file.
File location:
/var/log/xivo-confgend.logRotate configuration:
/etc/logrotate.d/xivo-confgendNumber of archived files: 15
Rotation frequence: Daily
xivo-ctid
File location:
/var/log/xivo-ctid.logRotate configuration:
/etc/logrotate.d/xivo-ctidNumber of archived log files: 15
Rotation frequence: Daily
xivo-dird
File location:
/var/log/xivo-dird.logRotate configuration:
/etc/logrotate.d/xivo-dirdNumber of archived files: 15
Rotation frequence: Daily
xivo-dird-phoned
File location:
/var/log/xivo-dird-phoned.logRotate configuration:
/etc/logrotate.d/xivo-dird-phonedNumber of archived files: 15
Rotation frequence: Daily
xivo-dxtora
File location:
/var/log/xivo-dxtora.logRotate configuration:
/etc/logrotate.d/xivo-dxtoraNumber of archived files: 15
Rotation frequence: Daily
xivo-provd
File location:
/var/log/xivo-provd.logRotate configuration:
/etc/logrotate.d/xivo-provdNumber of archived files: 15
Rotation frequence: Daily
xivo-purge-db
File location:
/var/log/xivo-purge-db.logRotate configuration:
/etc/logrotate.d/xivo-purge-dbNumber of archived files: 15
Rotation frequence: Daily
xivo-stat
File location:
/var/log/xivo-stat.logRotate configuration:
/etc/logrotate.d/xivo-statNumber of archived files: 15
Rotation frequence: Daily
xivo-sysconfd
File location:
/var/log/xivo-sysconfd.logRotate configuration:
/etc/logrotate.d/xivo-sysconfdNumber of archived files: 15
Rotation frequence: Daily
xivo-upgrade
File location:
/var/log/xivo-upgrade.logRotate configuration:
/etc/logrotate.d/xivo-upgradeNumber of archived files: 15
Rotation frequence: Daily
xivo-web-interface
File location:
/var/log/xivo-web-interface/*.logRotate configuration:
/etc/logrotate.d/xivo-web-interfaceNumber of archived files: 21
Rotation frequence: Daily
Collecting logs
The xivo-collect-logs script gathers the logs of a given day into a single directory and tarball,
ready to be attached to a support ticket. It is available on every node type (XiVO PBX, XiVO CC,
media server) and must be run as root:
xivo-collect-logs <YYYYMMDD> [ticket number]
YYYYMMDDis the day to collect logs for (e.g.20260610).ticket numberis optional. When given, the logs go to/var/local/issue<ticket number>; otherwise a temporary directory is used and its path is printed at the end.
The script detects the role of the node and collects the relevant logs (system logs plus the
services running for that role). On a XiVO PBX or UC addon node, the media servers and the XiVO CC
are discovered from the local database and their logs are collected over SSH (as root); each
node’s logs land under its own <node>/ sub-directory, all packed into one tarball.
Note
Collecting the media servers logs over SSH relies on the /root/.ssh/rsync_xds key
being present on the XiVO PBX node. Any node whose logs could not be collected is listed at the
end of the run so it can be retrieved manually.