HP machines with HPUX 11.31 Os.

[Vinayak_HPUX]

1 ]One of my HP machine with HPUX 11.31 Os is in stuck position after reboot..Coudl you plase do the needful..?
2 ]I have checked by booting in single user mode also but it is stucking /hanging at this point only.
3 ]This is IA machine in a 3 node cluster & was as a node in cluster. This m/c as rebooted due to reconfig-stress testcase. so no this node is getting joined.....

Snapshot:
ktracer is off until requested.
Warning: Decreasing the process_id_max parameter or increasing the process_id_min parameter does not affect the IDs assigned to processes which already exist.
Warning: Setting the process_id_max parameter to 1073741823 will allow the system to assign IDs to processes which are larger than 30000. The larger IDs can cause some applications, which assume IDs can not exceed 30000, to behave incorrectly or fail. See the process_id_max(5) manpage for more information.
Warning: Decreasing the process_id_max parameter or increasing the process_id_min parameter does not affect the IDs assigned to processes which already exist.
Warning: Setting the process_id_max parameter to 1073741823 will allow the system to assign IDs to processes which are larger than 30000. The larger IDs can cause some applications, which assume IDs can not exceed 30000, to behave incorrectly or fail. See the process_id_max(5) manpage for more information.
Installing Socket Protocol families AF_INET and AF_INET6
Kernel EVM initialized
sec_init(): kernel RPC authentication/security initialization.
secgss_init(): kernel RPCSEC_GSS security initialization.
rpc_init(): kernel RPC initialization.
rpcmod_install(): kernel RPC STREAMS module "rpcmod" installation. ...(driver_install)
NOTICE: nfs_client_pv3_install(): nfs3 File system was registered at index 11.
NOTICE: nfs_client_pv4_install(): nfs4 File system was registered at index 12.
NOTICE: cachefsc_install: cachefs File system was registered at index 14.
LLT INFO V-14-1-10009 LLT Protocol available
GAB INFO V-15-1-20021 GAB available
vxfen: vxfen protocol available
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/3/1/0
Boot device's HP-UX HW path is: 0.1.1.0.0.0
igelan1: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
igelan2: INITIALIZING HP A6825-60101 PCI 1000Base-T Adapter at hardware path 0/2/1/0

System Console is on the Built-In Serial Interface
AF_INET socket/streams output daemon running, pid 1073711861
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1
LVM: Root VG activated
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608

[Steven E. Protter · Accepted solution]

Shalom,

It appears your system was busy with so many processes that 30,000 processes were running and it ran out of space on the process id list.

I've never seen that before.

Warning: Setting the process_id_max parameter to 1073741823 will allow the system to assign IDs to processes which are larger than 30000. The larger IDs can cause some applications, which assume IDs can not exceed 30000, to behave incorrectly or fail. See the process_id_max(5) manpage for more information.

You can as it says get around this but your applications may not work properly.

If possible, I would test this, or reduce system load to avoid taking this risk.

kctune -l | grep process_id_max

process_id_max can be set in the kernel. The kctune command will get you the current settings and tell you if the parameter is dynamic or not.

SEP

[smatador]

Hi,
Maybe you have to look to nproc too, look the man page of process_id_max
http://docs.hp.com/en/B2355-60130/process_id_max.5.html

[Vinayak_HPUX]

I have ignited HPUX machine :: sfqapa5.vxindia.veritas.com & selected FS layout as "VERITAS Volume Manager (VxVM) with VxFS"
& have below logs where machine is in stuck position.

OS : HPUX11.31 march_09 fusion release i.e. latest HPUX11iv3 Os image from hxignite server.
===============================
Logs from console :: sfqapa5-c

* Bringing up Network (lan0)
add net default: gateway 10.209.140.1
* Reading configuration information from server...
* Loading configuration utility...
* Beginning installation from source: 10.209.137.46
======= 06/23/09 00:30:19 EDT Starting system configuration...
* Configure_Disks: Begin
* Will install B.11.31 onto this system.
NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk

VxVM vxdg ERROR V-5-1-585 Disk group rootdg: cannot create: Invalid attribute specification
* Starting VxVM. Target version: 5.0.
* (Install version: B.11.31, VxVM 4.1.)
* Enabling VxVM.
* Creating VxVM Disk Group "rootdg". Target version: 5.0.
* Creating VxVM Disk "disk27".
* Adding Disk "disk27" to rootdg as DM rootdisk01.
ERROR: CREATE_GROUP: do_cmd: Error (5120) cmd line = "/sbin/vxdg -T 140 init
rootdg rootdisk01=c2t0d0 cds=off"
* smapi listener returned "ACTION_FAILURE" for message "CREATE_GROUP"

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]):
========================================================

Above issue is not coming if we are installing os by using DVD set.

[Vinayak_HPUX]

I got the solutions

[gaurav_srivastava]

I am also facing the same issue but if somebody tries from the ignite server then what to do in this case.