Corrupt database error

Hello, less than a year ago I was forced to buy a C8 after the C7 displayed a blue light which would not go green. The first sign of trouble was the hub refusing to update, whenever I tried to update it would fail. After some soft resets I got the corrupt database error, even after restoring older backups. Eventually I got a blue light and that was it.
I decided to buy a C8 which worked well for about 6 months and now the hub is refusing to update, failing whenever you try. After soft resetting, I am now getting a corrupt database error.
I restored to an earlier version but still refuses to update. Any help would be greatly appreciated.

David

What are you using to power the hub?

1 Like

For issues with updating try

3 Likes

Couple of things.
1: Are you using the OEM power supply that came with the hub? If not do so.

2: under settings>>network setup>>Network Settings>>Ethernet Speed. If it's set for auto, change to fixed. If fixed change to auto and see if it updates then.

You should also get a Hub Protect sub if you don't have one already. (This will allow backup of the zigbee and z-wave radios)

2 Likes

Blue light is usually fully recoverable via the diagnostic tool.

Soft reset clears the database, I dont see how that would result it in saying it corrupted. Unless it says that after you restored the latest backup?

You provide almost no details.
Refuses to update how? Error? Stalls?
What version is the hub on right now?

First thing I recommend when update wont complete is to do it from the diagnostic tool, use the Download Latest button to download the update, then Restore Previous to install it.

1 Like

Hello Slate, the hub is plugged into a UPS which is plugged into the mains.

thebearmay, I have tried sever times toggling between ethernet speeds with no positive effects.

Thank you rlithgow1, I am using the OEM power supply and I also am using a new ethernet cable, hub is using wired internet rather that wifi.

under settings>>network setup>>Network Settings>>Ethernet Speed. If it's set for auto, change to fixed. If fixed change to auto and see if it updates then.

jtp10181, I will supply all details shortly.

Hi all. I have tried the ethernet speed switching already and soft reset. After restoring 2.4.0.144, 2.4.0.147 and 2.4.0.151 I got corrupt database error so I restored the original database the hub came with (2.3.9.201) and that is what is currently running.
Issues I encountered are difficulty in switching between ethernet speeds, corrupt database error, hub will not download new updates (starts but before it even reaches 1% I get an update failed error). New databases run for a while but slowly most automation notification stop working.
I am at a lost as to what to do next. Any help would be appreciated. The hub is less that one year old.

Restore from your latest database. Rebuild that database after. Then update the platform itself

Thats the issue, even after restoring to previous databases, the hub refuses to update. Something else is wrong, I just cant figure out what it is. Failure to update is the main issue here, its solution beats me.

Failure to update is nearly always some network configuration issue.

Did you play with any of the settings in Hubitat Network settings, like Static IP or DNS settings?

Is there some Antivirus or other protection in your router blocking outside connections?

While you are in the Hubitat network settings, can you ping Hubitat.com or Amazon.com? (network tests link in top right of the network settings page)

Neonturbo, no recent installs of antivirus that I can remember. I did try the ping in the network settings and it did return all packets. Could you please tell me how I can ping websites like hubitat or amazon?

This may be something your router firmware installed automatically.

Literally type in Amazon.com or Hubitat.com in the box, and tap the Ping button.

Oh..I can ping amazon and every other website I typed in..all work. I will post the results below.
However the ping fails for hubitat everytime. Now here is the strange part..the hub in question is at a friends house so we are talking by phone and I am relaying the results to you. At my home where I have a working C8...I get the very same results...go figure.

Amazon
PING amazon.com (205.251.242.103) 56(84) bytes of data.
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): icmp_seq=1 ttl=235 time=86.8 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): icmp_seq=2 ttl=235 time=85.0 ms
64 bytes from s3-console-us-standard.console.aws.amazon.com (205.251.242.103): icmp_seq=3 ttl=235 time=84.0 ms

--- amazon.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 83.997/85.260/86.773/1.146 ms

Hubitat
ping failed

The ping of hubitat.com may not be a valid test. It looks like they are setup to block icmp. I can't ping it either.

You may want to try the traceroute tool instead of ping to validate it resolves hubitat.com.

mavrrick58..I am not too sure what a successful traceroute looks like but a list of ip addresses came up. I can see my service provider and another address in florida below. Last line are three asterixs down to 29. Not too sure if its safe to post the return here, please let me know.

Basically the traceroute just lists all the devices you go through to get to the destination. So from you hub to your router, then to your ISP, and then onward. Some lines may only show * * * if they have some network stuff turned off.

Reguardless of the path the important part is it resolved a IP and tried to get there. The path could be important for a deep troubleshooting stuff at the ISP level, but not here.

As far as if it ia safe, well probably. All it would likely show is your gatewaym the traceroute wouldn't list your ip.