Skip to end of metadata
Go to start of metadata


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.



On this page:


Applications and Components

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

    Java-generated tracks in these files are set to GMT.

    As a result, in France, which is in the Europe/Paris time zone, times are +1h in the winter and +2h in the summer. To find items that took place at 15:00, you need to look for:

    • 14:00 from late October to late March
    • 13:00 from late March to late October
  • internal service logs, managed by each service's configuration.

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

ComponentPackage NameLog FileTypeDescription
BlueMind Corebm-core./bm/core.logLogBack

Main BlueMind service:

  • manages database contents
  • implements job rules
  • ...

RedHat: ./maillog



Postfix forwarding service which sends emails to recipients' mailbox or server.


RedHat: ./maillog



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
Webmailbm-webmail./bm-webmail/ :
  • errors
  • sendmail


  • errors from the webmail service (Round Cube).
  • keeps track of all sent messages as well as rules applied to these messages (alias, redirection, etc.).
Proxy IMAPbm-ips./bm-ips/ips.logLogBackTracks IMAP operations (moved files, deletions, etc.), including when they are carried out from BlueMind webmail
Synchronisation EASbm-eas./bm-eas/eas.logLogBackTracks 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.
Mail forwardingbm-lmtpd./bm-lmtpd/lmtpd.logLogBack

Service that delivers emails to the corresponding mailbox.

Some BlueMind-related operations are carried out here - ICS invitation analysis, for example.


LogBackLocate user-specific services (mailbox server, etc.)

Service that allows the BM-Core server to run system operations on the BlueMind architecture nodes.

The log file tracks commands.

BlueMind web serverbm-webserver./bm-webserver/ :
  • dav.log
  • js-errors.log
  • setup.log
  • webserver.log
LogBackDirectory containing log files generated by the webserver service.
Includes calendar synchronization tracking.
Authenticationbm-hps./bm-hps/hps.logLogBackTracks successful authentications, authentication issues and sessions started

Extracts metadata and document data for the ES index.
Tracks information indexing extraction errors.

PHP FPMbm-php-fpm


  • bm-php-fpm.log
  • slow.log

PHP interpreters.

The slow.log file contains PHP requests longer than 15s.


ElasticSearch service logs.

*_slowlog.log files contain slow requests.

Possible log configuration modifications to this service may be lost after a BlueMind update.

Milterbm-milter./bm-milter/milter.logLogBackSMTP analysis and modification of emails.

Instant messaging logs.


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 database logs.

This component's configuration can be edited using the file /etc/postgresql/9.6/main/postgresql.conf.local



  • access.log
  • error.log
  • webmail.log

The NGinx services 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 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:

<appender name="R" class="ch.qos.logback.core.rolling.RollingFileAppender">
  <!--See also -->
    <pattern>%d [%thread] %c{1} %p - %m\n</pattern>
  <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
  <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">

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:





  • No labels