Crash/Lockup - Possible Death During Backup

🛎️ Get Help
1

Here's the log from the last log entry to first few after a power-cycle of an unresponsive C7 on the 2.2.8.147 release. Is there any sort of crash log? 3:32am is not a very active time, so the only process that could be taxing would be the backup. I did not notice any failures to automate, as I only arrived home at 2:30pm, and the door locks and such are autonomous.

My C4 never crashed once, but died an early death, and was replaced by a C7. Bad choice?

=-=-=-=-=-=-=-=-=

dev:752021-08-31 02:58:48.999 pm infoRecovery feature ENABLED

dev:4262021-08-31 02:58:48.439 pm infogetDriverVersion() = v1.1.1.1123T

dev:752021-08-31 02:58:48.379 pm infogetDriverVersion() = v1.0.1.1123

dev:4262021-08-31 02:58:48.320 pm infotasmota_refresh(metaConfig=null)

dev:4262021-08-31 02:58:48.193 pm infogeneralInitialize()

dev:4262021-08-31 02:58:48.191 pm infoinitialize()

dev:752021-08-31 02:58:48.148 pm infoinitialize()

dev:5422021-08-31 03:32:35.229 am debugParse returned L2 Energy: 162.29 kWh

dev:5422021-08-31 03:31:05.120 am debugParse returned L2 Energy: 162.25 kWh

dev:5422021-08-31 03:28:50.886 am debugParse returned L1 Energy: 167.76 kWh

dev:5422021-08-31 03:28:10.100 am debugParse returned L2 Power: 261.0 Watts

dev:5422021-08-31 03:26:45.439 am debugParse returned L1 Power: 120.5 Watts

dev:5422021-08-31 03:21:37.612 am debugParse returned L2 Energy: 162.22 kWh

dev:5422021-08-31 03:18:43.340 am debugParse returned L1 Energy: 167.75 kWh

dev:5422021-08-31 03:16:59.228 am debugParse returned L1 Power: 121.8 Watts

dev:5422021-08-31 03:16:59.228 am debugParse returned L2 Power: 261.3 Watts

2

It can occur that the DB gets corrupted. When this occurs, it is necessary to do a soft reset from: http://hubitat.local:8081 and then restore the latest DB backup.

  1. Download the latest backups (They should still be available after the soft reset, but a good idea just in case)
  2. Perform a soft reset
  3. After the reset is done, go to Backup and restore the latest one
3

Thanks, but I was more interested in knowing the CAUSE of the crash / lockup. It does me no good to erase the clues that might tell me what happened. So, I'll ask again - Is there any sort of crash log?

4

Not that we would have access to. Might ask support if there is something they can look at.

3 Likes
5

I’ll second that. @support_team have some visibility that a regular user doesn’t. They might be able to help you find the cause of the issue.

2 Likes
6

Can you send me the hub id in a PM? I'll take a look.

7

Thanks, PM sent, and firewall open, but hub is on a NAT address. (192.168.1.166)