Gateway stopped after running some times

Ignition
1

Hello,
I have met a headake problem that ignition service stopped due to some unknown reasons. I got some logs as below. I could start the service manually ,but it will stop after some time. anyone can give some advise to reslove this problem? thanks

STATUS | wrapper | 2020/05/30 13:24:29 | --> Wrapper Started as Service
STATUS | wrapper | 2020/05/30 13:24:30 | Java Service Wrapper Standard Edition 64-bit 3.5.35
STATUS | wrapper | 2020/05/30 13:24:30 | Copyright © 1999-2018 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2020/05/30 13:24:30 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2020/05/30 13:24:30 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2020/05/30 13:24:30 |
WARN | wrapper | 2020/05/30 13:24:43 | Child process: Java version: timed out
STATUS | wrapper | 2020/05/30 13:24:43 | <-- Wrapper Stopped
STATUS | wrapper | 2020/05/30 18:16:28 | --> Wrapper Started as Service
STATUS | wrapper | 2020/05/30 18:16:29 | Java Service Wrapper Standard Edition 64-bit 3.5.35
STATUS | wrapper | 2020/05/30 18:16:29 | Copyright © 1999-2018 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2020/05/30 18:16:29 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2020/05/30 18:16:29 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2020/05/30 18:16:29 |
WARN | wrapper | 2020/05/30 18:16:42 | Child process: Java version: timed out
STATUS | wrapper | 2020/05/30 18:16:42 | <-- Wrapper Stopped
STATUS | wrapper | 2020/06/01 10:02:05 | --> Wrapper Started as Service
STATUS | wrapper | 2020/06/01 10:02:06 | Java Service Wrapper Standard Edition 64-bit 3.5.35
STATUS | wrapper | 2020/06/01 10:02:06 | Copyright © 1999-2018 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2020/06/01 10:02:06 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2020/06/01 10:02:06 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2020/06/01 10:02:06 |
WARN | wrapper | 2020/06/01 10:02:19 | Child process: Java version: timed out
STATUS | wrapper | 2020/06/01 10:02:20 | <-- Wrapper Stopped
STATUS | wrapper | 2020/06/01 11:11:53 | --> Wrapper Started as Service
STATUS | wrapper | 2020/06/01 11:11:53 | Java Service Wrapper Standard Edition 64-bit 3.5.35
STATUS | wrapper | 2020/06/01 11:11:53 | Copyright © 1999-2018 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2020/06/01 11:11:53 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2020/06/01 11:11:53 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2020/06/01 11:11:53 |
WARN | wrapper | 2020/06/01 11:12:05 | Child process: Java version: timed out
STATUS | wrapper | 2020/06/01 11:12:05 | <-- Wrapper Stopped
STATUS | wrapper | 2020/06/03 11:04:26 | --> Wrapper Started as Service
STATUS | wrapper | 2020/06/03 11:04:26 | Java Service Wrapper Standard Edition 64-bit 3.5.35
STATUS | wrapper | 2020/06/03 11:04:26 | Copyright © 1999-2018 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2020/06/03 11:04:26 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2020/06/03 11:04:26 | Licensed to Inductive Automation for Inductive Automation
STATUS | wrapper | 2020/06/03 11:04:26 |
WARN | wrapper | 2020/06/03 11:04:40 | Child process: Java version: timed out
INFO | wrapper | 2020/06/03 11:04:40 | Wrapper Process has not received any CPU time for 11 seconds. Extending timeouts.
STATUS | wrapper | 2020/06/03 11:04:41 | <-- Wrapper Stopped

2

This usually means the server is overloaded and doesn't give enough CPU time to Ignition to start up within the time limit. This can sometimes be mitigated by using a delayed startup setting on the service in windows, or setting a service dependency in linux on something else.

Or separate your functions so Ignition has a server (or VM) to itself.

3

Thanks, I have set a delay startup for IG and seems worked well