The 4158 second catalog run.

Kris Buytaert — Wed, 20 Apr 2011 20:36:03 +0000

Two of my tweets , sorry dents, earlier today caused some people to ask me what on earth I was doing :)

You don't exist, go away!

Was the first one, indeed .. it was a long time since I had actually seen that one.. this actually happens when you delete the user you are logged in with on a host, when the host notices you don't exist anymore it will tell you.

Now that is exactly what happend .. We were busy reordening the uid's on some hosts , so I modified the puppet config for that host and changed the uid values, a couple of minutes later I was told that I don't exist ..

The last time I saw that , was about 10 years ago when I was trying to fool some collegues :)

Now the second tweet that tracked some people's attention was the one about a very lengthy catalog run

Apr 20 05:12:42 sipx-a puppet-agent[22384]: Finished catalog run in 4158.09 seconds

Indeed, a puppet catalog run of about 69 minutes, yes thats 1 hour and 9 minutes ..

The reason for this lengthy catalog run was the above uid reordering , combined with

       "/var/sipxdata/":
                        owner => "sipxchange", group => "sipxchange",
                        recurse => true,
                        ensure => directory;

And about 5K files in that directory .. apparently recurse doesn't translate to chown -R yet :)

Everything is a Freaking DNS problem - uid

The 4158 second catalog run.