Good to hear you got it working, thanks for letting us know.
On Nov 5, 2007 11:23 AM, Robert Ashcraft <[EMAIL PROTECTED]> wrote:
> I did indeed turn out to be the switch...
>
> We purchased another of the same model of the netgear switch (though
> curiously they had a different look, different d
I did indeed turn out to be the switch...
We purchased another of the same model of the netgear switch (though
curiously they had a different look, different dimensions, and different
port layouts) and it worked fine the first time, passing all tests.
I am still not sure why the switch would
It seems like it may some problem with the switch. My colleague said
that they tried connecting the server/node with a crossover cable and
were able to pass all of the Oscar tests... He also said that he tried
another switch (100MB) and was also able to get the tests passed. This
seems to sa
Have you tried wiping the .ssh directory on the node? It may make things
worse, but it seems to be finding some files with contents it isn't
expecting there, judging by the messages from "ssh -vvv"
It will probably ask you for a password after that, but if it lets you SSH
at all, then we can work
Thanks again for your help.
We have tried a number of things but cannot seem to find what the
problem is. I will list a few of the things we have tried and some
other information to see if it helps point to anything...
Problem:
Cannot SSH from the compute back to the head node, which causes
Hi Robert,
One minor note is that you have to check to see if any normal user can access
from server to client nodes and vice versa but not a root user.
Regards,
- DongInn
Robert Ashcraft wrote:
> Thanks again for your help.
>
> We have tried a number of things but cannot seem to find what
Okay, so looking at the original oscarinstall.log and reading your original
message again, two things jump out at me. The first is that in your
/etc/hosts file you have one hostname mapping to two different IP
addresses. This may cause confusion.
The other thing I notice is that OSCAR isn't seei
So, I changed the internal IP to 192.168.1.10 to prevent any would-be
conflicts, ran the start_over script, and went through the usual setup
process.
Basically the same thing happened, but I got the iptable and verbose SSH
output. Maybe you can help make a little sense out of it.
Here is t
OSCAR doesn't need a gateway on the head node to work. One way
communication generally implies there is a firewall on the head node or
other routing problem.
What do you get from "iptables -L" on the head node?
You might try using a different address for the head node than 192.168.0.1,
that is a
Michael,
Thanks for the response. My colleague has tried those things and they
did not seems to help. The "ssh -vvv" command does not provide any
output and presumably just hangs somewhere in the connection process.
Just as some information... If we set up the the compute node to
connect
Robert Wilson Ashcraft
Sent: Thu 10/25/2007 12:13 PM
To: oscar-users@lists.sourceforge.net
Subject: [Oscar-users] SSH node->server test failure
Hi,
I am attempting to set up an OSCAR cluster. I have gotten through everything
past step 7, Complete CLuster Setup (which finished successfu
Do you have the firewall on the head node turned off?
You can check by doing "iptables -L" or checking under the "security level"
utility.
You can also try doing "ssh -vvv [EMAIL PROTECTED]" and see if it gives you any
clues.
On 10/25/07, Robert Wilson Ashcraft <[EMAIL PROTECTED]> wrote:
>
> Hi,
12 matches
Mail list logo
