IS http://192.168.0.90/brokenDatabase Broken? NOPE you just didn't read far enough

[Rxich]

I keep getting a corrupt database found when running this endpoint: http://192.168.0.90/brokenDatabase and even after doing a soft reset and before ever restoring a backup I still get the error.
This is on a C5 on the latest platform and even on older platforms, as I thought the update might fix it. BTW the hub runs okay, not much on it.
Also happens with my dev C7 on the latest platform, but my C4 & C7 production hubs are fine, no corrupt DB message

Even when I do a backup and restore I get the same thing

Has this endpoint been deprecated

[bertabcd1234]

Please provide a link to the documentation to support the presupposition this ever was
supported and what purpose it serves.

[neonturbo]

@Rxich

Has this endpoint been deprecated

I have never heard of that being a thing, and I usually have a pretty good memory about things like that.

Where did you find that endpoint?

[aaiyar]

Did you mean:

http://hubitat.local/hub/cleanupDatabase

[Rxich]

I have a document from some years ago where a collection of endpoints was published. I'm not certain if it was official.
Here's one example: C-8 inexplicably went offline this morning

Failure to boot

Can you try power cycling it and then going to http://hubs.ip.address.here/brokenDatabase ? Power cycle should unlock whatever may be locked on the file system, which may be the case here. The http://hubs.ip.address.here/brokenDatabase page will say "corrupt database found", but that's hardcoded on the page, it doesn't actually check. More importantly, there's a way to do a soft reset from there, and it should take you straight to the restore page after a reboot.

Right from the gopher's mouth

[bertabcd1234]

@Rxich

Right from the gopher's mouth

And as he says:

@gopher.ny

The http://hubs.ip.address.here/brokenDatabase page will say "corrupt database found", but that's hardcoded on the page, it doesn't actually check.

Going to this page doesn't test anything, which it sounds like is what you're assuming. It‘s just going to show you that message. Going there manually is one way you can do a soft reset (an option on that page) if you can't some other way for some reason.

This is normally just some place the hub would take you on its own, and that should be pretty rare given ways it can recover from this. Or to answer the original question: no, it is not broken.

[Rxich]

It's odd, not all of my hubs displayed the corrupt database message, so in failing to read the whole post, I ASSumed the message was valid, I was wrong, sorry guys, fixed the title.