Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1635

Stray output from "puppetserver start" command

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: SERVER 2.7.0
    • Fix Version/s: None
    • Component/s: Puppet Server
    • Labels:
    • Template:
    • Acceptance Criteria:
      • Warning output from puppetserver start goes into /var/log/mumble

      Description

      The puppetserver start command allows a warning message through to the CLI that should be sent to a log file somewhere. On a CentOS 6.5 system running Puppet Server (FOSS) 2.6.1.master.SNAPSHOT.2016.11.04T2126 and Puppet 4.8.1:

      # puppetserver --version
      puppetserver version: 2.6.1.master.SNAPSHOT.2016.11.04T2126
      # puppetserver start
      OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
      service puppetserver status
      # service puppetserver status
      puppetserver (pid  16743) is running...
      

      Seems like that OpenJDK warning should go to /var/log/mumble.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kurt.wall Kurt Wall
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support