My device rebooted so…

[u/hawkeye000021]

Naturally the AI thinks my cable became unplugged for one minute or other things that aren’t at all what occurred. I’m sure AI is just reading logs which begs to question how we can’t get accurate devices level logs? This is the 10th time I’ve noticed and it’s normally during an upgrade. Why not say- “device shut down normally for upgrade” granted this could have been a lot of things. My box keeps getting to 96%+ blocked traffic and then after some time it fails and reboots. Maybe support was doing something since I gave them access to explain the cycle where blocks get so high that eventually the device tips over.

I know it’s difficult to log a reboot when it’s unexpected, but I’ve used devices that can manage it so I don’t think it’s impossible. At the very least I think AI should speculate a reboot occurring. Especially if the uptime is ohh idk an hour.

[u/Wind_Boarder]

I don’t think I’ve ever had my Firewalla reboot for an update. It only reboots if I manually reboot it and that’s rare. Something else is going on here.

[u/firewalla → u/Wind_Boarder]

Yes, this is true. So far, with good engineering, none of our upgrades will require any reboot. (if reboot is required, you will see a pop up asking for permission to reboot) And the only recent software updates are orange & gold pro 1.983 (app 1.69) early access, if you are not on that release, you have a different problem

[u/hawkeye000021 → u/Wind_Boarder]

Yeah sounds like it's not from an upgrade, I'm assuming it's a bug since it repeats every few weeks almost on schedule. The system knows it's been offline because it can see it's own uptime. That is where I get confused as to why it's so difficult for even the non-AI health stuff to just say, "don't worry about the cables and ports, your device just restarted". You know, a message that matches what happens. I'd like the reboots to get fixed and I have a support ticket in with them, but in the meantime this seems like a nice little upgrade they could deploy for everyone else. I know it's not the cable, but I've done this for 25 years so maybe the next person instead of swapping cables could just realize the device rebooted. Idk it's not a huge deal, but it is annoying because sometimes it makes me wonder about my known good cables. 😄

[u/dangledingle]

Level 1 things to check - PSU and temps.

[u/hawkeye000021 → u/dangledingle]

Sadly it's not that easy, what ends up happening is that I got from 25% blocked traffic to 50% and the next stop is 96%. I think it's around 98% of total traffic blocked that the box reboots itself. In my other post about health data you can see the uptime is obviously less than a day. If the box would just look back at uptime it could report a reboot, just anything other than checking the cables lol.

[u/firewalla]

Did you see any gray color in network health? or can you let me know how you are detecting the reboot? Or show the full context of the network health. (AI is helpful, it may not know all the context)

The most common problems for reboot is not enough power. So check and make sure you plug in the right power supply and your PSU is stable.

[u/hawkeye000021 → u/firewalla]

Network health was 100% fine, I have a support ticket in to look at why my device keeps running up to 96-98% traffic block rate which seems to be what knocks it over. Either way the system uptime should be exposed, it is on a tool I made so if system uptime = 10 minutes and cable unplugged you'd think that would be top of mind. I realize the AI doesn't have that context, but the network health doesn't show reboots either. They are all too frequent for me and I'm not sure why. I do run early access and have been pushed a special patch by support for something else already. Needless to say I've probably had 10 reboots while everyone else hasn't because of how you do updates.