Logs
BlueMind keeps log files for each application and usage type.
It is important to provide for enough disk space to store log and archive files.
Space overload stops new information from being saved into log files and can lead to sluggish, and possibly blocked, services.
There are 3 types of log files:
-
system logs, which rely on log administration mechanisms (rsyslog + logrotate)
-
BlueMind's Java services log, which rely on LogBack
Track times
Traces generated by Java in these files are in GMT time.
In France, for example, in the Europe/Paris time zone, the hours are shifted by 1 hour in winter and 2 hours in summer. To search for events that took place at 3pm, search for :
- at 2 p.m. from late October to late March
- at 1 p.m. from late March to late October
-
logs internal to a service, managed via the configuration of this service
The length of retention depends on how these log management mechanisms are configured. Their configuration can be modified to obtain the desired retention time.
Log files
Log files are located in the /var/log file and its subfolders.
| Component | Package Name | Log File | Type | Description |
|---|---|---|---|---|
| BlueMind Core | bm-core | ./bm/ : - core.log - imap.log - js.log - mail-index.log - pop3.log - sendmail.log -slow-call.log ./bm/audit/ : - audit-calendar*.log | LogBack | BlueMind's main service: - database content management, business rules implementation - IMAP logs per user - logs of requests made via the web interface - mail indexing when performing reindexing tasks - POP3 logs per user -Mails sent - requests that took more than 200 ms to execute. Audit: - Traces actions performed within the calendar indicated in the file name: audit-calendar: "calendar name": "user uid".log |
| Postfix | postfix | RedHat: ./maillog Debian/Ubuntu: - ./mail.err - ./mail.info - ./mail.log - ./mail.warn | System | Postfix forwarding service which sends emails to recipients' mailbox or server. |
| bm-webmail | ./bm-webmail : - errors | LogBack | * errors from the webmail service (Round Cube). - tracks all sent messages as well as rules applied to these messages (alias, redirection, etc.). | |
| Synchronisation EAS | bm-eas | ./bm-eas/eas.log | LogBack | Tracks operations carried out to and from mobile devices connected through EAS. In addition, logs for each synchronization file are stored in separate files, which makes the analysis of bugs or erroneous behavior easier. |
| Mapi | bm-mapi | ./bm-mapi/mapi.log ./bm-mapi/requests.log | LogBack | General log of the mapi service Activity log For more detailed information, consult the dedicated page on Troubleshooting with Outlook. |
| Identification | bm-node | ./bm-node/node.log | LogBack | Service that allows the BM-Core server to run system operations on the BlueMind architecture nodes. The log file tracks commands. |
| BlueMind web server | bm-webserver | ./bm-webserver/ : - dav.log - js-errors.log - setup.log - webserver.log | LogBack | Directory containing log files generated by the _webserver_service. - calendar and agenda synchronization. - synchronization via caldav/carddav - JS errors on web applications - BlueMind updates |
| Tika | bm-tika | ./bm-tika/tika.log | LogBack | Extracts metadata and document data for the ES index. Tracks information indexing extraction errors. |
| PHP FPM | bm-php-fpm | ./bm-php-fpm: - bm-php-fpm.log - slow.log | LogBack | PHP interpreters. The slow.log file contains PHP requests longer than 15s. |
| ElasticSearch | bm-elasticsearch | ./bm-elasticsearch | Internal | ElasticSearch service logs.*_slowlog.log files contain slow requests.⚠️ Possible log configuration modifications to this service may be lost after a BlueMind update. |
| Milter | bm-milter | ./bm-milter/milter.log | LogBack | SMTP analysis and modification of emails. |
| YSNP | bm-ysnp | ./bm-ysnp/ysnp.log | LogBack | Service that allows Postfix or Cyrus to obtain or verify data with BlueMind: - SMTP and IMAP authentication - ACLs IMAP ACLs resolution - blocks mail flows when BlueMind is under maintenance or being updated |
| PostgreSQL | bm-postgresql | ./postgresql | Interne+logrotate | PostgreSQL database logs. This component's configuration can be edited using the file /etc/postgresql/9.6/main/postgresql.conf.local |
| NGinx | bm-nginx | ./nginx : - access.log - error.log - webmail.log - mail-proxy.log | Interne+logrotate | The NGinx service allows HTTP and HTTPs access to BlueMind. - access.log contains all HTTP and HTTPs requests made to BlueMind- error.log contains all HTTP and HTTPs error requests or requests whose return code shows an error (4xx, 5xx)- webmail.log contains all HTTP and HTTPs requests made through the webmail in error or whose return code indicates an error (4xx, 5xx)- mail-proxy.log contains the IMAP reverse proxy logs |