TCP/IP socklet license problem

I have a 5 node system, running QNX4.24.
The QNX networking works fine.

I bought 5 TCP/IP socklet licenses, and installed the 5 licenses in all
5 systems.

When I try to start the TCP/IP services, on Node1 they start.
On Node 2,4,5 I get an error message about no license.
On Node 3, which was originally Node1, but had the .boot remade for node
3,
the TCP/IP services start.

Does anyone have any ideas about what could be going on?
How can it be I take the .license file from Node 1, and copy it to Node
2
and suddenly TCP/IP doesn’'t have a valid license.

I wish QNX still had some free telephone support.

What does:
licinfo -a
say for each node?

(You must run as root.)

It will show how many of each license you have, how many are in use and
which nodes are using them. My guess is that you’ll find out that some
nodes don’t believe that they have 5 valid TCP/IP licenses.


Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Joe Seraphim” <wjgroup@weir-jones.com> wrote in message
news:3BF53B61.C07FA539@weir-jones.com

I have a 5 node system, running QNX4.24.
The QNX networking works fine.

I bought 5 TCP/IP socklet licenses, and installed the 5 licenses in all
5 systems.

When I try to start the TCP/IP services, on Node1 they start.
On Node 2,4,5 I get an error message about no license.
On Node 3, which was originally Node1, but had the .boot remade for node
3,
the TCP/IP services start.

Does anyone have any ideas about what could be going on?
How can it be I take the .license file from Node 1, and copy it to Node
2
and suddenly TCP/IP doesn’'t have a valid license.

I wish QNX still had some free telephone support.

If this only happens at startup then it could be a timing issue where
nameloc has not yet informed the nodes of the available licenses. I assume
node 1 has nameloc running and where node 3 was node 1 it also runs nameloc.
Is this correct? Can the rest of the other nodes see these node using fleet?
If not run nameloc on them if they can then add a nameloc -k or a sleep to
the sysinit file before starting licensed services.

“Joe Seraphim” <wjgroup@weir-jones.com> wrote in message
news:3BF53B61.C07FA539@weir-jones.com

I have a 5 node system, running QNX4.24.
The QNX networking works fine.

I bought 5 TCP/IP socklet licenses, and installed the 5 licenses in all
5 systems.

When I try to start the TCP/IP services, on Node1 they start.
On Node 2,4,5 I get an error message about no license.
On Node 3, which was originally Node1, but had the .boot remade for node
3,
the TCP/IP services start.

Does anyone have any ideas about what could be going on?
How can it be I take the .license file from Node 1, and copy it to Node
2
and suddenly TCP/IP doesn’'t have a valid license.

I wish QNX still had some free telephone support.

If these are “old style” licenses kept as one file/license in
/etc/config/licenses, then if you use cp on them the target will look OK
to ls but will be useless. You need to use the license utility to copy
from node to node.


“Brown, Richard” wrote:

If this only happens at startup then it could be a timing issue where
nameloc has not yet informed the nodes of the available licenses. I assume
node 1 has nameloc running and where node 3 was node 1 it also runs nameloc.
Is this correct? Can the rest of the other nodes see these node using fleet?
If not run nameloc on them if they can then add a nameloc -k or a sleep to
the sysinit file before starting licensed services.

“Joe Seraphim” <> wjgroup@weir-jones.com> > wrote in message
news:> 3BF53B61.C07FA539@weir-jones.com> …
I have a 5 node system, running QNX4.24.
The QNX networking works fine.

I bought 5 TCP/IP socklet licenses, and installed the 5 licenses in all
5 systems.

When I try to start the TCP/IP services, on Node1 they start.
On Node 2,4,5 I get an error message about no license.
On Node 3, which was originally Node1, but had the .boot remade for node
3,
the TCP/IP services start.

Does anyone have any ideas about what could be going on?
How can it be I take the .license file from Node 1, and copy it to Node
2
and suddenly TCP/IP doesn’'t have a valid license.

I wish QNX still had some free telephone support.

True. And licinfo will confirm this.


Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Richard R. Kramer” <rrkramer@kramer-smilko.com> wrote in message
news:3BF596D0.F138E990@kramer-smilko.com

If these are “old style” licenses kept as one file/license in
/etc/config/licenses, then if you use cp on them the target will look OK
to ls but will be useless. You need to use the license utility to copy
from node to node.


“Brown, Richard” wrote:

If this only happens at startup then it could be a timing issue where
nameloc has not yet informed the nodes of the available licenses. I
assume
node 1 has nameloc running and where node 3 was node 1 it also runs
nameloc.
Is this correct? Can the rest of the other nodes see these node using
fleet?
If not run nameloc on them if they can then add a nameloc -k or a sleep
to
the sysinit file before starting licensed services.

“Joe Seraphim” <> wjgroup@weir-jones.com> > wrote in message
news:> 3BF53B61.C07FA539@weir-jones.com> …
I have a 5 node system, running QNX4.24.
The QNX networking works fine.

I bought 5 TCP/IP socklet licenses, and installed the 5 licenses in
all
5 systems.

When I try to start the TCP/IP services, on Node1 they start.
On Node 2,4,5 I get an error message about no license.
On Node 3, which was originally Node1, but had the .boot remade for
node
3,
the TCP/IP services start.

Does anyone have any ideas about what could be going on?
How can it be I take the .license file from Node 1, and copy it to
Node
2
and suddenly TCP/IP doesn’'t have a valid license.

I wish QNX still had some free telephone support.