Bug #16126
Updated by François ARMAND over 4 years ago
With openjdk-9-jdk-headless:amd64 9~b114-0ubuntu1 , one CPU, the webapp get stuck at start
=> workaround: use 2 CPU for rudder, as specified in doc https://docs.rudder.io/reference/5.0/installation/requirements.html#_cpu
Rudder-jetty init script states that it doesn't start.
Last log is
<pre>
file:/var/rudder/tmp/jetty/jetty-rudder.war.dir/webapp/WEB-INF/lib/unboundid-ldapsdk-4.0.7.jar
file:/var/rudder/tmp/jetty/jetty-rudder.war.dir/webapp/WEB-INF/lib/lift-common_2.12-3.3.0.jar
[2019-11-05 23:24:18+0100] INFO org.reflections.Reflections - Reflections took 132 ms to scan 110 urls, producing 0 keys and 0 values
INFO Configure inventory processing with parallelism of '1' and queue size of '50'
[2019-11-05 23:24:18+0100] INFO inventory-processing - Incoming inventory watcher started - process existing inventories
[2019-11-05 23:24:24+0100] DEBUG com.normation.rudder.services.reports.NodeChangesServiceImpl - Get all changes on all rules
[2019-11-05 23:24:24+0100] DEBUG com.normation.rudder.repository.jdbc.ReportsJdbcRepository - Fetching all changes for intervals 2019-11-02T18:00:00.000+01:00/2019-11-03T00:00:00.000+01:00,2019-11-03T00:00:00.000+01:00/2019-11-03T06:00:00.000+01:00,2019-11-03T06:00:00.000+01:00/2019-11-03T12:00:00.000+01:00,2019-11-03T12:00:00.000+01:00/2019-11-03T18:00:00.000+01:00,2019-11-03T18:00:00.000+01:00/2019-11-04T00:00:00.000+01:00,2019-11-04T00:00:00.000+01:00/2019-11-04T06:00:00.000+01:00,2019-11-04T06:00:00.000+01:00/2019-11-04T12:00:00.000+01:00,2019-11-04T12:00:00.000+01:00/2019-11-04T18:00:00.000+01:00,2019-11-04T18:00:00.000+01:00/2019-11-05T00:00:00.000+01:00,2019-11-05T00:00:00.000+01:00/2019-11-05T06:00:00.000+01:00,2019-11-05T06:00:00.000+01:00/2019-11-05T12:00:00.000+01:00,2019-11-05T12:00:00.000+01:00/2019-11-05T18:00:00.000+01:00,2019-11-05T18:00:00.000+01:00/2019-11-06T00:00:00.000+01:00
</pre>
May be related to https://issues.rudder.io/issues/16004