Ignition 8.3 service stopping suddenly

Ignition
1

Hey guys!

We’re getting ready to deploy our Ignition system into production. However, these past few weeks there have been times when the Ignition service suddenly stops and we have to manually restart.

We checked the logs, but there doesn’t seem to be a log related to why it suddenly shut down.

We set up our VMs specs to fit with IAs recommended specs, but it might not be enough?

Our current guess is that it is related to the amount of resources being consumed by Ignition. Ever since we have upgraded to 8.3, we noticed that Zulu java is constantly consuming more and more memory. But this is just a guess.

We saw a post discussing about limiting the amount of memory that is allowed to be allocated by Zulu, but I don’t know if that will make the service even more unstable.

Wanted to know if anyone else has experienced anything similar or have anymore ideas on how we can debug. Thanks in advance!

2

What does your gateway memory trend look like? Is it normal saw tooth or does it just steadily increase until the service ends up stopping? How much memory does your VM have? How much memory do you have Ignition allocate?

Your initial and maximum heap settings should be the same value in your config file, and your max heap value should be less than the total memory for your vm. You'll need to leave some memory free for OS overhead.

1 Like