Error 500

bobbles · April 6, 2018, 6:27pm

It’s happened again.
Automation may be local but thats of little comfort if nothing works.

cuboy29 · April 6, 2018, 6:31pm

DB corrupted also? I saw something strange with file corruption yesterday while deleting devices and editing a rule in RM. Not sure if those events are related to the file corruption issue or not. I deleted my ECObee integration which deleted all the thermostat and temperature sensors BUT there were a few rules that were still using those devices that got deleted. When I try to edit those rule with the missing devices, I started getting error staying file corruption hence error 500. I was able to reboot yesterday and got back into RM to edit the rules with the missing devices and save. Hopefully nothing is corrupted anymore.

Back up often to protect yourself.

bobbles · April 6, 2018, 6:39pm

2 reboots and I’m back working again.
This is becoming to regular for my liking.
May migrate back to ST.

EdwardN · April 6, 2018, 6:55pm

Ok, don’t do that. Before you remove a device, check if it’s connected to automations (it’ll say which apps are using the device at the bottom) and remove the device from the automations first.

cuboy29 · April 6, 2018, 8:13pm

Yes, I should have edited the rules before removing a device, BUT there need to be some safeguards in place to prevent impatient people like me from doing stupid stuffs like that that can cause extensive down time.

bobbles · April 6, 2018, 8:34pm

Managed to get things back on track by doing a restore from 2 days ago, deleting a webCoRE piston and a device.
The device was deleted before without deleting it from a piston first.
I agree. Perhaps devices should not be able to be deleted if they are still tied to an automation.
It’s not an issue for me in ST.
It’s all a learning curve.

EdwardN · April 6, 2018, 8:49pm

@bravenel Could you add a warning or just block people from deleting devices still attached to automations? Seems like this is starting to cause problems.

bravenel · April 6, 2018, 9:00pm

It does warn you, and it should not cause a problem.

cuboy29 · April 7, 2018, 4:47am

Well this is just great… Error 500 again tonight. I didn’t do anything either. Things were working fine this afternoon and now error 500. Time to power cycle I guess. @bobbyD what’s going on?

So power cycle brought things back to normal for now.

stephack · April 11, 2018, 1:25am

I just got the error 500 tonight as well. The hub froze up in the middle of configuring an RM rule. Had to pull the plug. It’s now stuck at 70% for the past 5 minutes. Going to pull the plug again and pray.

@bravenel @patrick any idea what’s going on here. I was noticing lag spikes on 706 from time to time. Now full lockup on 707. Getting a bit worried here.

stephack · April 11, 2018, 1:33am

Ok…so a second hard reboot got the hub online…BUT…it seems to have automatically reverted to an old database. I now have a device that I deleted earlier today is back. Everything that I configured today, including a updating 5 apps, 4 dashboards, etc…all gone. NOT HAPPY

cuboy29 · April 11, 2018, 1:51am

yes, it’s seems to be doing auto restore of a previous version as I found out too. I found that out too. I wish I know what is causing the error 500. Are they any logs that support can get to help diagnose this?

bravenel · April 11, 2018, 1:55am

What were you doing when you got the 500?

stephack · April 11, 2018, 1:56am

The timing of this is what making it so aggravating. I didn’t have time all week to make a bunch of changes and I picked today to spend a few hours adjusting a few rules and configuring the new 707 options…then proof all gone. I can’t even remember everything I updated today.

stephack · April 11, 2018, 1:58am

I was just recreating a RM rule to work with 2 motion sensors (I couldn’t get the Motion aggregator to work right). The page froze and when I refreshed I got the 500 error

bravenel · April 11, 2018, 1:59am

I need more details about what specifically you were doing, what page you were on.

stephack · April 11, 2018, 2:03am

I was configuring a Triggered rule. In the middle of "actions for false ". Can’t remember the exact field for sure but I believe I was somewhere in the turn off dimmers section.

bravenel · April 11, 2018, 2:08am

OK, so when you “pull the plug”, there is a good chance that the database becomes corrupted when you do that.

Before resorting to that, open another tab in your browser and see if the hub is alive or not. If a page is “frozen”, best bet is to close that tab, not to pull the plug. If the database became corrupted, the hub is going to load the most recent backup, since loading a corrupted database won’t get you anywhere at all. We highly recommend against pulling power.

stephack · April 11, 2018, 2:13am

I tried to connect to the hub from my phone and my PC. I even force closed chrome on my phone to make sure it wasn’t the browser. All displayed error 500. I then waited 10 minutes before pulling the plug.

cuboy29 · April 11, 2018, 2:14am

As I said, nothing was done. I just logged in but all I see is the error 500.