Logs
BlueMind keeps log files for each application and usage type.
info
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
:::info 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 - mail-index.log - slow-call.log ./bm/audit/ : - audit-calendar*.log | LogBack | BlueMind's main service: - database content management, implementation of business rules - email indexing during reindexing tasks - queries that took more than 200 ms to execute. Audit: - Traces actions performed within the calendar specified 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. |
| Cyrus | bm-cyrus-imapd | RedHat: ./maillog Debian/Ubuntu: - ./mail.err - ./mail.info - ./mail.log - ./mail.warn | System | Cyrus IMAP mail service. Allows you to: - move an email to the appropriate folder and access it via IMAP and/or POP. - Filter emails as they arrive - Manage your out-of-office email - Manage email forwarding |
| bm-webmail | ./bm-webmail/ : - errors - sendmailmailSent.log | 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 | Traces operations to and from EAS-connected mobile devices. Please note that logs for each synchronization queue are stored in separate files, to facilitate analysis of bugs or inappropriate behavior. |
| Mail forwarding | bm-lmtpd | ./bm-lmtpd/lmtpd.log | LogBack | Service responsible for delivering an email to the corresponding inbox. Some BlueMind-related operations are performed at this level—such as the analysis of ICS invitations. |
| Location | bm-locator | ./bm-locator/locator.log | LogBack | Locate user-specific services (mailbox server, etc.) |
| Mapi | bm-mapi | ./bm-mapi/mapi.log ./bm-mapi/requests.log | LogBack | General MAPI service log Activity log For more detailed information, see the Troubleshooting Outlook page. |
| Replication | ./bm/replication.log | LogBack | Forwards a copy of the emails to the bm-core service to retrieve the metadata required by bm-eas, bm-mapi, and ElasticSearch For more information, see the page BlueMind 4 Deployment: Important Considerations | |
| Identification | bm-node | ./bm-node/node.log | LogBack | Service enabling the BM-Core server to perform system operations on BlueMind architecture nodes. The log file tracks commands executed. |
| BlueMind web server | bm-webserver | ./bm-webserver/ : - dav.log - js-errors.log - setup.log - webserver.log | LogBack | Directory containing the log files generated by the webserver service. - calendar synchronization. - synchronization via caldav/carddav - JS errors on web applications - BlueMind upgrades |
| Authentication | bm-hps | ./bm-hps/hps.log | LogBack | Tracks successful authentications, authentication issues and sessions started |
| Tika | bm-tika | ./bm-tika/tika.log | LogBack | Extraction of metadata and data from documents to populate the ES index. Traces extraction errors in the information to be indexed. |
| PHP FPM | bm-php-fpm | ./bm-php-fpm: - bm-php-fpm.log - slow.log | LogBack | PHP interpreters. The slow.log file contains PHP requests lasting more than 15 s. |
| ElasticSearch | bm-elasticsearch | ./bm-elasticsearch | Internal | ElasticSearch service logs. The *_slowlog.log files contain slow requests.⚠️ Any log configuration changes made to this service may be lost when BlueMind is upgraded. |
| Milter | bm-milter | ./bm-milter/milter.log | LogBack | SMTP analysis and modification of emails. |
| XMPP | bm-xmpp | ./bm-xmpp/xmpp.log | LogBack | Instant messaging logs. |
| 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 | Database logs PostgreSQL. You can modify its configuration using the /etc/postgresql/9.6/main/postgresql.conf.local file. |
| NGinx | bm-nginx | ./nginx: - access.log - error.log - webmail.log | Interne+logrotate | The NGinx service provides HTTP and HTTPs access to BlueMind. - access.log contains all HTTP requests and HTTPs made to BlueMind.- error.log contains all HTTP requests and HTTPs in error or whose return code indicates an error (4xx, 5xx).- webmail.log contains all HTTP and HTTPS requests made through webmail that failed or returned an error code (4xx, 5xx) |