HI all,
So, I took a backup of my laptops local gateway which was running a project I was using to experiment with the Ignition software with the intention of deploying another configuration over the top such that i could work locally on an issue we have (without the need to remote in over the internet and all the potential issues that come with that).
After the backup, I proceeded to deploy the GWBK file for the project i wanted to work on over the top.
Problem is, it got to a point whereby the gateway was reporting a 'Gateway is: Uknown' status.
Looking through the wrapper, it all seems as if it was going well, until, it attempted to restart...at which point it decided it had detected an error:
INFO | jvm 1 | 2023/10/18 14:55:50 | I [g.IdpAdapterManager ] [13:55:50]: Shut down in 0 ms
INFO | jvm 1 | 2023/10/18 14:55:50 | I [g.PersistentRecordIdpAdapterMetricsService] [13:55:50]: Shut down in 0 ms
INFO | jvm 1 | 2023/10/18 14:55:50 | I [g.PersistentRecordIdpAdapterConfigService] [13:55:50]: Shut down in 0 ms
INFO | jvm 1 | 2023/10/18 14:55:50 | I [g.SecurityLevelManager ] [13:55:50]: Shut down in 0 ms
INFO | jvm 1 | 2023/10/18 14:55:50 | I [g.PersistentRecordSecurityLevelConfigService] [13:55:50]: Shut down in 0 ms
INFO | jvm 1 | 2023/10/18 14:55:50 | I [IgnitionGateway ] [13:55:50]: Ignition Gateway shut down in 2712ms
INFO | jvm 1 | 2023/10/18 14:55:50 | 14:55:50,431 |-INFO in ch.qos.logback.classic.AsyncAppender[SysoutAsync] - Worker thread will flush remaining events before exiting.
INFO | jvm 1 | 2023/10/18 14:55:50 | 14:55:50,435 |-INFO in ch.qos.logback.classic.AsyncAppender[SysoutAsync] - Queue flush finished successfully within timeout.
INFO | jvm 1 | 2023/10/18 14:55:50 | 14:55:50,435 |-INFO in ch.qos.logback.classic.AsyncAppender[DBAsync] - Worker thread will flush remaining events before exiting.
INFO | jvm 1 | 2023/10/18 14:55:50 | 14:55:50,439 |-INFO in ch.qos.logback.classic.AsyncAppender[DBAsync] - Queue flush finished successfully within timeout.
STATUS | wrapper | 2023/10/18 14:55:53 | on_exit trigger matched. Restarting the JVM. (Exit code: 2)
STATUS | wrapper | 2023/10/18 14:55:58 | Reloading Wrapper configuration...
STATUS | wrapper | 2023/10/18 14:55:58 | Launching a JVM...
INFO | jvm 2 | 2023/10/18 14:55:59 | Error opening zip file or JAR manifest missing : d:\opt\appd\appagent\javaagent.jar
INFO | jvm 2 | 2023/10/18 14:55:59 | Error occurred during initialization of VM
INFO | jvm 2 | 2023/10/18 14:55:59 | agent library failed to init: instrument
ERROR | wrapper | 2023/10/18 14:55:59 | JVM exited while loading the application.
Not entirely sure what all this means.
I have attached an extract of the
Wrapper.log (20.1 KB)
from the point I initiated the restoration operation.
The problem is, the Wrapper logging just stopped...as such, I assume that this means that the GW has also stopped...if that's the case, the root cause of the issue aside for a moment, having not had to deal with such a situation previously, I'd also be at a loss as to the steps required to get it to attempt a re-initialisation.
Either way, many thanks for any advice anyone may have here!
Cheers!
Rob