Last update: 9 August 2017
This article provides a general overview of various logfiles created by Mindbreeze and a simple guide to gather those. Additionally logfiles created in combination with Fabasoft Folio as well as the correlation of different component objects created by Mindbreeze in Fabasoft Folio are described.
When submitting Mindbreeze Logs it is always best to include as much information as possible, thus supplying the entire Mindbreeze log directory.
In case the delivery of the complete log directory is not possible (e.g. due to it's size) we can further differentiate issues and the related logfiles.
Please keep in mind that the Mindbreeze service log directories for specific services (index, client, filter, ...) are further devided into subdirectories, each representing the timespan between service restarts.
In most cases supplying e.g. the latest three subdirectories (information up to three service restarts in the past) for a specific service is sufficient.
- log-mesnode.txt
- log-mesmaster.txt
- log-messdkcsandbox--Index_[Ports]
- Index (Query) Service Log
- Client Service Log
- Index (Query) Service Log
- Index (Query) Service Log
- Filter Service Log
- Mindbreeze Server configuration -
The directory Mindbreeze logfiles are created in may be changed in the "Advanced Settings" in the Mindbreeze server configuration. The default directories for Windows and Linux are:
Windows: C:\Users\<mindbreeze service user>\AppData\Local\Temp
Linux: /var/opt/mindbreeze/log
In the Mindbreeze log directory the following directories and single logfiles are located:
File | Description |
log-mesnode.txt | information about the Mindbreeze node process and the state of various subprocesses |
log-mesmaster.txt | information about the Mindbreeze master process itself |
log-messdkcsandbox--Index_[Ports] | information about the communication between Mindbreeze and the Fabasoft Kernel |
log-messdknetsandbox2.txt | information about .net based filter plugins |
Note: Fileextensions of log files (.log, .txt) may vary based on the operating system and the Mindbreeze version in use.
Subdirectory | Description |
Client Service Log | log-mesclientservice-<client-port> |
Index (Query) Service Log | log-mesindex-<index-path> |
Filter Service Log | log-mesfilterservice-<port> |
Crawler Service Log | log-mescrawler-launchedservice-<Category>_<Source Name> |
Log directories for specific C based filter plugins | log-messdkcsandbox2-Default-Filter@[ort]-[PluginName] ... |
Log directories for specific Java based filter plugins | log-messdkjavasandbox2-Filter@[Port] ... |
The Mindbreeze server configuration is saved in the mesconfig.xml file. By default the containing directory is located at:
Windows: C:\Users\<mindbreeze service user>\AppData\Roaming\Mindbreeze\Enterprise Search\Server
Linux: /var/opt/mindbreeze
%userprofile% represents the user profile of the Fabasoft Folio Service user. For scheduled updates, this is usually the AT Service user.
Directory | Description | Default location |
error.log | Created when the Indexing Service Object cannot create or update the index and the log location is not set manually | %userprofile%\AppData\Local\Temp\Fabasoft |
BuildIndex.log | Contains information about the indexing process | Only created when log location set manually |
Log location may be set in the Mindbreeze Indexing Service object in Fabasoft Folio in the property "Directory for Log Files".
Object | Description | Location in Fabasoft Folio |
Mindbreeze Indexing Service | Contains the indexing service configuration | Domain Administration - Domain Objects - Services |
Mindbreeze Filter Service | Contains the filter service configuration | Domain Administration - Domain Objects - Services |
Mindbreeze Configuration Object | Contains the configuration of which files and properties are indexed | Domain Administration - Domain Objects - Current Domain - Components Configuration - Mindbreeze * |
Administration Configuration Object | The tab "Search" contains several properties to optimize performance of the ACL Check | Domain Administration - Domain Objects - Current Domain - Components Configuration - Administration * |
* If the property is empty move to the parent configuration located in the "Domain Type" property.