I mean just create the device, boot it up where it’s detected by the console and starts updating something there (it just says “updating” as far I can see) and then when it’s done I restart without having made any changes like password or dashboards, and it does reboot promptly but at this point I no longer get sensor data. The log says it’s timing out.
If I re-image and have the device discovered, and let it update however it’s doing that, and never restart it will continue to work properly. Does that help? The image I don’t think is the problem- I think it’s to do with whatever updates occur once a new device is brought online. I have repeated this a few times and am getting a consistent problem, before I set about making any changes.
I just provisioned a Pi 3B+ with balenaSense and it seems to be working ok. I want to see if I can reproduce what you are describing. When you say “restart” are you referring to rebooting the device, power cycling, or selecting “restart services?” Once the initial updating is complete and the software is running, there should not be any further updates (unless you are “pushing” the software again.)
I just ran through it all again- let me tell you my steps in case I’m missing something.
1.) New image written to SD card. All prior instances are deleted in console.
2.) Boot fresh image and it joins the console and gets as expected- see “joins.png”
3.) Updates - see “updates-detail.png”
4.) Updates finish and everything is working- see “working.png”
5.) I restart services (or I could reboot, it’s the same outcome) - see “RestartService.png”
6.) Everything seems to restart cleanly but no new data will ever populate - see “problem.png”
7.) Post system restart, I get “No Data” - see “No Data.png”
Curiously, there is now a new/additional dashboard that has some subsequent data, but also has stopped refreshing. The first dash was called “sensor” and the new dash is called “MQTT Consumer”. On the new dashboard, I get the same original problem where no new data populates. - see “NewDash-Same.png”
This is as far as I get. I can’t see what’s changing or causing drama. I thought it might be a sensor thing, a wonky memory card, bad image version, and have tried with alternates for all of these to no avail.
I see this message in the logs: 2024-11-16T00:40:12Z E! [inputs.http] Error in plugin: [url=http://sensor:7575]: Get “http://sensor:7575”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Does any of this help? Am I doing something wrong? Thanks!
Cheers,
Scott
UPDATE: I can only post one image per post, as I’m a new user. I can ZIP them and send them if you want or need to see what I’m trying to refer to. Sheesh.
With more poking about, I’ve narrowed the root cause a bit. If I wait until everything is rebooted and running with the issue described above, I can restart the sensor service only and it starts functioning again.
Is there something important about the timing or sequence of these services starting?
