patch b qnet problem?

After installing patch B on my laptop, remaking my image files (from the
identical build files from before) and copying them to my embedded system
(PC-104, pentium II), qnet has stopped working.

I don’t get any errors on boot, or when I try to manually start qnet from
the command prompt (mount -Tio-net -pqnet), and a /net directory is created,
but the directory is empty. /net/localhost is not there, neither is my
laptop (which is connected directly over ethernet).

The main point is that this setup worked immediately before I installed
Patch B and did not work immediately after, so I am very suspicious.

Has anyone else experienced similar errors with patch b? Does anyone have
any suggestions?

Thanks much,
Dan

Dan Helmick a écrit :

After installing patch B on my laptop, remaking my image files (from the
identical build files from before) and copying them to my embedded system
(PC-104, pentium II), qnet has stopped working.

I don’t get any errors on boot, or when I try to manually start qnet from
the command prompt (mount -Tio-net -pqnet), and a /net directory is created,
but the directory is empty. /net/localhost is not there, neither is my
laptop (which is connected directly over ethernet).

The main point is that this setup worked immediately before I installed
Patch B and did not work immediately after, so I am very suspicious.

Has anyone else experienced similar errors with patch b? Does anyone have
any suggestions?

Thanks much,
Dan

Did you release all your qrtp machines? I had this problem in the past!
I think that qnet is moving a lot as some features are missing.

Alain.

Dan Helmick <danielhelmick@earthlink.net> wrote:

After installing patch B on my laptop, remaking my image files (from the
identical build files from before) and copying them to my embedded system
(PC-104, pentium II), qnet has stopped working.

I don’t get any errors on boot, or when I try to manually start qnet from
the command prompt (mount -Tio-net -pqnet), and a /net directory is created,
but the directory is empty. /net/localhost is not there, neither is my
laptop (which is connected directly over ethernet).

Is tcpip working properly? If /net existing but nothing in there
(not even the node itself), usually indicate your local interface
is not comming up.

Also, I saw your nodename is “localhost”, this is not a good thing.
You probably didn’t set the hostname and let it be the default
“localhost”. When QNET start, and there is another “localhost”
on the network, (to avoid duplicate name), the second QNET will
stay there, wait till you change your hostname.

So 2 thing to try. 1) Make sure tcpip work properly, 2) Set the
node name before start QNET, or, if you can’t, your QNET command
line option “host=”, ie:

io-net -d -p tcpip -p qnet host=“myhost.mydomain”
or
mount -Tio-net -o “host=myhost.mydomain” /lib/dll/npm-qnet.so

-xtang

The main point is that this setup worked immediately before I installed
Patch B and did not work immediately after, so I am very suspicious.

Has anyone else experienced similar errors with patch b? Does anyone have
any suggestions?

Thanks much,
Dan

Is tcpip working properly? If /net existing but nothing in there
(not even the node itself), usually indicate your local interface
is not comming up.

I’m not using TCP/IP. For my case (just directly connecting two nodes with
a crossover ethernet cable) TCP/IP isn’t necessary (someone should
definitely correct me if I’m wrong, but I know that qnet worked previously
without it).

Also, I saw your nodename is “localhost”, this is not a good thing.
You probably didn’t set the hostname and let it be the default
“localhost”. When QNET start, and there is another “localhost”
on the network, (to avoid duplicate name), the second QNET will
stay there, wait till you change your hostname.

I was just using localhost as a generic example. I’m actually using a
‘real’ hostname.

-Dan