At some point in time the daemon eats up 100% of CPU without any hint why this is so. It resembles pretty much the same behaviour as e.g. https://github.com/hbz/events/issues/5 and thus the solution should be the same: automatically restarting of the service.
At some point in time the daemon eats up 100% of CPU without any hint why this is so. It resembles pretty much the same behaviour as e.g. https://github.com/hbz/events/issues/5 and thus the solution should be the same: automatically restarting of the service.