Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have setup stored configuration primarily as a method to manage my ssh known_hosts. Unfortunately as I retire hosts the old configs still exist in my database. The answer seems to be run the command puppet node clean <hostname>.

The problem is that while this does command does run, and does clean up some data, it doesn't seem to clean up everything.

For example I can still find values in the puppet_tags table that only applied to a hosts that no longer exists.

What should I be doing to keep my stored configuration database clean of all extra junk that seems to be building up?

P.S. Can anyone point me any documentation for the stored configuration schema?  If I could find good documentation, or at least an entity-relationship-diagram, I would be tempted to just do some manual clean-up.

share|improve this question
The requirements of this question are not specific. What are all of the tables/fields that have extra data building up? – Barry Oct 21 '12 at 8:42
up vote 2 down vote accepted

Storedconfigs are stored as activerecord models.

Here's the schema:

If you really want an ER diagram, it can be extracted from the source with something like

share|improve this answer
This is useful, and I am awarding the bounty since it would be lost other wise. I am not going to mark this as accepted though since it doesn't really answer the core question about cleaning up some of the extra cruft. – Zoredache Oct 18 '12 at 20:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.