Issue #21655 has been updated by Josh Cooper.

Status changed from Needs More Information to Duplicate

In puppet 3.3.1, a malformed state.yaml file will not prevent the agent from 
being able to run. See #22471

----------------------------------------
Bug #21655: on Windows: Puppet agent can't start: error "could not find 
expected ':' while scanning a simple key at line 60 column 3
https://projects.puppetlabs.com/issues/21655#change-97696

* Author: Eric Veiras Galisson
* Status: Duplicate
* Priority: Normal
* Assignee: Tristan Helmich
* Category: windows
* Target version: 
* Affected Puppet version: 3.2.2
* Keywords: windows, agent
* Branch: 
----------------------------------------
Hello,

I'm testing Puppet 3.2.2 on a Windows Server 2008 R2 64 bits. The server is 
3.2.2 too on Debian stable.
Yesterday, I was able to push some manifests to my Windows Server, creating 
users and managing groups.
Since then, (but can't remember what changes i did), Puppet Agent don't start.

The following error appears in the event log, or when running from command line:

  Could not run Puppet configuration client: (<unknown>): could not find 
expected ':' while scanning a simple key at line 60 column 3
  Could not run: can't convert Puppet::Util::Log into Integer


Even removing all manifests for the node, or removing the node completely on 
the puppet master, the problem persists.

 Do you have any idea of what can be this problem?


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to