# The devices disappear from the Connected Devices list **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [August 1, 2019, 2:11pm UTC](https://forum.inductiveautomation.com/t/the-devices-disappear-from-the-connected-devices-list/27082 "2019-08-01T14:11:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![juan.guerrero](https://avatars.discourse-cdn.com/v4/letter/j/b38774/32.png) [@juan.guerrero](https://forum.inductiveautomation.com/u/juan.guerrero)\ **Post date:** [August 1, 2019, 2:11pm UTC](https://forum.inductiveautomation.com/t/the-devices-disappear-from-the-connected-devices-list/27082/1 "2019-08-01T14:11:10Z")
Hello everyone I have a problem with the Ignition Gateway, I usually have 35 devices connected, but now only 18 appear. I don’t know what happened to the other devices. I have already restarted the service more than 5 times, but the others still do not appear. I already checked the logs but I’m not sure what the error means. I hope you can help me. ```auto INFO | jvm 1 | 2019/08/01 08:58:09 | E [x.s.DeviceManager] [12:58:09]: Error adding driver 'CX4823FPZ3' of type 'LogixDriver'. module-name=Logix Driver INFO | jvm 1 | 2019/08/01 08:58:09 | simpleorm.utils.SException$Jdbc: Opening com.inductiveautomation.ignition.gateway.localdb.CountingDataSource@5cbd6c2d INFO | jvm 1 | 2019/08/01 08:58:09 | at simpleorm.sessionjdbc.SSessionJdbc.innerOpen(SSessionJdbc.java:113) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.localdb.persistence.PersistenceSession.initialize(PersistenceSession.java:31) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.localdb.PersistenceInterfaceImpl.getSession(PersistenceInterfaceImpl.java:62) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.model.BaseExtensionPointType.findProfileSettingsRecord(BaseExtensionPointType.java:105) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.xopc.drivers.logix.LogixDriverType.createDriver(LogixDriverType.java:24) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.xopc.server.devices.DeviceManager.loadDriver(DeviceManager.java:240) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.xopc.server.devices.DeviceManager.loadAllOfType(DeviceManager.java:212) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.xopc.server.devices.DeviceManager.registerDriverType(DeviceManager.java:178) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.xopc.driver.common.AbstractDriverModuleHook.serviceReady(AbstractDriverModuleHook.java:99) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.services.ModuleServicesManagerImpl.subscribe(ModuleServicesManagerImpl.java:96) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.xopc.driver.common.AbstractDriverModuleHook.startup(AbstractDriverModuleHook.java:68) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.xopc.drivers.logix.LogixDriverHook.startup(LogixDriverHook.java:60) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl$LoadedModule.startup(ModuleManagerImpl.java:2273) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl.startup(ModuleManagerImpl.java:385) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.SRContext.startupInternal(SRContext.java:1394) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl.startup(RedundancyManagerImpl.java:224) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.SRContext.asyncInit(SRContext.java:1036) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.SRContext.access$300(SRContext.java:289) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.SRContext$2.run(SRContext.java:767) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:518) INFO | jvm 1 | 2019/08/01 08:58:09 | at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) INFO | jvm 1 | 2019/08/01 08:58:09 | at java.util.concurrent.FutureTask.run(Unknown Source) INFO | jvm 1 | 2019/08/01 08:58:09 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) INFO | jvm 1 | 2019/08/01 08:58:09 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) INFO | jvm 1 | 2019/08/01 08:58:09 | at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) INFO | jvm 1 | 2019/08/01 08:58:09 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) INFO | jvm 1 | 2019/08/01 08:58:09 | at java.lang.Thread.run(Unknown Source) INFO | jvm 1 | 2019/08/01 08:58:09 | Caused by: java.sql.SQLException: Connection is locked. Datasource only allows one connection at a time. More information was logged to the gateway console. INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.localdb.sqlite.SingleConnectionDatasource.getConnection(SingleConnectionDatasource.java:75) INFO | jvm 1 | 2019/08/01 08:58:09 | at com.inductiveautomation.ignition.gateway.localdb.DelegatingDataSource.getConnection(DelegatingDataSource.java:60) INFO | jvm 1 | 2019/08/01 08:58:09 | at simpleorm.sessionjdbc.SSessionJdbc.innerOpen(SSessionJdbc.java:111) INFO | jvm 1 | 2019/08/01 08:58:09 | ... 26 common frames omitted ``` ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [August 1, 2019, 2:38pm UTC](https://forum.inductiveautomation.com/t/the-devices-disappear-from-the-connected-devices-list/27082/2 "2019-08-01T14:38:05Z")
Can you upload the rest of the logs? Do you have any custom modules installed? The internal database Ignition uses to store all configuration and settings is a SQLite file. SQLite only allows one connection at a time [1], to help ensure data correctness. Ignition itself _should_ be the only connection to that database, but the error is indicating that something _else_ has already established a connection, so Ignition isn’t able to. [1]: Technically, there are exceptions to this that allow multiple concurrent reads, but we’re not using them because it makes things that much more likely to break. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [August 1, 2019, 2:48pm UTC](https://forum.inductiveautomation.com/t/the-devices-disappear-from-the-connected-devices-list/27082/3 "2019-08-01T14:48:05Z")
This is indicative of a more serious issue with your Ignition gateway - the internal DB seems to be under massive contention. The most common cause I see for this is the use/abuse of `system.tag.browse`, when done frequently, often in a tag via `runScript`. ---
**Author:** ![juan.guerrero](https://avatars.discourse-cdn.com/v4/letter/j/b38774/32.png) [@juan.guerrero](https://forum.inductiveautomation.com/u/juan.guerrero)\ **Post date:** [November 28, 2023, 8:24pm UTC](https://forum.inductiveautomation.com/t/the-devices-disappear-from-the-connected-devices-list/27082/4 "2023-11-28T20:24:43Z")
It's been more than 4 years since then and still I have the same issue. Not only with one gateway but several of them. The only workaround I have found is disable the tag providers before to restart the service. ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [November 28, 2023, 8:35pm UTC](https://forum.inductiveautomation.com/t/the-devices-disappear-from-the-connected-devices-list/27082/5 "2023-11-28T20:35:28Z")
> [@juan.guerrero](#): > > It's been more than 4 years since then and still I have the same issue. > Not only with one gateway but several of them. Did you create a support ticket? This forum is not official support. That being said, two IA employees responded to your post 4 years ago and you didn't respond back. ---
**Author:** ![brian.mcenulty](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@brian.mcenulty](https://forum.inductiveautomation.com/u/brian.mcenulty)\ **Post date:** [November 28, 2023, 10:35pm UTC](https://forum.inductiveautomation.com/t/the-devices-disappear-from-the-connected-devices-list/27082/6 "2023-11-28T22:35:20Z")
I recently ran into a similar (but not the same) issue which was caused by a runScript call on an expression tag to the system.devices.listDevices() function. The gateway in question would show a different number of devices on the primary and backup gateways for a redundant pair. I never saw the same log entries you had listed, but it's worth mentioning.