I have a bizarre problem with yum; I can add packages without incident
with the following syntax:
package { "mod_perl": ensure => present, }
package { "mod_ssl": ensure => present, }
package { "perl-DBD-MySQL": ensure => present, }
Works fine, for most packages. However, the specific one in the middle
above, mod_ssl, fails:
zule[~]$ sudo puppetd --test
info: Loading fact subnet
info: Retrieving facts
info: Loading fact subnet
info: Caching catalog at /var/puppet/state/localconfig.yaml
notice: Starting catalog run
err: //Node[webserver]/web_server/Package[mod_ssl]/ensure: change from
absent to present failed: Could not find package mod_ssl
notice: Finished catalog run in 13.78 seconds
I can check to see that it''s available with yum list:
zule[~]$ sudo yum list mod_ssl
Available Packages
mod_ssl.x86_64
And I''m even passing dependency checks when I try a "yum
install"
zule[~]$ sudo yum install mod_ssl
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package mod_ssl.x86_64 1:2.2.10-2 set to be updated
--> Processing Dependency: libdistcache.so.1()(64bit) for package: mod_ssl
--> Processing Dependency: libnal.so.1()(64bit) for package: mod_ssl
--> Running transaction check
---> Package distcache.x86_64 0:1.4.5-17 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================================================================================
Package Arch
Version
Repository
Size
===============================================================================================================================Installing:
mod_ssl x86_64
1:2.2.10-2
fedora
86 k
Installing for dependencies:
distcache x86_64
1.4.5-17
fedora
123 k
Transaction Summary
===============================================================================================================================Install
2 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total size: 210 k
Is this ok [y/N]:
Explicitly specifying the architecture doesn''t help either:
zule[~]$ sudo puppetd --test
info: Loading fact subnet
info: Retrieving facts
info: Loading fact subnet
info: Caching catalog at /var/puppet/state/localconfig.yaml
notice: Starting catalog run
err: //Node[webserver]/web_server/Package[mod_ssl.x86_64]/ensure:
change from absent to present failed: Could not find package
mod_ssl.x86_64
notice: Finished catalog run in 14.14 seconds
I feel like I must be missing something simple, but since yum installs
are working all over the place, it seems really weird to me... has
anyone seen anything like this, or is there more info I can provide to
help figure this out?
Thanks,
Marti
--
Systems Programmer, Principal
Electrical & Computer Engineering
The University of Arizona
marti@arizona.edu
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
Marti Martinez wrote:> I have a bizarre problem with yum; I can add packages without incident > with the following syntax: > > package { "mod_perl": ensure => present, } > package { "mod_ssl": ensure => present, } > package { "perl-DBD-MySQL": ensure => present, } > > > Works fine, for most packages. However, the specific one in the middle > above, mod_ssl, fails: > > zule[~]$ sudo puppetd --test > info: Loading fact subnet > info: Retrieving facts > info: Loading fact subnet > info: Caching catalog at /var/puppet/state/localconfig.yaml > notice: Starting catalog run > err: //Node[webserver]/web_server/Package[mod_ssl]/ensure: change from > absent to present failed: Could not find package mod_ssl > notice: Finished catalog run in 13.78 seconds > > I can check to see that it''s available with yum list: > > zule[~]$ sudo yum list mod_ssl > Available Packages > mod_ssl.x86_64 > > And I''m even passing dependency checks when I try a "yum install" > > zule[~]$ sudo yum install mod_ssl > Setting up Install Process > Parsing package install arguments > Resolving Dependencies > --> Running transaction check > ---> Package mod_ssl.x86_64 1:2.2.10-2 set to be updated > --> Processing Dependency: libdistcache.so.1()(64bit) for package: mod_ssl > --> Processing Dependency: libnal.so.1()(64bit) for package: mod_ssl > --> Running transaction check > ---> Package distcache.x86_64 0:1.4.5-17 set to be updated > --> Finished Dependency Resolution > > Dependencies Resolved > > ===============================================================================================================================> Package Arch > Version > Repository > Size > ===============================================================================================================================> Installing: > mod_ssl x86_64 > 1:2.2.10-2 > fedora > 86 k > Installing for dependencies: > distcache x86_64 > 1.4.5-17 > fedora > 123 k > > Transaction Summary > ===============================================================================================================================> Install 2 Package(s) > Update 0 Package(s) > Remove 0 Package(s) > > Total size: 210 k > Is this ok [y/N]: > > Explicitly specifying the architecture doesn''t help either: > > zule[~]$ sudo puppetd --test > info: Loading fact subnet > info: Retrieving facts > info: Loading fact subnet > info: Caching catalog at /var/puppet/state/localconfig.yaml > notice: Starting catalog run > err: //Node[webserver]/web_server/Package[mod_ssl.x86_64]/ensure: > change from absent to present failed: Could not find package > mod_ssl.x86_64 > notice: Finished catalog run in 14.14 seconds > > > I feel like I must be missing something simple, but since yum installs > are working all over the place, it seems really weird to me... has > anyone seen anything like this, or is there more info I can provide to > help figure this out? > > Thanks, > Marti >I doubt this will have much impact, but try forcing the provider in the package block with provider => "yum" --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On Mar 9, 9:17 am, Joe McDonagh <joseph.e.mcdon...@gmail.com> wrote:> Marti Martinez wrote: > > I have a bizarre problem with yum; I can add packages without incident > > with the following syntax: > > > package { "mod_perl": ensure => present, } > > package { "mod_ssl": ensure => present, } > > package { "perl-DBD-MySQL": ensure => present, } > > > Works fine, for most packages. However, the specific one in the middle > > above, mod_ssl, fails: > > > zule[~]$ sudo puppetd --test > > info: Loading fact subnet > > info: Retrieving facts > > info: Loading fact subnet > > info: Caching catalog at /var/puppet/state/localconfig.yaml > > notice: Starting catalog run > > err: //Node[webserver]/web_server/Package[mod_ssl]/ensure: change from > > absent to present failed: Could not find package mod_ssl > > notice: Finished catalog run in 13.78 seconds > > > I can check to see that it''s available with yum list: > > > zule[~]$ sudo yum list mod_ssl > > Available Packages > > mod_ssl.x86_64 > > > And I''m even passing dependency checks when I try a "yum install" > > > zule[~]$ sudo yum install mod_ssl > > Setting up Install Process > > Parsing package install arguments > > Resolving Dependencies > > --> Running transaction check > > ---> Package mod_ssl.x86_64 1:2.2.10-2 set to be updated > > --> Processing Dependency: libdistcache.so.1()(64bit) for package: mod_ssl > > --> Processing Dependency: libnal.so.1()(64bit) for package: mod_ssl > > --> Running transaction check > > ---> Package distcache.x86_64 0:1.4.5-17 set to be updated > > --> Finished Dependency Resolution > > > Dependencies Resolved > > > =========================================================================== ====================================================> > Package Arch > > Version > > Repository > > Size > > =========================================================================== ====================================================> > Installing: > > mod_ssl x86_64 > > 1:2.2.10-2 > > fedora > > 86 k > > Installing for dependencies: > > distcache x86_64 > > 1.4.5-17 > > fedora > > 123 k > > > Transaction Summary > > =========================================================================== ====================================================> > Install 2 Package(s) > > Update 0 Package(s) > > Remove 0 Package(s) > > > Total size: 210 k > > Is this ok [y/N]: > > > Explicitly specifying the architecture doesn''t help either: > > > zule[~]$ sudo puppetd --test > > info: Loading fact subnet > > info: Retrieving facts > > info: Loading fact subnet > > info: Caching catalog at /var/puppet/state/localconfig.yaml > > notice: Starting catalog run > > err: //Node[webserver]/web_server/Package[mod_ssl.x86_64]/ensure: > > change from absent to present failed: Could not find package > > mod_ssl.x86_64 > > notice: Finished catalog run in 14.14 seconds > > > I feel like I must be missing something simple, but since yum installs > > are working all over the place, it seems really weird to me... has > > anyone seen anything like this, or is there more info I can provide to > > help figure this out? > > > Thanks, > > Marti > > I doubt this will have much impact, but try forcing the provider in the > package block with provider => "yum"Good thought, but no, it doesn''t change anything. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
This wasn''t a problem with yum or puppet (at least not directly) but with an inconsistency in the way that NFS automounts work on Solaris and Fedora... removing a funky NFS mount point fixed the problem -- anything trying to traverse the mount point (which rpm apparently does...!?) would segfault. I didn''t catch it because server B (which I ran ''yum install'' manually on) hadn''t yet accessed that automount, but server A had. Anyhow, thanks all, and sorry for a false alarm! On Mar 9, 9:30 am, Marti <martine...@gmail.com> wrote:> On Mar 9, 9:17 am, Joe McDonagh <joseph.e.mcdon...@gmail.com> wrote: > > > > > > > Marti Martinez wrote: > > > I have a bizarre problem with yum; I can add packages without incident > > > with the following syntax: > > > > package { "mod_perl": ensure => present, } > > > package { "mod_ssl": ensure => present, } > > > package { "perl-DBD-MySQL": ensure => present, } > > > > Works fine, for most packages. However, the specific one in the middle > > > above, mod_ssl, fails: > > > > zule[~]$ sudo puppetd --test > > > info: Loading fact subnet > > > info: Retrieving facts > > > info: Loading fact subnet > > > info: Caching catalog at /var/puppet/state/localconfig.yaml > > > notice: Starting catalog run > > > err: //Node[webserver]/web_server/Package[mod_ssl]/ensure: change from > > > absent to present failed: Could not find package mod_ssl > > > notice: Finished catalog run in 13.78 seconds > > > > I can check to see that it''s available with yum list: > > > > zule[~]$ sudo yum list mod_ssl > > > Available Packages > > > mod_ssl.x86_64 > > > > And I''m even passing dependency checks when I try a "yum install" > > > > zule[~]$ sudo yum install mod_ssl > > > Setting up Install Process > > > Parsing package install arguments > > > Resolving Dependencies > > > --> Running transaction check > > > ---> Package mod_ssl.x86_64 1:2.2.10-2 set to be updated > > > --> Processing Dependency: libdistcache.so.1()(64bit) for package: mod_ssl > > > --> Processing Dependency: libnal.so.1()(64bit) for package: mod_ssl > > > --> Running transaction check > > > ---> Package distcache.x86_64 0:1.4.5-17 set to be updated > > > --> Finished Dependency Resolution > > > > Dependencies Resolved > > > > =========================================================================== ====================================================> > > Package Arch > > > Version > > > Repository > > > Size > > > =========================================================================== ====================================================> > > Installing: > > > mod_ssl x86_64 > > > 1:2.2.10-2 > > > fedora > > > 86 k > > > Installing for dependencies: > > > distcache x86_64 > > > 1.4.5-17 > > > fedora > > > 123 k > > > > Transaction Summary > > > =========================================================================== ====================================================> > > Install 2 Package(s) > > > Update 0 Package(s) > > > Remove 0 Package(s) > > > > Total size: 210 k > > > Is this ok [y/N]: > > > > Explicitly specifying the architecture doesn''t help either: > > > > zule[~]$ sudo puppetd --test > > > info: Loading fact subnet > > > info: Retrieving facts > > > info: Loading fact subnet > > > info: Caching catalog at /var/puppet/state/localconfig.yaml > > > notice: Starting catalog run > > > err: //Node[webserver]/web_server/Package[mod_ssl.x86_64]/ensure: > > > change from absent to present failed: Could not find package > > > mod_ssl.x86_64 > > > notice: Finished catalog run in 14.14 seconds > > > > I feel like I must be missing something simple, but since yum installs > > > are working all over the place, it seems really weird to me... has > > > anyone seen anything like this, or is there more info I can provide to > > > help figure this out? > > > > Thanks, > > > Marti > > > I doubt this will have much impact, but try forcing the provider in the > > package block with provider => "yum" > > Good thought, but no, it doesn''t change anything.--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Marti wrote:> anything trying to traverse the mount point (which rpm apparently > does...!?)Rpm does a statvfs() call on all mount points, to check how much free space there is in the file systems. It then compares that with how much space the package being installed requires in different places. This is done so there will be less chance of encountering an out of space condition after it has begun to actually install files into the filesystem(s). It would be nice if the rpm command was smarter about which mountpoints it actually calls statvfs() on. /Thomas Bellman --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---