"ERROR 500" accessing Logs since 2.3.0 upgrade

Upgraded from 2.2.9.latest to 2.3.0 this morning on both of my C7 hubs. On one of the hubs, I now get "ERROR 500: A Server error has occurred" on one of the hubs after boot. Any suggestions?

Can you PM me your hub's UID? I can take a look at the engineering logs on the hub.

Good chance that you have a corrupted database that limped along without problems until the reboot,. I had a similar thing happen early in the 2.2.9 release sequence.

My suggestion, if you can get to the Diag Tools menu (your.hub.IP:8081), would be to do a Soft Reset and then go back a few database backups for the restore when the Soft Reset completes.

EDIT: Victor (@gopher.ny ) is on the case, he will give the best advice. Leave it so that he can figure it out and put proactive code into the next release.

This looks like a bug. Depending on what apps/drivers actively run at the moment, a refresh may bring the page up. In the long term, it will require a code fix, to be done in the next iteration of 2.3.0.

3 Likes

Ok, thanks.

Same issue. can' t restore any backup. just error 500. need help.

Can you PM me your hub's id? I can take a look at the engineering logs on the hub.

1 Like