Ask Your Question

Execs keeps running after puppet run failed

asked 2014-02-12 06:36:18 -0500

onitlikesonic gravatar image

It has happened to me some times already, puppet run completes with errors and apt gets locked due to "zombie" processes still running...

exec { "purge-apparmor":
      command => "apt-get purge ${apparmor::params::apparmor_package_name}",

err: /Stage[main]/Apparmor::Install/Exec[purge-apparmor]/returns: change from notrun to 0 failed: apt-get purge -y apparmor returned 100 instead of one of [0] at /etc/puppet/environments/development/modules/apparmor/manifests/install.pp:40

# apt-get purge apparmor
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

# ps ...
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-02-13 13:10:36 -0500

Stefan gravatar image

My first idea was the timeout parameter but if you'd hit a timeout the error message would be different. Are you absolutely sure that puppet is causing these zombie processes and it is not the other way around: There already is this apt-get zombie before you run puppet and when puppet tries to run it, it fails with returncode 100 because there was an already running apt-get process?

The thing that apt-get gets executed as sh -c /bin/sh -c "apt-get pruge apparmor" doesn't really look like a command that puppet would execute.

edit flag offensive delete link more


it's surely a puppet command, I've placed it above in the original question on that exec...

onitlikesonic gravatar imageonitlikesonic ( 2014-02-14 06:22:18 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2014-02-12 06:36:18 -0500

Seen: 252 times

Last updated: Feb 13 '14