Hub scheduler failed to start

Get Help
1

I have a C7 hub running platform version 2.5.0.159. I noticed recently that while I can control devices manually, automations are not working as intended. One example is turning on interior lights via a switch when the garage door opens. Logs on the hub indicate the garage events and I can still control the lights manually.

On digging in, there’s an error that indicates that, “Hub scheduler failed to start.” And the hub logs page shows the following event on startup (middle line below) :

image
image1574×230 21.2 KB

Checking the specific automation noted above, I tried to delete the automation to troubleshoot which also failed. In the logs after the delete event, there was this error :

image

I think these two things are related but having not run into these issues before or interacting with SQL tables on the hub, I’m not sure what my next steps are.

I’ve currently worked around this by exposing the devices I need to a C8 hub and running automations there. That said, I’d prefer to keep those automations on the ‘local’ hub.

I’m open to any ideas that anyone has. Thanks for taking the time to review.

2

I've never seen that.

I would try rebooting with the option checked to rebuild the database.

3

Thanks for your response @chrisbvt. I forgot to mention that I had tried that and I just did again but the same error is logged at about the same point in the reboot sequence.

4

If it is not the database itself, maybe something is hosed in the platform. You could try using the diagnostic tool to revert to the previous platform level, and if that fixes it, do the update again to get current.

I have no idea what is actually going on, I'm just throwing stuff out there to try. :slightly_smiling_face:

Edit: Another thought, if that doesn't fix it, maybe it is an issue in your database that is just not being fixed by the rebuild tool. At that point I would use the diagnostic tool to restore a backup from when it last worked to get back to a working database.

5

Well, I’m clearly incomplete in explaining all of my troubleshooting steps but I did the platform level revert as well.

My next step will be to nuke and start over to see if that helps but repairing devices and hubs is something I was hoping to avoid.

6

A soft reset isn't too bad to go through, so I would just do that and restore a backup from when it worked, before going nuclear.

Edit: If you have not done a soft reset before, it doesn't effect your devices. So you can just restore a local backup, and all devices will still be there. You don't need a cloud backup with device data in it for a soft reset.

If you do go full nuclear, and you don't have a cloud backup, it will take a lot more time to rebuild everything after re-pairing devices.

If you are not sure when the issue started, you may need to try some older backups if the first attempt doesn't fix it.

7

Ask for support's help before you reset

@support_team

8

Do you have a recent backup? If yes, restoring one should fix the issue.

9

Same issue here. Migrated via C5 (latest release) to C8 via temporary Cloud Backup nd restore. Hub Scheduler does not start due to an App (rule) not found which DID exist.

For grins, deleted the rule and it still fails.

Did all the fun chicken dances:

  • soft reset ; restore from backup (of various platform versions)
  • reboot with rebuild database

Scheduler just fails to start
Most fun part is:

  • upgrading platform from the UI fails (download slow, then timesout)
  • upgrade from diagnostic tool works

but everything feels like the db is junked up.

6 years later and we still don’t have a true diagnostic utility to triage/fix the db?

10

Can you PM me the hub id? I'd wager it's not the database itself but some data inconsistency. We got endpoints to fix missing/broken jobs, but doing it automatically can be risky.

11

It’s been a minute since I’ve been in this forum, very appreciative to see the fast response , thanks @gopher.ny I’ve DM’ed the details.