Service Logs
Service logs provide a complete record of each FindFace Multi component activity. Consulting logs is one of the first things you should do to identify a cause for any system problem.
In this section:
Configure Logging
The FindFace Multi services log a large amount of data, which can eventually lead to disc overload. To prevent this from happening, we advise you to disable rsyslog due to its suboptimal log rotation scheme and use the appropriately configured systemd-journal service instead.
Do the following:
Check whether the
/var/log/journaldirectory already exists. If not, create it by executing the following command:sudo mkdir /var/log/journal sudo chmod 2755 /var/log/journal
Open the
/etc/systemd/journald.confconfiguration file. Enable savingjournaldlogs to your hard drive by uncommenting theStorageparameter and changing its value topersistent. Disable filtering insystemd-journalas well:sudo vi /etc/systemd/journald.conf [Journal] ... Storage=persistent ... RateLimitInterval=0 RateLimitBurst=0 ...
If necessary, uncomment and edit the
SystemMaxUseparameter. This parameter determines the maximum volume of log files on your hard drive. Specify its value in bytes or use K, M, G, T, P, E as units for the specified size (equal to \(1024\), \(1024^2\), … bytes).... SystemMaxUse=3G
Restart the
journaldservice.sudo systemctl restart systemd-journald.service
Stop and disable the
syslogservice.sudo systemctl stop syslog.socket rsyslog.service sudo systemctl disable syslog.socket rsyslog.service
If necessary, delete the existing log files created through
syslog, and the kernel logs.sudo rm /var/log/syslog* sudo rm /var/log/kern.log*
Consult Service Logs
Use the journalctl -u <component> command to consult a component log, for example as follows:
journalctl -u findface-extraction-api
See also