Red Hat Bugzilla – Bug 885787
Wallaby agent exception while running in memory
Last modified: 2013-03-06 13:47:41 EST
Description of problem: Running wallaby-agent on foreground (in memory) ends up with error: # wallaby-agent -f storing results to :memory: storing snapshots to :memory: creating user tables creating table for Mrg::Grid::Config::Feature... creating table for Mrg::Grid::Config::Group... creating table for Mrg::Grid::Config::Parameter... creating table for Mrg::Grid::Config::Subsystem... creating table for Mrg::Grid::Config::Node... creating table for Mrg::Grid::Config::ArcLabel... creating table for Mrg::Grid::Config::ParameterArc... creating table for Mrg::Grid::Config::FeatureArc... creating table for Mrg::Grid::Config::FeatureParams... creating table for Mrg::Grid::Config::NodeMembership... creating table for Mrg::Grid::Config::GroupParams... creating table for Mrg::Grid::Config::GroupFeatures... creating table for Mrg::Grid::Config::SubsystemParams... creating table for Mrg::Grid::Config::DirtyElement... creating snapshot tables checking for necessary user database migrations.... checking for necessary default database migrations.... agent exiting with exception #<Errno::ENOENT: No such file or directory - :memory:> /usr/lib/ruby/1.8/fileutils.rb:1207:in `stat' /usr/lib/ruby/1.8/fileutils.rb:1207:in `lstat' /usr/lib/ruby/1.8/fileutils.rb:1185:in `stat' /usr/lib/ruby/1.8/fileutils.rb:1267:in `copy_file' /usr/lib/ruby/1.8/fileutils.rb:464:in `copy_file' /usr/lib/ruby/1.8/fileutils.rb:383:in `cp' /usr/lib/ruby/1.8/fileutils.rb:1402:in `fu_each_src_dest' /usr/lib/ruby/1.8/fileutils.rb:1418:in `fu_each_src_dest0' /usr/lib/ruby/1.8/fileutils.rb:1400:in `fu_each_src_dest' /usr/lib/ruby/1.8/fileutils.rb:382:in `cp' /usr/bin/wallaby-agent:261 /usr/lib/ruby/site_ruby/1.8/sqlite3/database.rb:564:in `transaction' /usr/bin/wallaby-agent:256 /usr/lib/ruby/site_ruby/1.8/mrg/grid/config/dbmeta.rb:71:in `migrate' /usr/bin/wallaby-agent:255 /usr/bin/wallaby-agent:248:in `each' /usr/bin/wallaby-agent:248 Version-Release number of selected component (if applicable): wallaby-utils-0.16.1-2.el6.noarch wallaby-0.16.1-2.el6.noarch condor-wallaby-base-db-1.25-1.el6_3.noarch python-wallabyclient-5.0.4-1.el6_3.noarch ruby-condor-wallaby-tools-5.0.2-1.el6.noarch ruby-condor-wallaby-5.0.4-1.el6_3.noarch condor-wallaby-client-5.0.4-1.el6_3.noarch ruby-wallaby-0.16.1-2.el6.noarch condor-wallaby-tools-5.0.4-1.el6_3.noarch How reproducible: 100% Steps to Reproduce: 1. run wallaby-agent on foreground (-f parameter) Actual results: wallaby agent won't run in memory Expected results: wallaby agent will be working
Note that the -f parameter has nothing to do with this behavior; rather, the issue is that we're running with db tables in memory instead of in a file.
Successfully reproduced on wallaby-0.16.0-9 # wallaby-agent -f storing results to :memory: storing snapshots to :memory: creating user tables creating table for Mrg::Grid::Config::Feature... creating table for Mrg::Grid::Config::Group... creating table for Mrg::Grid::Config::Parameter... creating table for Mrg::Grid::Config::Subsystem... creating table for Mrg::Grid::Config::Node... creating table for Mrg::Grid::Config::ArcLabel... creating table for Mrg::Grid::Config::ParameterArc... creating table for Mrg::Grid::Config::FeatureArc... creating table for Mrg::Grid::Config::FeatureParams... creating table for Mrg::Grid::Config::NodeMembership... creating table for Mrg::Grid::Config::GroupParams... creating table for Mrg::Grid::Config::GroupFeatures... creating table for Mrg::Grid::Config::SubsystemParams... creating table for Mrg::Grid::Config::DirtyElement... creating snapshot tables checking for necessary user database migrations.... checking for necessary default database migrations.... agent exiting with exception #<Errno::ENOENT: No such file or directory - :memory:> /usr/lib/ruby/1.8/fileutils.rb:1189:in `stat' /usr/lib/ruby/1.8/fileutils.rb:1189:in `lstat' /usr/lib/ruby/1.8/fileutils.rb:1167:in `stat' /usr/lib/ruby/1.8/fileutils.rb:1249:in `copy_file' /usr/lib/ruby/1.8/fileutils.rb:459:in `copy_file' /usr/lib/ruby/1.8/fileutils.rb:383:in `cp' /usr/lib/ruby/1.8/fileutils.rb:1384:in `fu_each_src_dest' /usr/lib/ruby/1.8/fileutils.rb:1400:in `fu_each_src_dest0' /usr/lib/ruby/1.8/fileutils.rb:1382:in `fu_each_src_dest' /usr/lib/ruby/1.8/fileutils.rb:382:in `cp' /usr/bin/wallaby-agent:261 /usr/lib/ruby/site_ruby/1.8/sqlite3/database.rb:564:in `transaction' /usr/bin/wallaby-agent:256 /usr/lib/ruby/site_ruby/1.8/mrg/grid/config/dbmeta.rb:71:in `migrate' /usr/bin/wallaby-agent:255 /usr/bin/wallaby-agent:248:in `each' /usr/bin/wallaby-agent:248
Tested with: wallaby-0.16.3-1 Tested on: RHEL6 i386,x86_64 RHEL5 i386,x86_64 wallaby-agent is working # wallaby-agent -f storing results to :memory: storing snapshots to :memory: creating user tables creating table for Mrg::Grid::Config::Feature... creating table for Mrg::Grid::Config::Group... creating table for Mrg::Grid::Config::Parameter... creating table for Mrg::Grid::Config::Subsystem... creating table for Mrg::Grid::Config::Node... creating table for Mrg::Grid::Config::ArcLabel... creating table for Mrg::Grid::Config::ParameterArc... creating table for Mrg::Grid::Config::FeatureArc... creating table for Mrg::Grid::Config::FeatureParams... creating table for Mrg::Grid::Config::NodeMembership... creating table for Mrg::Grid::Config::GroupParams... creating table for Mrg::Grid::Config::GroupFeatures... creating table for Mrg::Grid::Config::SubsystemParams... creating table for Mrg::Grid::Config::DirtyElement... creating snapshot tables checking for necessary user database migrations.... checking for necessary default database migrations.... checking for necessary snapshot database migrations.... Agent Connection Established... 2013-01-10 07:06:12 [Management] notice Initial object-id bank assigned: 1.503 >>> verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0564.html