Bug #682
Sunstone: missing OneMonitor entry in install.sh
Status: | Closed | Start date: | 06/15/2011 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Hector Sanjuan | % Done: | 0% | |
Category: | Sunstone | |||
Target version: | Release 3.0 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: |
Description
Hello
The module OneMonitor is not installed by the install.sh script and the following message appears in $ONE_LOCATION/var/sunstone.log file.
Extract from the log file (with ONE_LOCATION set to /srv/cloud/one30)
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- OneMonitorClient (LoadError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /srv/cloud/one30/lib/sunstone/models/SunstoneServer.rb:20
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /srv/cloud/one30/lib/sunstone/sunstone-server.rb:48
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /srv/cloud/one30/lib/sunstone/config.ru:23
from /usr/lib/ruby/gems/1.8/gems/rack-1.3.0/lib/rack/builder.rb:51:in `instance_eval'
from /usr/lib/ruby/gems/1.8/gems/rack-1.3.0/lib/rack/builder.rb:51:in `initialize'
from /srv/cloud/one30/lib/sunstone/config.ru:1:in `new'
from /srv/cloud/one30/lib/sunstone/config.ru:1
The following command fixes the startup problem:
cp -a <compile_dir>/src/sunstone/share $ONE_LOCATION/lib/sunstone
Also, the runOneMonitor.sh script is missing as reported by the "sunstone-server stop" output.
/srv/cloud/one30/lib/sunstone/share/OneMonitor/runOneMonitor.sh: No such file or directory
Related issues
Associated revisions
Bug #682: Added missing Sunstone files to install script
History
#1 Updated by Hector Sanjuan about 10 years ago
- Resolution set to fixed
Hi, these problems should be fixed now. Thanks for taking the time to report
#2 Updated by Stéphane Angot about 10 years ago
Ok for me
#3 Updated by Hector Sanjuan almost 10 years ago
- Status changed from New to Closed