Amitav,

I have to agree with Lukasz, about being unable to help without as much as an error message, unless you really are not interested in getting help in the first place.

Also, Amitav, if you end up solving a problem that you encountered, it's considered good etiquette to write a couple of lines describing what the problem was and how it was that you fixed it, rather than reporting that it was a problem with this file or the other, simply because it might be of help to somebody else who might be facing an issue similar to yours.


Regards,
Prashanth Chengi
National PARAM SuperComputing Facility
System Administration and Networking Group
C-DAC Pune

--
Our greatest triumph is not in never falling.
It is in getting up every time we fall.


On Mon, 9 May 2011, Lukasz Lacinski wrote:

It's difficult to help without seeing the error you get.

Lukasz

On 5/9/11 3:18 AM, Amitav Mohanty wrote:
On 05/04/2011 04:39 AM, Lukasz Lacinski wrote:
There are to options only:
1. The machine 10.53.232.5 is not connected to network.
2. There is a firewall between a machine where ./myproxy-logon is executed (you removed a prompt for a reason) and 10.53.232.5.

MyProxy server runs maybe on 10.53.232.5 but we cannot say this as long as there is not connectivity between a client machine and 10.53.232.5:7512.

Please, show an output from:
# netstat -ltpn
and
# iptables-save
executed on 10.53.232.7.

Lukasz


On 5/3/11 5:15 PM, Amitav Mohanty wrote:
On 05/03/2011 11:49 PM, Lukasz Lacinski wrote:
Hi Amitav,

What output from myproxy-logon do you get? Did you use the option -v?

I am pasting the output below.

./myproxy-logon -s linux.machine -v
MyProxy v5.3 17 Jan 2011 PAM OCSP
Attempting to connect to 10.53.232.5:7512
Unable to connect to 10.53.232.5:7512
Unable to connect to linux.machine
Connection timed out

Amitav


It was an issue with /etc/hosts file. I fixed it and now I am getting an authentication error.

Amitav


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply via email to