[ 
https://issues.apache.org/jira/browse/DTACLOUD-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194529#comment-13194529
 ] 

Marios Andreou commented on DTACLOUD-132:
-----------------------------------------

Hi Raja, 

ok - now we're getting to the bottom of this. The problem is that, although it 
seems installation was successful, your system can't find the detacloudd 
executable because the directory /var/lib/gems/1.8/bin is not in your $PATH. 
You can resolve this either by using the full path to deltacloudd when running 
the server:

/var/lib/gems/1.8/bin/deltacloudd -i ec2 
(for example to start server with the ec2 driver)

OR

you can place that directory in your path: "export 
PATH=$PATH:/var/lib/gems/1.8/bin"

 (and you may want to place this in your $HOME/.bashrc file so it is exported 
every time you open a terminal shell). Please let me know if that works for you 
so I can close this issue,

marios
                
> deltacloudd & deltacloudc command not found
> -------------------------------------------
>
>                 Key: DTACLOUD-132
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-132
>             Project: DeltaCloud
>          Issue Type: Question
>         Environment: Ubuntu 
>            Reporter: Rajaguganeswaran K
>            Assignee: David Lutterkort
>
> Hai,
> We are trying out deltacloud in ubuntu. we have installed the required 
> dependencies. Also we have installed deltacloud-core and deltacloud-client 
> using gem install. We are able to get the response for gem list 
> deltacloud-core and gem list deltacloud-client. But we are not able to work 
> with the deltacloudd and deltacloudc command line tools.
> When we give ' which deltacloudd ' , it simply skips to the next command line 
> without displaying any location for the gem and the start script. Please 
> suggest us to get those commands and to run the deltacloud server.
> Raja

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to