Luckily the emonhub.log is still found in the same place on all linux based installs at /var/log/emonhub/emonhub.log.
Although I’m not entirely sure the “Active: active (exited)” is indicative of a failed or stopped service, we see this quite frequently (eg emonPi hangs and stops logging - #38 by borpin). I’m tempted to say it’s more likely to be linked to the fact the emonhub and feedwriter services are systemV init scripts being run in “compatibility mode” by systemd, but I cannot be sure. Both Mosquitto and mqtt_input services are systemd units.
Looking at the “server information” that shows the feedwriter as running and I see no “errors” in the short log attached to the emonhub service status, only some valid start up lines and the last entry is a keyboard interrupt. @Daniel_Edvall have you manually stopped the emonhub service to try minicom?
What I do find interesting is that both the emonhub and mqtt_input services are only running 6mins were as the other 2 are running 15hours, @Daniel_Edvall did something significant ocurr 6mins before checking the statuses? eg running the emonpi update again.
It’s always been an issue since MQTT was first implemented, the apparent changes in frequency have been due to other issues coming and going so more or less logs are seen, and at some point the code was changed so the errors weren’t logged but the problem has always been there.