Operating System - HP-UX
1752703 Members
5334 Online
108789 Solutions
New Discussion юеВ

Re: error re-creating an Ignite client...

 
Steve Hinchman
Advisor

error re-creating an Ignite client...

I am trying to re-create an Ignite client for server xxxxxx and it keeps failing with the following messages:

* Scanning system for IO devices...

WARNING: send_smapi_command_listener: smapi_send_and_wait failed, got: CONTINUE

WARNING: send_smapi_command_listener: smapi_send_and_wait failed, got: CONTINUE

ERROR: Unable to initiate connection to IO listener: Error 0 (errno = 0)

WARNING: Could not find Q_BOOT device. Cannot determine what the boot device was.

ERROR: Could not write disk information file

I have checked the ITRC for clues and found some help, but nothing that solves the problem.

ioscan shows all devices "claimed" except for:
tty 2 64 vcn NO_HW DEVICE Virtual Console Client
tty 3 65 vcs NO_HW DEVICE Virtual Console Server

I have deleted the old /var/opt/ignite/clients directory and link.

Can someone help solve this issue?
5 REPLIES 5
Michal Kapalka (mikap)
Honored Contributor

Re: error re-creating an Ignite client...

hi,

check this link :

http://docstore.mik.ua/manuals/hp-ux/en/IUX/faq.html

its a know error.

mikap
Steve Hinchman
Advisor

Re: error re-creating an Ignite client...

These links are all good reading, but I could not find any entries that deal specifically with the errors I documented. If you found a specific solution would you please provide a specific link?
sujit kumar singh
Honored Contributor

Re: error re-creating an Ignite client...

Hi


can you please confirm the following that shall be helpful for you to get more replies:
1) swlist -l bundle | grep -i ignite
2) what commad is being used to create the image?
3) is your server a VPAR?
4) What is the OS version for the server tha you are creating an Image.
5) for the server you intend to create the Image please post
#vgdisplay -v vg00
#lvlnboot -v
#cat /stand/bootconf

regards
sujit
Steve Hinchman
Advisor

Re: error re-creating an Ignite client...

Upgrading to C.7.7.98 on both the Ignite server and client solved my problem.

Thanks for the assistance.