Log files
Les fichiers journaux se trouvent dans le dossier /var/log
et ses sous-dossiers
Composant | Package Name | Log File | Type | Description |
---|
BlueMind Core | bm-core | ./bm/core.log | LogBack | Main BlueMind service |
Postfix | postfix | RedHat: ./maillog Debian/Ubuntu: | System | Service de transfert des courriels Postfix qui permet l'acheminement des emails vers la boîte ou le serveur des destinataires. |
Cyrus | bm-cyrus-imapd | RedHat: ./maillog Debian/Ubuntu: | System | Service de gestion des boîtes aux lettres Cyrus IMAP. Permet de: - remettre un email dans la boîte correspondante et d'y accéder en IMAP et/ou POP.
- filtrer les emails lors de leur réception
- gérer le message d'absence
- gérer les redirections
|
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).
|
sendmail and mailSent.log keep - 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 | ./ |
EAS logs are stored in the file: /var/log/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. |
Transfert de courrier | bm-lmtpd | ./bm-lmtpd/lmtpd.log |
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.LogBack | Service chargé de délivrer un email dans la boîte correspondante. Certaines opérations liées à BlueMind sont réalisées à ce niveau - l'analyse des invitations ICS par exemple |
Localisation | bm-locator | ./bm-locator/locator.log | LogBack | Locate user-specific services (mailbox server, etc.) |
Identification | bm-node | ./bm-node/node.log | LogBack | Service permettant au serveur BM-Core d'exécuter des opérations systèmes sur les nœuds de l'architecture BlueMind. Le fichier log trace les commandes exécutées. |
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. |
Authentification | bm-hps | ./bm-hps/hps.log | LogBack | Trace les problèmes et réussites d'authentification et ouverture de session |
Tika | bm-tika | ./bm-tika/tika.log | LogBack | Extraction des méta-données et données des documents permettant de renseigner l'index ES. Trace les erreurs d'extraction des informations à indexer. |
PHP FPM | bm-php-fpm | ./bm-php-fpm: | LogBack | Interpréteurs PHP. Le fichier slow.log contient les requêtes PHP ayant duré plus de 15s. |
ElasticSearch | bm-elasticsearch | ./bm-elasticsearch | Interne | Logs du service ElasticSearch. Les fichiers *_slowlog.log contiennent les requêtes lentes. Les éventuelles modifications de configuration des logs de ce services pourront-être perdues suite à une mise à jour de BlueMind. |
Milter | bm-milter | ./bm-milter/milter.log | LogBack | Analyse et modification des emails au niveau SMTP |
XMPP | bm-xmpp | ./bm-xmpp/xmpp.log | LogBack | Logs de la messagerie instantanée |
YSNP | bm-ysnp | ./bm-ysnp/ysnp.log | LogBack | Service permettant à Postfix ou Cyrus d'obtenir ou valider certaines données auprès de BlueMind : - authentification SMTP et IMAP
- résolution des ACLs IMAP
- blocage du flux mail dans les cas où BlueMind est en maintenance ou mise à jour
|
PostgreSQL | bm-postgresql | ./postgresql | Interne+logrotate | Logs de la base de données PostgreSQL Il est possible de modifier sa configuration via l'utilisation du fichier /etc/postgresql/9.6/main/postgresql.conf.local |
NGinx | bm-nginx | ./nginx: - access.log
- error.log
- webmail.log
| Interne+logrotate | Le service NGinx permet l'accès en HTTP et HTTPs à BlueMind. access.log contient l'ensemble des requête HTTP et HTTPs faites à BlueMinderror.log contient l'ensemble des requêtes HTTP et HTTPs en erreur ou dont le code retour indique une erreur (4xx, 5xx)webmail.log contient l'ensemble des requêtes HTTP et HTTPs faites via le webmail en erreur ou dont le code retour indique une erreur (4xx, 5xx)
|
Configuration LogBack
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