vpars console getting frozen

[likid0]

Hy,


I am installing a partition with several vpars,
at the moment i have installed vpars software and all the patches on the server, the i create the first vpar and boot from /stand/vpmon, the machines boots ok until it gets to the login prompt, then the console freezes, i can ssh or telnet to the server with no problem, but the console doesnt respond, i have tried several reboots but its always the same, i have seen in the syslog the following output wich looks suspicious:

Sep 19 18:35:01 med9srd vmunix: igelan0: INITIALIZING HP A6794-60001 PCI 1000Bas e-T at hardware path 1/0/1/1/0/4/0
Sep 19 18:35:01 med9srd vmunix: igelan1: INITIALIZING HP A9784-60002 PCI/PCI-X 1 000Base-T FC/GigE Combo Adapter at hardware path 1/0/2/1/0/6/0
Sep 19 18:35:01 med9srd vmunix: Entering cifs_init...
Sep 19 18:35:01 med9srd vmunix: Initialization finished successfully... slot is 9
Sep 19 18:35:01 med9srd vmunix: 64 vcn
Sep 19 18:35:01 med9srd vmunix: 65 vcs
Sep 19 18:35:01 med9srd vmunix:
Sep 19 18:35:01 med9srd vmunix: Host is virtual System Console slave
Sep 19 18:35:01 med9srd vmunix: Logical volume 64, 0x3 configured as ROOT
Sep 19 18:35:01 med9srd vmunix: Logical volume 64, 0x9 configured as SWAP
Sep 19 18:35:01 med9srd vmunix: Logical volume 64, 0x9 configured as DUMP
Sep 19 18:35:01 med9srd vmunix: Swap device table: (start & size given in 5 12-byte blocks)
Sep 19 18:35:01 med9srd vmunix: entry 0 - major is 64, minor is 0x9; sta rt = 0, size = 8388608
Sep 19 18:35:01 med9srd vmunix: Dump device table: (start & size given in 1 -Kbyte blocks)
Sep 19 18:35:01 med9srd vmunix: entry 0000000000000000 - major is 31, mi nor is 0x36000; start = 314208, size = 4194304
Sep 19 18:35:01 med9srd vmunix: read_ss_nvm: Cannot validate NVM - -2
Sep 19 18:35:01 med9srd vmunix: Starting the STREAMS daemons-phase 1
Sep 19 18:35:01 med9srd vmunix: vconsd: exited
Sep 19 18:35:01 med9srd vmunix:
Sep 19 18:35:01 med9srd vmunix: System Console is virtual
Sep 19 18:35:01 med9srd vmunix: Create STCP device files
Sep 19 18:35:01 med9srd vmunix: vconsd: exited
Sep 19 18:35:01 med9srd vmunix: Starting the STREAMS daemons-phase 2
Sep 19 18:35:01 med9srd vmunix: $Revision: vmunix: v w: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' - - cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $



this part looks strange:

vconsd: exited


any idea what can cause this??


thnx a lot

[Marvin Strong]

Are you sure the console is frozen or is it that the vpar just doesn't know about the console? You have to assign the console hardware path to the vpar.

Also I think cntl-A switches between vpars. I might be wrong on the cntl-A its been awhile since I have had a vpar to play with.

[Jannik]

It is ctrl to switch vpar. But try to look at the file /etc/rc.log is every thing startet or is it hanging at the last part?

[Steven E. Protter]

Shalom,

I think martin has a point on the hardware assignment issue.

Also, it could merely be a hardware issue in the GSP/MSP/iLo card.

SEP

[IT_2007]

check syslog for any errors.

Also did you try to do CTRL-a to login to server at console?

[likid0]

Hy,

It cant be anything to do with the hardware i would think, because it works ok, when i reboot the same machine as a vpar.

I cant use ctrl-a to change vpars, its completly frozen, i only have one vpar create anyway.

looking at the rc.log i see vpars load ok:

Virtual Partitions Initialization
Output from "/sbin/rc1.d/S105vparinit start":
----------------------------
Created VPAR device files
Created VPAR dump file (NORMAL)

and it load everything:

**************************************************
HP-UX run-level transition completed
Tue Sep 19 18:37:07 2006
**************************************************


it keeps giving this error which i cant find any info on it but doesnt look good:
Sep 19 18:35:01 med9srd vmunix: entry 0000000000000000 - major is 31, mi nor is 0x36000; start = 314208, size = 4194304
Sep 19 18:35:01 med9srd vmunix: read_ss_nvm: Cannot validate NVM - -2
Sep 19 18:35:01 med9srd vmunix: Starting the STREAMS daemons-phase 1
Sep 19 18:35:01 med9srd vmunix: vconsd: exited
Sep 19 18:35:01 med9srd vmunix:
Sep 19 18:35:01 med9srd vmunix: System Console is virtual
Sep 19 18:35:01 med9srd vmunix: Create STCP device files
Sep 19 18:35:01 med9srd vmunix: vconsd: exited


i have done the same process in the other npartition and everything is working ok.

i never had to tell the vpar what is the hw path of the console, whats that about?

all i have in the vpar are the virtual consoles like allways in NO_HW:

tty 2 64 vcn NO_HW DEVICE Virtual Console Client
tty 3 65 vcs NO_HW DEVICE Virtual Console Server



Thnx a lot once again 4 ur help

[melvyn burnard · Accepted solution]

You do NOT have to add in the console device when creating your Vpar, as it uses the virtual console, but what MUST be in the first Vpar is the hardware path of the core i/o card that has the console port.

What you do not tell us is what model of server, what OS versiojn, and what Vpars software version you are using.

The Sep 19 18:35:01 med9srd vmunix: read_ss_nvm: Cannot validate NVM - -2
message indicates that the kernel is unable to read the server stable storage at boot time, hence this error.
Thios would possibly be the cause of the vconsd exiting, and losing your virtual console server means you cannot "connect" to it from you virtual console.

You also need to verify you have the latest firmware installed for your server.

[likid0]

Great, now i understand what you meant by the hw path to the console, you were spot ON!, the first vpar that was loading didnt have the 0.0.0 included in the vpar configuration, and that whas the problem as you sed, it didnt have access to the terminal console.

Once i added the 0.0.0 to the 1st vpar its all w0rking fine!.

Thnx a lot and 10 points on their way.

[likid0]

Great, now i understand what you meant by the hw path to the console, you were spot ON!, the first vpar that was loading didnt have the 0.0.0 included in the vpar configuration, and that whas the problem as you sed, it didnt have access to the terminal console.

Once i added the 0.0.0 to the 1st vpar its all w0rking fine!.

Thnx a lot and 10 points on their way.