CLI hangs

suheil · Post by **suheil** » Mon Dec 19, 2005 6:18 pm

Hi

I am using Vault 3.0.6. I am able to use the GUI Client and Web-browser Client. However, I just installed the 3.0.6 API, and tried a few simple commands.

Code: Select all

vault help

works as expected and gives me a list of available commands. Similalrly, vault help for a specific single command works.

If I enter a command with wrong syntax, I get xml output telling me so.

But when I try a command with correct syntax (like one of those below), the command just hangs.
e.g.

Code: Select all

vault addrepository -host IPaddr -user admin -password admpwd TEST
vault history -host IPaddr -user admin -password admpwd -repository "Main Repository" "$/TEST"

No output, no results. I tried waiting a long time, thinking it might just be slow, but to no avail. Nor can I interrupt with ^C.

What could be happening here?

Thanks,
-sl

Post by **jclausius** » Tue Dec 20, 2005 6:53 am

The Vault Command Line Client (CLC) is installed with the normal Vault client.

Try this:

From the installation directory of Vault 3.0.6 client*, and run the following command for the Vault CLC

vault LISTREPOSITORIES -host "IP_ADDRESS" -user "USER" -password "PASS"

- Notice the use of double quotes.

Does that work?

-----
* - There is a Vault 3.1.5 version available. It is strongly recommended everyone on Vault 3.0.x upgrade to this latest version.

suheil · Post by **suheil** » Tue Dec 20, 2005 11:25 am

That hangs too.

Post by **jclausius** » Tue Dec 20, 2005 11:37 am

So the CLC out of the Vault Client directory seems to hang as well? It could be the client's request is not getting to the Vault Server. Do you have any proxy settings required that may need to be configured for the CLC?

We could trouble shoot this from the Server's point of view. Can you see any log in attempts during the last run of the CLC?

You could also place the Vault Server's Log in Debug mode, and re-attempt the command, you should be able to see the actual log in command logged in the server's log file. This would provide much more information about the CLC's attempt to connect.

If you do not see any login attempts from the client, something in your setup is blocking the request from the CLC.

suheil · Post by **suheil** » Tue Dec 20, 2005 11:58 am

Ah! No logins were being logged; they were not getting through. I have a Norton firewall on my machine, so guessing that it may be behind this, I disabled it and retried. With firewall disabled, it works.

Thanks.