looking at the emonpiupdate.log there are 2 separate entries that say to check the settings.php after the update, have you done that? It usually means the settings have been revised and the update script wasn’t able to do the update automatically because the setting.php file wasn’t “stock” there were some user specific settings (other than mysql user/password).
settings.php HAS been user modified
Update required to settings.php...
**ERROR: unable to autoupdate settings.php since user changes are present, manual review required**
this second entry seems to be in html, perhaps @glyn.hudson can say why that might be?
<div style='width:600px; background-color:#eee; padding:20px; font-family:arial;'><h3>settings.php file error</h3><p>settings.php config file has new settings for this version. Copy default.settings.php to settings.php and modify the later.</p><p>To fix, check that the settings are set in <i>settings.php</i> or try re-creating your <i>settings.php</i> file from <i>default.settings.php</i> template</p></div>
Beyond that,the fact your remote emoncms works part of the time, but then fails, might be linked to the local emoncms issue but not necessarily so.
Can you plaese provide some emonhub.log when the fault occurs before you reboot? The current emonhub.log shows us that the remote is being updated and is also shows the local mqtt being published.
so can you do the following 3 checks to confirm all the services are running?
sudo systemctl status feedwriter
sudo systemctl status mqtt_input
sudo systemctl status emonhub
can you check these both now (whilst the remote emoncms is ok) and later when the remote emoncms stops updating, but before you reboot?
On the local emoncms can you please check to see if there are any inputs getting updated by uncollapsing the whole page (rapid double click one inputs “+” button and they all open) and looking for any green updated times.
I’m not sure about the LCD but I suspect it’s unrelated at this point.