Have a C8Pro that has taken to restarting itself several times a week. It is running the latest build and is always kept up to date.
I am running Hub Information on it and writing this information out to syslog and see nothing unusual in terms of memory, etc. I am only monitoring this information every 5 minutes so a sudden spike would not be caught.
I am not running Zwave or Zigbee on this hub. I do that on dedicated hubs and leave this one for app management and rule processing.
I filled out a tech support request but didn't receive a confirmation or response yet. So I am not sure if that went through.
My thought is to swap out the hardware at this point but open to other suggestions.
Please provide your hub model (C7, C8, etc.) and its platform version from Settings>Hub Details.
Check out the following post for help troubleshooting problems and gathering details that will help others to identify and solve the problem you are experiencing: ‼ READ FIRST - Before Posting in Get Help
Nothing. As I mentioned I have everything going into syslog and I have looked at the logs up to the hub restart and there is nothing. Plus I am monitoring through the hub information third party device and nothing looks out of the ordinary there.
I was just familiarizing you with the support page; I don't know how long you have been using Hubitat.
You can try specifically tagging bobbyD if there are no good suggestions here today and you find no way to track what's the issue is.
Support can look at the engineering logs in your hub and possibly find the issue.
Sorry to fixate on this, but by everything you mean all the logs, not just hub info logs? In your OP you only talked about exporting logs when talking about hub info. I'm assuming you mean all logs.
The only reason I wanted to check, and for my last post, is I would have expected if the platform initiated a restart there would be some kind of log... At least in the location events tab
Thanks - I appreciate that. I didn't know if that was a new approach they had introduced. As I mentioned I did fill out the support form but can't see any confirmation. I usually don't tag Bobby until I have exhausted all possibilities. But I might be getting there.
I think they are pretty good about begin tagged when all else pulls your hair out.
From what I have seem over the years, the HE users don't abuse the tagging and they appreciate that.
Unusual behavior doubled by more uncertainty due to absence of logs to give you a clue. Please send us a private message along with your hub id so we can check the engineering logs for clues @support_team
Now, if you have custom apps and drivers that don't properly log activity, that could explain the missing logs.
I have a version of the syslog relay that I modified - which doesn't send everything through - but is a good starting point. That captures everything coming through the logsocket web socket. I also wrote drivers to take Z-Wave and Zigbee logs from the respective web sockets and send them out to my syslog server. Although not relevant here as this hub has the radios disabled. Finally I use the excellent Hub Information plug-in running that captures a lot of data and that gets to syslog as well.
I don't think location services get picked up this way. But I have checked in there and there is nothing unusual.
My operating hunch is the power strip it is plugged into it's glitching. It is an automated strip so I can control the power to the hubs. This is all plugged into a large UPS so it shouldn't be an issue. But I am going to bypass that and see what happens.
