# Ignition 8 Gateway Randomly Stops

**URL:** <https://forum.inductiveautomation.com/t/ignition-8-gateway-randomly-stops/33625>\
**Category:** Ignition\
**Created:** [April 2, 2020, 2:31pm UTC](https://forum.inductiveautomation.com/t/ignition-8-gateway-randomly-stops/33625 "2020-04-02T14:31:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon222](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@brandon222](https://forum.inductiveautomation.com/u/brandon222)\
**Post date:** [April 2, 2020, 2:31pm UTC](https://forum.inductiveautomation.com/t/ignition-8-gateway-randomly-stops/33625/1 "2020-04-02T14:31:35Z")

</div>

Hi there,

I have used Ignition for many years now without any issues. Now that we have transitioned to 8 I noticed that randomly the gateway will stop. The clients will show the Gateway Connection Lost popup and if I look in the services of the computer it shows the Ignition Gateway as stopped. I have set it now to restart if lost which helps but the gateway is still lost randomly and I know its not a networking issue as it loses itself on the computer running the gateway as well. Anyone have any ideas? or had similar issues.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 2, 2020, 3:06pm UTC](https://forum.inductiveautomation.com/t/ignition-8-gateway-randomly-stops/33625/2 "2020-04-02T15:06:18Z")

</div>

There should be something in the wrapper log or in your server’s event log.

---

<div class="post-metadata">

**Author:** ![brandon222](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@brandon222](https://forum.inductiveautomation.com/u/brandon222)\
**Post date:** [April 2, 2020, 3:46pm UTC](https://forum.inductiveautomation.com/t/ignition-8-gateway-randomly-stops/33625/3 "2020-04-02T15:46:53Z")

</div>

Just checked the server event log and there is this error 🙂

java.lang.IllegalArgumentException: Specified historical sink ‘Alarming’ does not exist.

at com.inductiveautomation.ignition.gateway.history.HistoryManagerImpl.storeHistory(HistoryManagerImpl.java:166)

at com.inductiveautomation.gateway.tags.history.actor.HistoryActorFactory$DelayedEvaluationContainer.process(HistoryActorFactory.java:887)

at com.inductiveautomation.gateway.tags.history.actor.HistoryActorFactory$DelayedEvaluationContainer.run(HistoryActorFactory.java:848)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)

at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.base/java.lang.Thread.run(Unknown Source)

could that be the cause?

---

<div class="post-metadata">

**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:** [April 2, 2020, 3:50pm UTC](https://forum.inductiveautomation.com/t/ignition-8-gateway-randomly-stops/33625/4 "2020-04-02T15:50:51Z")

</div>

Probably not. If you don’t know what to look for, you should really contact support.

---

<div class="post-metadata">

**Author:** ![brandon222](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@brandon222](https://forum.inductiveautomation.com/u/brandon222)\
**Post date:** [April 2, 2020, 5:52pm UTC](https://forum.inductiveautomation.com/t/ignition-8-gateway-randomly-stops/33625/5 "2020-04-02T17:52:17Z")

</div>

I noticed I was on version 8.0.4 . I just upgraded to 8.0.10. I am hoping that fixes the problem. If not I will contact support. Just curious to see if anyone else was having the same issue