GJ Software Products Posted February 4, 2023 Posted February 4, 2023 (edited) A bit ago I upgraded to 5.5.5 and after the eisy restarted I had to stop & start the ELK NS to get the nodes to populate with valid values. Although this time around when I forced a reboot it came to life on it's own. The log (attached) after the upgrade shows "ERROR interface:send: MQTT Send timeout" but after a stop & start that fixed it. And then it held through a reboot. I think all is well, just a similar /strange quirk like last time related to the startup of the MQTT service? But then the full reboot seemed to fix it too... PG3x 3.1.22, ELK 3.5.8 AfterUpgrade.zip Edited February 4, 2023 by GJ Software Products
Jimbo.Automates Posted February 4, 2023 Posted February 4, 2023 Thanks, this is something that @bpwwer will need to review.Sent from my Pixel 6 Pro using Tapatalk
bpwwer Posted February 4, 2023 Posted February 4, 2023 Very likely the upgrade wasn't finished.' With the eisy, there's no good way to know when it has finished and PG3x may start before some of the other services that it requires. In this case, it looks like the MQTT service wasn't initialized when ELK first tried to start. The latest update seems to be causing quite a bit of trouble. 1
Recommended Posts