Corrupt Database

I have had perform multiple soft resets in the past month. When reviewing the log files there are no error messages. Only a debugging message from Life360. Can anyone assist?

app:3042021-08-25 08:03:45.179 pm debugwebhookEvent ending

app:3042021-08-25 08:03:45.155 pm debugcalled arrived

app:3042021-08-25 08:03:45.150 pm debugchecking 629551cb-dd5f-4a64-80d0-d9ccad49f6e8 vs 629551cb-dd5f-4a64-80d0-d9ccad49f6e8 for in

app:3042021-08-25 08:03:45.074 pm debugselecting user device 304.653be6f2-9804-4457-91ad-d98eb54c6e12

app:3042021-08-25 08:03:45.070 pm debugwebhookEvent: Circle: 72747793-a03a-4490-bbbf-ebdd9794f84d, Place: 629551cb-dd5f-4a64-80d0-d9ccad49f6e8, User: 653be6f2-9804-4457-91ad-d98eb54c6e12, Direction: in

app:3042021-08-25 08:03:45.059 pm debugwebhook event params: [access_token:639945d2-bbef-460d-bacb-f34467375732, safetimeout:1, placeId:629551cb-dd5f-4a64-80d0-d9ccad49f6e8, circleId:72747793-a03a-4490-bbbf-ebdd9794f84d, userId:653be6f2-9804-4457-91ad-d98eb54c6e12, direction:in] [body:userId=653be6f2-9804-4457-91ad-d98eb54c6e12&circleId=72747793-a03a-4490-bbbf-ebdd9794f84d&placeId=629551cb-dd5f-4a64-80d0-d9ccad49f6e8&direction=in, requestSource:cloud, HOST:cloud.hubitat.com, headers:[Accept:[/], Newrelic:[eyJ2IjpbMCwxXSwiZCI6eyJ0eSI6IkFwcCIsImFjIjoiODY3MTMiLCJhcCI6Ijg1NzkyNDUzIiwidHIiOiJiZDM2MWFjN2ExNTc5YzlkIiwidHgiOiJiZDM2MWFjN2ExNTc5YzlkIiwicHIiOjAuNjQ2NDcsInNhIjpmYWxzZSwidGkiOjE2Mjk5NDcwMjUyNDd9fQ==], X-forwarded-port:[443], Host:[cloud.hubitat.com], User-agent:[curl/platform], Content-type:[application/x-www-form-urlencoded], X-forwarded-for:[54.152.62.173, 70.132.33.138], X-forwarded-proto:[https]]] null null

The debug messages look innocuous. Might consider looking at the Runtime Stats tab to see if you have any devices or apps that have abnormally high usage. Another suspect would be power fluctuations, if possible consider using a UPS or other means of providing continuous clean power. Along those lines if you're not using the power block that came with your hub, make sure that it is compatible and providing enough power.

1 Like

I cannot help you I'm afraid but in your logs I can see the access_token.
I'm not sure if there is any other info in these logs that people can put together and maybe access your hub.
Like I say, I'm not sure but you might want to just post a screen shot instead of cut & paste and blank out those tokens.
I know Bruce always asks for screenshots not cut & paste as it is easier to read.
Good luck with getting a solution.

1 Like

Thanks for the follow-up. I am using the power source that came with the hub and it is on a UPS. The Runtime Stats to my novice eye look reasonable. The device using the most recourses is a motion sensor and is at .013% of the total.

Maybe @gopher.ny can chime in

Please consider deleting the duplicate topics created for this issue. Keeping the discussion to one topic can help prevent things from getting fragmented, which should help minimize potential confusion.

https://community.hubitat.com/t/multiple-corrupt-database-problems-over-the-past-week/78574

3 Likes

Based on the errors in the log, please run this endpoint: http://hubs.ip.address.here/hub/advanced/flushClassloaderCaches

Looks like there is some sort of file system corruption. Running the endpoint should fix at least some of it by rebuilding user apps/drivers. I'll add logic to handle this without manual intervention in 2.2.9.

1 Like

When I cut and paste the amended link after inserting my hub IP address Chrome tells me the site isnt secure. When I allow it it seems to do nothing when I refresh. Should I see a confirmation or activity when the browser connects?
Thanks for your help

It should say "ok" in plain text.

Ok then it successfully loaded. Thanks. What now? Is there a confirmation that the it is done rebuilding?

No, it just flushed existing cached user apps/drivers, and is going to rebuild them from source the next time app/driver is called. Ping me if some issue manifests, otherwise I'll check the hub again in a few hours to see if anything else pops up in the logs.

1 Like

Thanks for your help.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.