Did you do a ps -ef | grep yum? It tells you the pid. I wouldn't kill it. Let it finish its other work. If the pid isn't present, remove the pid-file and retry. If that fails, you have some serious troubleshooting to do tracing the process, googling the web for the error message, and other drill-down.
On Sep 3, 2013, at 11:41 AM, Glenn Poston <[email protected]> wrote: > Any ideas??? > > On Friday, June 28, 2013 9:38:29 AM UTC-4, Glenn Poston wrote: > Running Amazon Linux (which is essentially Centos5.5). > > Anyone seen random yum errors like this one? I don't think it's necessarily > related to Puppet, but it randomly fails my puppet runs and I don't know how > to fix it. > > Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice: > /Stage[main]/Zookeeper/Package[zookeeper]/ensure: created > Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice: > /Stage[main]/Zookeeper/File[/var/lib/zookeeper/data]/ensure: created > Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice: > /Stage[main]/Zookeeper/File[/var/lib/zookeeper/data/myid]/ensure: created > Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice: > /Stage[main]/Yum_repo::Configs/File[/etc/yum.repos.d/inin-epel.repo]/ensure: > defined content as '{md5}b94171f63e31f07b8bd75444073e301c' > Jun 28 08:41:35 ip-10-159-65-145 run_puppet: [Notice: > /Stage[main]/Zookeeper/File[/etc/zookeeper/zookeeper-env.sh]/content: content > changed '{md5}cd666c7520ce5279ddbc185512b0b177' to > '{md5}5cb59b25f5e7567d94ba14b06f6e7081' > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error: Execution of > '/usr/bin/yum -d 0 -e 0 -y install daemonize' returned 1: Existing lock > /var/run/yum.pid: another copy is running as pid 2502. > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently holding > the yum lock; waiting for it to exit... > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB > VSZ) > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28 08:41:33 > 2013 - 00:03 ago > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502 > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is > malformed > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error: > /Stage[main]/Mcollective/Package[daemonize]/ensure: change from absent to > present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install daemonize' > returned 1: Existing lock /var/run/yum.pid: another copy is running as pid > 2502. > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently holding > the yum lock; waiting for it to exit... > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB > VSZ) > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28 08:41:33 > 2013 - 00:03 ago > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502 > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is > malformed > Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [mNotice: > /Stage[main]/Zookeeper/File[/etc/zookeeper/zoo.cfg]/content: content changed > '{md5}5c543298c5572c3caf40a3d108309019' to > '{md5}31db609f6601a8a02561d411e98db12b' > Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice: > /Stage[main]/Puppet/File[/usr/local/bin/run_puppet.sh]/content: content > changed '{md5}4e9496313a0b4152c663defce5100af5' to > '{md5}49d78e473fa2202dea13e9b195e63575' > Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice: > /Stage[main]/Yum_repo::Configs/Exec[puppet_repo]/returns: executed > successfully > Jun 28 08:41:48 ip-10-159-65-145 run_puppet: [mNotice: > /Stage[main]/Mcollective::Common/Package[mcollective-package-agent]/ensure: > created > > The problem does not persist. Yum packages are installed by puppet before > and after the errors. A subsequent puppet run installs the previously > skipped packages fine. > > It's as if some background process creates a lock, while updating the yum DB, > but when the lock is released, the yum DB is still in a bad state > (momentarily). > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" 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-users. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users. For more options, visit https://groups.google.com/groups/opt_out.
