Hi, We have majority of RHEL5 servers in our environment. I have noticed in the process of trying to deploy puppet, that i am getting errors when yum is trying to install packages. Most of the time it works flawlessly, however sometime the following will be reported: change from absent to present failed: Execution of ''/usr/bin/yum -d 0 - e 0 -y install modcluster'' returned 1: This system is not registered with RHN. RHN support will be disabled. Error Downloading Packages: modcluster-0.12.1-2.el5.x86_64: failure: modcluster-0.12.1-2.el5.x86_64.rpm from core-1: [Errno 256] No more mirrors to try. The only way to correct the issue is to run "yum clean all" on the client and then rerun the puppet catalogue. Does anyone have any information as to what is going wrong here? Or what can be done to stop this from happening. The repo''s i am using are local mirrors I have configured for our company. Cheers, Josh --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
2009/7/29 josbal <joshua.baldock@gmail.com>:> > Hi, > > We have majority of RHEL5 servers in our environment. I have noticed > in the process of trying to deploy puppet, that i am getting errors > when yum is trying to install packages. Most of the time it works > flawlessly, however sometime the following will be reported: > > change from absent to present failed: Execution of ''/usr/bin/yum -d 0 - > e 0 -y install modcluster'' returned 1: This system is not registered > with RHN. RHN support will be disabled. Error Downloading > Packages: modcluster-0.12.1-2.el5.x86_64: failure: > modcluster-0.12.1-2.el5.x86_64.rpm from core-1: [Errno 256] No more > mirrors to try.This is unlikely to be a puppet issue. You are most likely to be hitting an issue in your yum configuration with metadata_expire being to high. metadata_expire Time (in seconds) after which the metadata will expire. So that if the current metadata downloaded is less than this many sec- onds old then yum will not update the metadata against the repository. If you find that yum is not downloading information on updates as often as you would like lower the value of this option. If say you are updating a package in the repo (and removing the old) and it''s less than metadata_expire your yum client may be looking for the old removed package. Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Hello,> We have majority of RHEL5 servers in our environment. I have noticed > in the process of trying to deploy puppet, that i am getting errors > when yum is trying to install packages. Most of the time it works > flawlessly, however sometime the following will be reported: > [...] > Does anyone have any information as to what is going wrong here? Or > what can be done to stop this from happening. The repo''s i am using > are local mirrors I have configured for our company.If you''re not using redhat-network. It''s probably an idea to put: [main] enabled = 0 in your /etc/yum/pluginconf.d/rhnplugin.conf The only fact that yum won''t try to log into RHN each time it gets run might be enough to solve your issue. Marc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Thanks guys. I will give both your suggestions a try and see how i get on. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
josbal <joshua.baldock <at> gmail.com> writes:> > > Thanks guys. I will give both your suggestions a try and see how i get > on. > --~--~---------~--~----~------------~-------~--~----~ > 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 <at> googlegroups.com > To unsubscribe from this group, send email to puppet-users+unsubscribe <at>googlegroups.com> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en> -~----------~----~----~----~------~----~------~--~--- > >I''m getting the same error message while installing via puppet. It works fine if I pull all package information via yum or try to download the package manually. - JM -- 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.