I''m getting this on my client:
Jun 14 15:21:26 s_sys@app09.fr.xxx.com puppetd[24751]: Could not
retrieve catalog: stack level too deep on node app09.fr.twofish.com
Jun 14 15:21:26 s_sys@app09.fr.xxx.com puppetd[24751]: Not using cache
on failed catalog
Since running puppetd in debug gives no useful info:
info: Starting handler for Runner
info: Starting server for Puppet version 0.24.8
info: Listening on port 8139
notice: Starting Puppet client version 0.24.8
debug: Loaded state in 0.02 seconds
debug: Retrieved facts in 0.48 seconds
debug: Retrieving catalog
debug: Calling puppetmaster.getconfig
err: Could not retrieve catalog: stack level too deep on node app09.fr.xxx.com
warning: Not using cache on failed catalog
... I started to cut my node manifest down to it''s barest essentials.
This is what I currently have:
---
classes:
- server_role::baseNode
environment: production
parameters:
and the server_role::baseNode class has this:
class server_role::baseNode {
}
In a word... What the hell? This was previously working and I''m at a
loss as to why including ONE class in my external node manifest is
yielding a stack too deep error.
Doug.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1> In a word... What the hell? This was previously working and I''m at a > loss as to why including ONE class in my external node manifest is > yielding a stack too deep error.I doubt that this is related to your manifests. Can you run your server and client with --verbose and --debug so we can see where you end up in an endless loop? cheers pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwWvpMACgkQbwltcAfKi397iQCgtlyFqT8Gr16hUUtrUp3K4vv4 J1EAn31kgWerXwsBTXE55gwx9kfIdiM8 =s8hN -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Peter Meier wrote:>> In a word... What the hell? This was previously working and I''m at a >> loss as to why including ONE class in my external node manifest is >> yielding a stack too deep error. > > I doubt that this is related to your manifests. Can you run your server > and client with --verbose and --debug so we can see where you end up in > an endless loop?And add --trace too will help. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Possibly Parallel Threads
- Upgrading Samba 3 to Samba 4 - Domain Controller unreachable
- [PATCH v2 2/7] New API: setfiles - SELinux relabel parts of the filesystem.
- Help me understand class namespacing
- Is sshkey host_aliases new in 0.25?
- Upgraded > Samba no longer listening on 192.168.0.x