Hubitat no longer sending or receiving signals at all

Hubitat is non operational, worked fine for a little over one year... then had a few errors and slowly stopped operating devices. I removed the non operating devices. at this point out of about 50 devices only a few will work sporadically. IThe last month has been a disaster, it controls too much at our home to give it up at this point and now we are going out of town and I am heading to buy timers for aquarium lighting. It's needing restarted to give one signal then the next morning again needs restarted.

I need help and I have no idea where to start on thing.
thanks,
Ernie

there are hundreds of lines of this in the log:

dev:2892019-12-24 01:10:12.801 pm error Connections could not be acquired from the underlying database!

dev:2892019-12-24 01:10:09.097 pm error Connections could not be acquired from the underlying database!

dev:2892019-12-24 01:08:12.137 pm error Connections could not be acquired from the underlying database!

dev:2892019-12-24 01:08:12.128 pm error Connections could not be acquired from the underlying database!

dev:2942019-12-24 01:08:08.522 pm error java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. (parse)

dev:2892019-12-24 01:08:08.484 pm error java.sql.SQLException: Connections could not be acquired from the underlying database! (parse)

dev:2892019-12-24 01:08:08.434 pm error Connections could not be acquired from the underlying database!

dev:2312019-12-24 01:07:27.880 pm debug Executing 'refresh'

dev:2892019-12-24 01:05:56.756 pm error java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. (parse)

dev:2892019-12-24 01:05:56.660 pm error Connections could not be acquired from the underlying database!

dev:2892019-12-24 01:05:52.940 pm error java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. (parse)

dev:2892019-12-24 01:05:52.880 pm error java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. (parse)

dev:2592019-12-24 01:02:58.108 pm error java.sql.SQLException: Connections could not be acquired from the underlying database! (parse)

dev:2572019-12-24 12:58:36.896 pm error java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. (parse)

dev:2572019-12-24 12:58:36.837 pm error An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down.

dev:2312019-12-24 12:58:36.851 pm error java.sql.SQLException: An SQLException was provoked by the following failure: com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down. (refresh)

Given all your SQL errors it appears your database is corrupted. I would recommend downloading a recent backup and performing a soft reset. Also contact support while you are at it
https://docs.hubitat.com/index.php?title=Soft_Reset

2 Likes

I would do a reboot first.. That should clear your errors..

Which type of apps do you have installed? There is a known issue when it comes to resource management and the Hubitat team is trying to track that down, however, it has been proven to be difficult to identify the root cause.

While you are out of town, you might want to consider to do a nightly reboot via Rule Machine. There are several users here that do that until the root cause has been fixed. It has also shown that there are some misbehaving apps out there that can cause issues with resources. That's why I asked what you had installed.

1 Like