Under some circumstances, the logs for specific services (e.g. elasticsearch) placed in ./logs./services where ROXcomposer is installed get written in a file for another service (e.g. labelizer.log).
This occured after deleting all logs in this folder, loading a session in ROXcomposer GUI with a pipeline consisting of a labelizer (TopicMatcher) service and an elasticsearch service and restarting all services to produce logs.
The logs for the elasticsearch services got written into labelizer.log
Under some circumstances, the logs for specific services (e.g. elasticsearch) placed in ./logs./services where ROXcomposer is installed get written in a file for another service (e.g. labelizer.log).
This occured after deleting all logs in this folder, loading a session in ROXcomposer GUI with a pipeline consisting of a labelizer (TopicMatcher) service and an elasticsearch service and restarting all services to produce logs.
The logs for the elasticsearch services got written into labelizer.log
Bugs that might be related: https://github.com/droxit/ROXcomposer-gui/issues/22