problem booting up after new image creation

Hello all,

I created a new image with a new node#. licinfo -a reveals plenty of qnx
and tcp licenses, yet Socklet errors out on bootup stating ‘no license’
… but then I can start Socklet with no erros once the system is
booted.

I see this as strange system behavior. Why does the system not read the
licenses correctly on bootup?

Any insights would be greatly appreciated…

delia

Delia Leal <Delia.Leal@sri.com> wrote:

Hello all,

I created a new image with a new node#. licinfo -a reveals plenty of qnx
and tcp licenses, yet Socklet errors out on bootup stating ‘no license’
… but then I can start Socklet with no erros once the system is
booted.

I see this as strange system behavior. Why does the system not read the
licenses correctly on bootup?

Any insights would be greatly appreciated…

Do you have a “nameloc” running? Is this a standalone machine?
[on a standalone machine, you need nameloc running.]

Cheers,
-RK


Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.

Robert Krten wrote:

Delia Leal <> Delia.Leal@sri.com> > wrote:
Hello all,

I created a new image with a new node#. licinfo -a reveals plenty of qnx
and tcp licenses, yet Socklet errors out on bootup stating ‘no license’
… but then I can start Socklet with no erros once the system is
booted.

I see this as strange system behavior. Why does the system not read the
licenses correctly on bootup?

Any insights would be greatly appreciated…

Do you have a “nameloc” running? Is this a standalone machine?
[on a standalone machine, you need nameloc running.]

Yes, nameloc is running.

Delia Leal <Delia.Leal@sri.com> wrote:

Robert Krten wrote:

Delia Leal <> Delia.Leal@sri.com> > wrote:
Hello all,

I created a new image with a new node#. licinfo -a reveals plenty of qnx
and tcp licenses, yet Socklet errors out on bootup stating ‘no license’
… but then I can start Socklet with no erros once the system is
booted.

I see this as strange system behavior. Why does the system not read the
licenses correctly on bootup?

Any insights would be greatly appreciated…

Do you have a “nameloc” running? Is this a standalone machine?
[on a standalone machine, you need nameloc running.]


Yes, nameloc is running.

Is nameloc running soon enough?
If your starting Tcpip in your startup scripts make sure that namelog
was started first and give it a second or two to do it’s magic.

Try adding these lines before you start Socket in your startup scripts:
lifinco -a > log_licenses
sleep 2
lifinco -a > log_licenses
Socket [options]


Bill Caroselli – Q-TPS Consulting
1-(626) 824-7983
qtps@earthlink.net

Bill Caroselli wrote:

Delia Leal <> Delia.Leal@sri.com> > wrote:
Robert Krten wrote:

Delia Leal <> Delia.Leal@sri.com> > wrote:
Hello all,

I created a new image with a new node#. licinfo -a reveals plenty of qnx
and tcp licenses, yet Socklet errors out on bootup stating ‘no license’
… but then I can start Socklet with no erros once the system is
booted.

I see this as strange system behavior. Why does the system not read the
licenses correctly on bootup?

Any insights would be greatly appreciated…

Do you have a “nameloc” running? Is this a standalone machine?
[on a standalone machine, you need nameloc running.]


Yes, nameloc is running.

Is nameloc running soon enough?
If your starting Tcpip in your startup scripts make sure that namelog
was started first and give it a second or two to do it’s magic.

Try adding these lines before you start Socket in your startup scripts:
lifinco -a > log_licenses
sleep 2
lifinco -a > log_licenses
Socket [options]

The interesting part of this behavior is that if I boot up with the
original node #, all is fine. The only difference between the two
images is the node#. I’m using the same sysinit.x … All that has
changed is the node#

delia

“Delia Leal” <Delia.Leal@sri.com> wrote in message
news:3E370BA8.8C5364F2@sri.com

Bill Caroselli wrote:

Delia Leal <> Delia.Leal@sri.com> > wrote:
Robert Krten wrote:

Delia Leal <> Delia.Leal@sri.com> > wrote:
Hello all,

I created a new image with a new node#. licinfo -a reveals plenty
of qnx
and tcp licenses, yet Socklet errors out on bootup stating ‘no
license’
… but then I can start Socklet with no erros once the system is
booted.

I see this as strange system behavior. Why does the system not
read the
licenses correctly on bootup?

Any insights would be greatly appreciated…

Do you have a “nameloc” running? Is this a standalone machine?
[on a standalone machine, you need nameloc running.]


Yes, nameloc is running.

Is nameloc running soon enough?
If your starting Tcpip in your startup scripts make sure that namelog
was started first and give it a second or two to do it’s magic.

Try adding these lines before you start Socket in your startup scripts:
lifinco -a > log_licenses
sleep 2
lifinco -a > log_licenses
Socket [options]


The interesting part of this behavior is that if I boot up with the
original node #, all is fine. The only difference between the two
images is the node#. I’m using the same sysinit.x … All that has
changed is the node#

If your node number is 10 for example you need 10 licenses even though you
only have 3 nodes on your network.

delia

What did you change the node number from, and to?
How many licenses is “lots”?

-Martin.

The interesting part of this behavior is that if I boot up with the
original node #, all is fine. The only difference between the two
images is the node#. I’m using the same sysinit.x … All that has
changed is the node#

delia

Martin Walter wrote:

What did you change the node number from, and to?
How many licenses is “lots”?

-Martin.


The interesting part of this behavior is that if I boot up with the
original node #, all is fine. The only difference between the two
images is the node#. I’m using the same sysinit.x … All that has
changed is the node#

delia

Thanks all for your help. It turned out to be a timing issue with
nameloc, automap & netstart.

delia

“Delia Leal” <Delia.Leal@sri.com> wrote in message
news:3E384846.BA5DCDCD@sri.com

Martin Walter wrote:

What did you change the node number from, and to?
How many licenses is “lots”?

-Martin.


The interesting part of this behavior is that if I boot up with the
original node #, all is fine. The only difference between the two
images is the node#. I’m using the same sysinit.x … All that has
changed is the node#

delia

Thanks all for your help. It turned out to be a timing issue with
nameloc, automap & netstart.

Well nameloc behavior will change depeding on the node number it’s on so
that could explain it, because automap and netstart shouldn’t be affected by
the node #.

delia