Ronelle Landy created DTACLOUD-427:
--------------------------------------

             Summary: Starting Deltacloud server with WEBrick from any 
directory other than deltacloud/server, errors out 
                 Key: DTACLOUD-427
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-427
             Project: DeltaCloud
          Issue Type: Bug
          Components: Server
         Environment: WEBrick 1.3.
Deltacloud 1.1.0
            Reporter: Ronelle Landy


Starting Deltacloud server (using the mock provider) from the top-level 
deltacloud dir errors out:

[rlandy@localhost ~]$ cd /home/rlandy/workspace/deltacloud
[rlandy@localhost deltacloud]$ ./server/bin/deltacloudd -i mock -w
Starting Deltacloud API :: mock :: http://localhost:3001/api

config.ru:23:in `load': no such file to load -- ./lib/deltacloud_rack.rb 
(LoadError)
        from config.ru:23
        from /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/builder.rb:51:in 
`instance_eval'
        from /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/builder.rb:51:in 
`initialize'
        from config.ru:1:in `new'
        from config.ru:1

cd to the deltacloud/server dir. Now start Deltacloud server with WEBrick w/o 
any issues:

[rlandy@localhost deltacloud]$ cd server
[rlandy@localhost server]$ ./bin/deltacloudd -i mock -w
Starting Deltacloud API :: mock :: http://localhost:3001/api

./lib/deltacloud/./drivers/.././core_ext/proc.rb:21: warning: already 
initialized constant Callback
./lib/deltacloud/./helpers/deltacloud_helper.rb:341: warning: already 
initialized constant HTML_ESCAPE
=> Ctrl-C to shutdown server
[2013-01-18 14:45:42] INFO  WEBrick 1.3.1
[2013-01-18 14:45:42] INFO  ruby 1.8.7 (2012-10-12) [x86_64-linux]
[2013-01-18 14:45:42] INFO  WEBrick::HTTPServer#start: pid=12967 port=3001


^C[2013-01-18 14:45:44] INFO  going to shutdown ...
[2013-01-18 14:45:44] INFO  WEBrick::HTTPServer#start done.
[rlandy@localhost server]$ 

See config.ru for the causes of the error.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to