I will preface this with that I am a linux guy and usually I am pretty comfortable on the cli front with the OS but had something happen yesterday to one of my newer units that has me a little stumped and was hoping that I could get some others to see if they had any suggestions. I have a rref-pi unit running one of the @Michael Lane hats with a rpi zero w2. Been up and running for about 4 months and yesterday I went to connect to it from my phone and it wouldn't respond from the web page which was odd. I then I grab my PC and couldn't ping the address. Everything appeared to be working, at least all my outlets and lights etc were still in operation but it wasn't responding, first thing I tried was to pull power and reboot, which I hate but with no monitor its hard to see what is going on. I re-applied power and waited and nothing came back online, so thinking the worse that my SD card was corrupted etc, I disconnected everything and pulled the SD card out and took it to the bench where I could insert it into another rpi and boot with a monitor and to my surprise it booted right up, now that was odd. I did not see any issues, so I put it back in and powered up and it to booted back up, what the heck is going on.
So once I had everything connected (which I did find one of my 12v power inputs to be loose, maybe this was an issue?) and appeared to be stable I started poking around in the log to see maybe I could see what was going on. I have logs back through June (which I thought I should be rolling them monthly, need to look into that) but what I came across is something I have never seen before. A few times in June and july the box appears to be rebooting, when looking at the logs I do not see anything but a Boot statement like this:
-- Boot 0a45a896c2c345e5b53e90e8f5ade4d8 --
Nothing before that indicates any issues just reef-pi doing its thing and then more messages like its booting. But I see a lot of these messages, sometimes over and over. But the messages actually do not look like the box is rebooting, at least they do not show up in the reboot log:
bishop@atollpi:~ $ last reboot
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 still running
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
Not sure this is recording what I think its recording but, yesterday it was rebooting or appearing to reboot over and over and over. I've attached the journalctl output for all boot statements with the previous line for context but right now I have no idea what is causing this or how to address since I am not sure its really rebooting but something is going on. I am running an up to date Bullseye installation, since booting it back up yesterday and correcting the loose wire no reboot messages but now I am pretty paranoid, lol. I've attached 2 files one just pulls out all the boot statements with a line before and the other was a segment from yesterday when it was constantly rebooting, you can see it appears to be rebooting and then another boot statement but doesnt appear to be rebooting, I dunno this is pretty odd stuff but thought I would post to see if anyone has any ideas....
Thanks
So once I had everything connected (which I did find one of my 12v power inputs to be loose, maybe this was an issue?) and appeared to be stable I started poking around in the log to see maybe I could see what was going on. I have logs back through June (which I thought I should be rolling them monthly, need to look into that) but what I came across is something I have never seen before. A few times in June and july the box appears to be rebooting, when looking at the logs I do not see anything but a Boot statement like this:
-- Boot 0a45a896c2c345e5b53e90e8f5ade4d8 --
Nothing before that indicates any issues just reef-pi doing its thing and then more messages like its booting. But I see a lot of these messages, sometimes over and over. But the messages actually do not look like the box is rebooting, at least they do not show up in the reboot log:
bishop@atollpi:~ $ last reboot
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 still running
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
reboot system boot 6.1.21-v7+ Wed Dec 31 18:00 - 17:35 (19568+22:35)
Not sure this is recording what I think its recording but, yesterday it was rebooting or appearing to reboot over and over and over. I've attached the journalctl output for all boot statements with the previous line for context but right now I have no idea what is causing this or how to address since I am not sure its really rebooting but something is going on. I am running an up to date Bullseye installation, since booting it back up yesterday and correcting the loose wire no reboot messages but now I am pretty paranoid, lol. I've attached 2 files one just pulls out all the boot statements with a line before and the other was a segment from yesterday when it was constantly rebooting, you can see it appears to be rebooting and then another boot statement but doesnt appear to be rebooting, I dunno this is pretty odd stuff but thought I would post to see if anyone has any ideas....
Thanks