In an effort to figure out what might be causing the scheduling problem I tried doing a fresh install:
r...@wrath ~# ruby --version ruby 1.8.7 (2008-05-31 patchlevel 0) [i386-solaris2.10] r...@wrath ~# puppet --version 0.24.7 r...@wrath ~# facter --version 1.5.3 r...@wrath ~# uname -a SunOS wrath 5.10 Generic_138889-03 i86pc i386 i86pc And now there's a new and exciting problem. It seems that puppetd is no longer able to execute external commands (e.g., svcs, crontab). The debug output looks like it's running the right stuff, e.g.: debug: Puppet::Type::Service::ProviderSmf: Executing '/usr/bin/svcs -l sma' wrong number of arguments (2 for 1) warning: Service[sma](provider=smf): Could not get status on service sma But clearly whatever in Ruby is returning this "wrong number of arguments (2 for 1)" error is blocking the execution of svcs (and crontab). The only bright spot is that the schedule issue doesn't *seem* to be recurring, but that's not very useful if puppetd can't actually run anything. I was previously using: ruby 1.8.7 (2008-04-26 patchlevel 5000) [i386-solaris2.10] which was the current pre-release when I originally did the Puppet installs. I used that because the stable release broke Puppet in some other exciting way I can no longer recall... Matt -- * Matt McLeod | mail: m...@boggle.org | blog: http://abortrephrase.com/ * --- People can do the work, so machines have time to think --- --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
