Bug 1601462 - systemctl status puppetserver shows warning.
Summary: systemctl status puppetserver shows warning.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.3.2
Hardware: All
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-16 12:38 UTC by Martijn ten Heuvel
Modified: 2019-06-03 15:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-03 17:11:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24289 0 Normal Rejected OpenJDK shows warning on puppetserver after installation 2020-10-04 16:08:29 UTC

Description Martijn ten Heuvel 2018-07-16 12:38:05 UTC
Description of problem:
OpenJDK configuration gives error when not expected.


Version-Release number of selected component (if applicable):
6.3.2

How reproducible:
upgraded to puppet4, running puppetserver process.

Steps to Reproduce:
1. upgrade to 6.3.2
2. migrate to puppet4
3. restart puppetserver process

Actual results:
[root@satellite62 ~]# systemctl status puppetserver -l
● puppetserver.service - puppetserver Service
   Loaded: loaded (/usr/lib/systemd/system/puppetserver.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2018-07-16 14:34:18 CEST; 1min 0s ago
  Process: 1194 ExecStart=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver start (code=exited, status=0/SUCCESS)
 Main PID: 1293 (java)
   CGroup: /system.slice/puppetserver.service
           └─1293 /usr/bin/java -Xms2G -Xmx2G -XX:MaxPermSize=256m -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar clojure.main -m puppetlabs.trapperkeeper.main --config /etc/puppetlabs/puppetserver/conf.d --bootstrap-config /etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/ --restart-file /opt/puppetlabs/server/data/puppetserver/restartcounter

Jul 16 14:32:11 satellite62.mobile.mth systemd[1]: Starting puppetserver Service...
Jul 16 14:32:12 satellite62.mobile.mth puppetserver[1194]: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Jul 16 14:34:18 satellite62.mobile.mth systemd[1]: Started puppetserver Service.


Expected results:
[root@satellite62 ~]# systemctl status puppetserver -l
● puppetserver.service - puppetserver Service
   Loaded: loaded (/usr/lib/systemd/system/puppetserver.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2018-07-16 14:34:18 CEST; 1min 0s ago
  Process: 1194 ExecStart=/opt/puppetlabs/server/apps/puppetserver/bin/puppetserver start (code=exited, status=0/SUCCESS)
 Main PID: 1293 (java)
   CGroup: /system.slice/puppetserver.service
           └─1293 /usr/bin/java -Xms2G -Xmx2G -XX:MaxPermSize=256m -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp /opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar clojure.main -m puppetlabs.trapperkeeper.main --config /etc/puppetlabs/puppetserver/conf.d --bootstrap-config /etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/ --restart-file /opt/puppetlabs/server/data/puppetserver/restartcounter

Jul 16 14:32:11 satellite62.mobile.mth systemd[1]: Starting puppetserver Service...
Jul 16 14:34:18 satellite62.mobile.mth systemd[1]: Started puppetserver Service.

Additional info:
Please see diff of the output.

Comment 2 Daniel Lobato Garcia 2018-07-18 15:25:12 UTC
I'm seeing this warning too, copying to upstream and setting as triaged.

Comment 3 Daniel Lobato Garcia 2018-07-18 15:27:06 UTC
Created redmine issue https://projects.theforeman.org/issues/24289 from this bug

Comment 4 Ewoud Kohl van Wijngaarden 2018-07-18 15:43:59 UTC
This can be removed with --puppet-server-jvm-extra-args ''

Future upstream versions already do this automatically when Puppet 5 is detected because it requires JRE 8. With Puppet 4 you can still run with JRE 7 so we don't autodetect this.

Comment 5 Bryan Kearney 2018-08-03 17:11:32 UTC
I am closing this out as WONTFIX based on https://bugzilla.redhat.com/show_bug.cgi?id=1601462#c4.


Note You need to log in before you can comment on or make changes to this bug.