There are 3 types of log files:
Storage time depends on each log administration mechanism's settings. These settings can be changed to the desired storage time.
Log files
Les fichiers journaux se trouvent dans le dossier /var/log et ses sous-dossiers
| Component | Package Name | Log File | Type | Description |
|---|
| BlueMind Core | bm-core | ./bm/core.log | LogBack | Main BlueMind service: - manages database contents
- implements job rules
- ...
|
| Postfix | postfix | RedHat: ./maillog Debian/Ubuntu: | System | Postfix forwarding service which sends emails to recipients' mailbox or server. |
| Cyrus | bm-cyrus-imapd | RedHat: ./maillog Debian/Ubuntu: | System | Cyrus IMAP mail service. Permet de: - place an email in the corresponding mailbox and access it through IMAP and/or POP.
- filter emails on reception
- manage away message
- manage redirects
|
| Webmail | bm-webmail | ./bm-webmail/ :
- errors
- sendmail
mailSent.log
| LogBack | |
BlueMind Core component log
Logs are kept in the file: /var/log/bm/core.log.
Mail services log
Three log files are kept in the /var/log/bm-webmail directory:
errors reports errors found in - the webmail service (Round Cube).
|
- keeps track of all sent messages as well as rules applied to these messages (alias, redirection, etc.).
|
BlueMind synchronization component (EAS) log
| Proxy IMAP | bm-ips | ./bm-ips/ips.log | LogBack | Tracks IMAP operations (moved files, deletions, etc.), including when they are carried out from BlueMind webmail |
| 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. |
BlueMind message queue component log
BM-MQ logs are kept in the file "/var/log/bm-mq/hornetq.log", and can be used to check message queue processes such as push to mobile devices.
BlueMind mailboxes message tracking component log
These logs are stored in the /var/log/bm-lmtpd/lmtpd.log file and enable you to check messages paths to BlueMind mailboxes.
BlueMind locator component log
These logs are kept in the /var/log/bm-locator/locator.log file and can be used to locate user-specific services (mailbox server, etc.).
BlueMind server identification component log
/var/log/bm-node/node.log can be used to analyse requests to identify services on BlueMind servers as well as actions initiated by the BM-Core server and executed on the BlueMind architecture nodes.
BlueMind Tomcat service log
/var/log/bm-tomcat/ lists the log files generated by the Tomcat server. It also tracks indexing content rules.| Mail forwarding | bm-lmtpd | ./bm-lmtpd/lmtpd.log | LogBack | Service that delivers emails to the corresponding mailbox. Some BlueMind-related operations are carried out here - ICS invitation analysis, for example. |
| Localization | bm-locator | ./bm-locator/locator.log | LogBack | Locate user-specific services (mailbox server, etc.) |
| 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.
Includes calendar synchronization tracking. |
| Authentication | bm-hps | ./bm-hps/hps.log | LogBack | Tracks successful authentications, authentication issues and sessions started |
| 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: | LogBack | PHP interpreters. The slow.log file contains PHP requests longer than 15s. |
| ElasticSearch | bm-elasticsearch | ./bm-elasticsearch | Interne | 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. |
| 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 | 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
| Interne+logrotate | The NGinx services allows HTTP and HTTPs access to BlueMind. access.log contains all HTTP and HTTPs requests made to BlueMinderror.log contains all HTTP and HTTPs error requests or request whose return code shows an error (4xx, 5xx)webmail.log contains all HTTP and HTTPs requests made through webmail or error requests or requests whose return code shows an error (4xx, 5xx)
|
LogBack configuration
By default, configuration files are located in the directory /usr/share/bm-conf/logs/:
- bm-core-audit.log.xml
- bm-core.log.xml
- bm-eas.log.xml
- bm-hps.log.xml
- bm-ips.log.xml
- bm-lmtpd.log.xml
- bm-locator.log.xml
- bm-milter.log.xml
- bm-node.log.xml
- bm-pimp.log.xml
- bm-tika.log.xml
- bm-webserver.log.xml
- bm-xmpp.log.xml
- bm-ysnp.log.xml
To edit them, copy the file you want to edit into /etc/bm/local and edit the copy.
Configuration example:
| Bloc de code |
|---|
<appender name="R" class="ch.qos.logback.core.rolling.RollingFileAppender">
<!--See also http://logback.qos.ch/manual/appenders.html#RollingFileAppender -->
<File>/var/log/bm/core.log</File>
<encoder>
<pattern>%d [%thread] %c{1} %p - %m\n</pattern>
</encoder>
<rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<maxIndex>20</maxIndex>
<FileNamePattern>/var/log/bm/core.log.%i.gz</FileNamePattern>
</rollingPolicy>
<triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<MaxFileSize>60000KB</MaxFileSize>
</triggeringPolicy>
</appender |
In the example above, the main log file core.log can keep 20 log files of 60Mb each at the most.
For more information about configuration, please refer to the site Log4j or the following documentation: https://logback.qos.ch/manual/appenders.html#RollingFileAppender
