# \[BUG-11343\] Unable to start designer on Ubuntu 16.04

**URL:** <https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675>\
**Category:** Ignition Early Access\
**Created:** [November 8, 2018, 5:35pm UTC](https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675 "2018-11-08T17:35:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidf](https://avatars.discourse-cdn.com/v4/letter/d/f07891/32.png) [@davidf](https://forum.inductiveautomation.com/u/davidf)\
**Post date:** [November 8, 2018, 5:35pm UTC](https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675/1 "2018-11-08T17:35:05Z")

</div>

After installing nightly build from 11/08/2018 onto an Ubuntu VM, the gateway fails to launch.

Host OS: Linux 4.4.0-81-generic #104-Ubuntu SMP x86\_64 GNU/Linux

Java version: jdk1.8.0\_121

The error in the wrapper log is:  
STATUS | wrapper | 2018/11/08 17:25:20 | Launching a JVM…  
ERROR | wrapper | 2018/11/08 17:25:20 | JVM exited while loading the application.  
INFO | jvm 5 | 2018/11/08 17:25:20 | Unrecognized VM option ‘PrintGCDateStamps’  
INFO | jvm 5 | 2018/11/08 17:25:20 | Error: Could not create the Java Virtual Machine.  
INFO | jvm 5 | 2018/11/08 17:25:20 | Error: A fatal exception has occurred. Program will exit.  
FATAL | wrapper | 2018/11/08 17:25:20 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.  
FATAL | wrapper | 2018/11/08 17:25:20 | There may be a configuration problem: please check the logs.  
STATUS | wrapper | 2018/11/08 17:25:20 | \<-- Wrapper Stopped

I will try to upgrade Java, but was wondering if there is a version requirement? I did not see it on the beta installation page.

---

<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:** [November 8, 2018, 5:37pm UTC](https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675/2 "2018-11-08T17:37:06Z")

</div>

> [@davidf](#):
>
> INFO | jvm 5 | 2018/11/08 17:25:20 | Unrecognized VM option 'PrintGCDateStamps'

You need to update the ignition.conf to remove the `PrintGCDateStamps` argument that was added at some point - it's not supported by Java 11. I've also updated the auto-upgrade logic to remove this argument automatically; that fix will go into a future build to prevent this from happening again.

---

<div class="post-metadata">

**Author:** ![davidf](https://avatars.discourse-cdn.com/v4/letter/d/f07891/32.png) [@davidf](https://forum.inductiveautomation.com/u/davidf)\
**Post date:** [November 8, 2018, 5:48pm UTC](https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675/3 "2018-11-08T17:48:23Z")

</div>

Thanks, I also had to disable several other options, see the comment lines below. I am not sure if UseG1GC was disabled before but the others I had to disable. Normally we use G1GC on our gateways as well.

#wrapper.java.additional.1=-XX:+UseG1GC  
wrapper.java.additional.3=-Ddata.dir=/var/lib/ignition/data  
wrapper.java.additional.4=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE\_CLEAR\_REFERENCES=false  
wrapper.java.additional.7=-Dignition.allowunsignedmodules=true  
wrapper.java.additional.8=-Dignition.tags.scriptthreads=30  
wrapper.java.additional.9=-XX:+PrintGCDetails

# wrapper.java.additional.10=-XX:+PrintGCDateStamps

# wrapper.java.additional.11=-Xloggc:/var/log/ignition/gclog.txt

# wrapper.java.additional.12=-XX:+UseGCLogFileRotation

# wrapper.java.additional.13=-XX:NumberOfGCLogFiles=5

# wrapper.java.additional.14=-XX:GCLogFileSize=10M

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [December 7, 2018, 12:40am UTC](https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675/4 "2018-12-07T00:40:23Z")

</div>

This issue was fixed in the build that was uploaded on 11/10. Please let us know if you continue to see this behavior after upgrading.

---

<div class="post-metadata">

**Author:** ![davidf](https://avatars.discourse-cdn.com/v4/letter/d/f07891/32.png) [@davidf](https://forum.inductiveautomation.com/u/davidf)\
**Post date:** [December 12, 2018, 6:56pm UTC](https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675/5 "2018-12-12T18:56:42Z")

</div>

I saw this same error after upgrading to yesterday’s nightly build.

---

<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:** [December 12, 2018, 9:24pm UTC](https://forum.inductiveautomation.com/t/bug-11343-unable-to-start-designer-on-ubuntu-16-04/20675/6 "2018-12-12T21:24:47Z")

</div>

@davidf  
Can you post a wrapper.log file from a failed start? Also, if possible, could you remove Ignition altogether, then do a “clean” install of the nightly, then restore the .gwbk from your existing system? If that still fails, could you also upload/PM me your ignition.conf file from the system in the .gwbk?
