The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #3313

puppet.conf option client=true/false doesn't seem to work

Added by christian c over 4 years ago. Updated over 2 years ago.

Status:DuplicateStart date:03/01/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:plumbing
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

Hi, I’m using puppet 0.25.4 on OpenSuse 11.1.

Trying to run puppet as listening client only with “listen=true” and “client=false” options in puppet.conf doesn’t seem to work. After restarting puppet with the new configuration, first thing it does is polling the puppetmaster and afterwards every 30min.

But if I start puppetd with —no-client parameter it polls the puppetmaster only after being triggered by a puppetrun-command coming from the master.

Additionally, if the option works again, you should add it to the configuration reference because right now it isn’t mentioned.

My config: [puppetd]

    classfile = $vardir/classes.txt
    server = puppet
    localconfig = $vardir/localconfigi
    httplog  = $logdir/http.log
    listen = true
    noop = false
    client = false
    puppetdlog = $logdir/puppetd.log
    puppetport = 8139
    pluginsync = true

Related issues

Duplicates Puppet - Bug #8917: `client` is not a configuration option, and --client/--no... Code Insufficient 08/10/2011

History

#1 Updated by Matt Moran over 4 years ago

This also happens on CentOS 5, also with version 0.25.1 as well as 0.25.4

#2 Updated by James Turnbull over 4 years ago

  • Category set to plumbing
  • Status changed from Unreviewed to Accepted
  • Assignee set to Jesse Wolfe

#3 Updated by Matt Chesler about 4 years ago

I’m experiencing this same issue with CentOS 5, Puppet version 2.6.0. The workaround that I’ve found is to add “PUPPET_EXTRA_OPTS=—no-client” to /etc/sysconfig/puppet and restart the puppet agent.

#4 Updated by Anonymous almost 3 years ago

  • Assignee deleted (Jesse Wolfe)

This issue was assigned to a former Puppet Labs employee. Adding back to the pool of unreviewed issues.

#5 Updated by Ben Hughes almost 3 years ago

  • Description updated (diff)
  • Status changed from Accepted to Unreviewed

#6 Updated by Luke Kanies over 2 years ago

  • Description updated (diff)
  • Status changed from Unreviewed to Duplicate

Rejecting in favor of #8917.

Also available in: Atom PDF