Closed aussieW closed 6 years ago
Looking at it, the message bus service doesn't have a single LOG statement in itself so it won't ever log much. The log messages are from loading the config at startup and it isn't registered to update configuration when web configuration change.
The process should probably log some more things like if it's auto-restarted, maybe new connections of that's possible with this loose architecture.
What sort of messages would you expect here?
Not exactly sure what I should expect there, just figured something was wrong. I recently installed mycroft on a VM and saw that there are a lots of message-bus messages being logged in mycroft-bus.log so I figured there was something wrong on the picroft version. Don't want to be missing any helpful info when trying to debug the skills I am developing :).
This issue seems to be resolved in the 17.08 release.
I have noticed on 3 separate picrofts that mycroft-messagebus.log stops capturing messages not long after booting.
Below is the entire mycroft-messagebus.log for a system that has been running for 5 days: