Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

PI/open installation question

33 views
Skip to first unread message

Natasha Zagsky

unread,
Jul 21, 2010, 7:36:00 PM7/21/10
to
I'm setting up a test server and I am running into a problem during
the installation process. If you're familiar with installing PI/open,
please help.

Database: PI/open Rev. 3.6.2.r6
Operating System: HP-UX B.10.20
Hardware: HP 9000 Series 800 System


From "PI/open Installation Menu" (UNIX script ./pi_install)
I execute option "6 updateisys Update ISYS account"
and receive this error message:

Updating /usr/isys ...
updateisys: Failed to bootstrap shared PI/open.


UNIX script updateisys runs command
./piopen -boot 102
which generates the following output:
...
Loading PI/open
*** Status 2 (OS: No such file or directory), severity WARNING,
subsystem STARTUP
Full details have been directed to: /usr/isys/&PILOG&/WARN.0

Error: Maximum shared memory segment size is too small.

Please check your system configuration parameters against those
listed under option 5 of the PI/open installation menu

Fatal Error: could not setup shared memory
*** Status 12940 (from PI/open), severity WARNING, subsystem SMM
Full details have been directed to: /usr/isys/&PILOG&/WARN.1
*** Status 12940 (from PI/open), severity WARNING, subsystem SMM
Full details have been directed to: /usr/isys/&PILOG&/WARN.2
Exiting PI/open


Looking at the details in &PILOG& file I see the following error
messages:

In /usr/isys/&PILOG&/WARN.0
...
*** Status 2 (OS: No such file or directory), severity WARNING
Detected by the STARTUP subsystem in st_get_limits at location 3.


In /usr/isys/&PILOG&/WARN.1
...
*** Status 12940 (from PI/open), severity WARNING
Detected by the SMM subsystem in sm_inits at location 0.
=> Unable to allocate 154208 bytes of shared memory.
System maximum is set to 0

Called from st_cold_boot at location 1.
=> error doing shared initialisation of shared memory subsystem


In /usr/isys/&PILOG&/WARN.2
...*** Status 12940 (from PI/open), severity WARNING
Detected by the SMM subsystem in st_bproc at location 29.
=> bootstrap processor error doing a cold boot of PI


The error messages seem to point to HP-UX configurable kernel
parameter shmmax, which sets the maximum size of the shared memory
segment for the system. I have increased shmmax to the maximum
allowed value (1073741824 bytes), but it makes no difference to
piopen.

I have played with PI/open boot.params file, increasing and decreasing
CS_BYTES (which defines shared memory catalog space) and DIO_BYTES
(which defines shared memory for disk I/O subsystem tables), but
nothing makes a difference to piopen.

I have checked all the HP-UX and PI/open system configuration
parameters I could think of.

I have tried making all the parameters identical to the existing PI/
open production server, which is running successfully, but I still run
into the same problem on the test server.

The message (OS: No such file or directory) in &PILOG& WARN.0 is
obviously suspicious, but I have no indication what file or directory
it refers to.

Can anyone with experience installing PI/open make any suggestions?

Thank you in advance,

Natasha Zagsky
zag...@hotmail.com

Natasha Zagsky

unread,
Jul 22, 2010, 4:55:37 PM7/22/10
to
The solution, as described in the PI/open installation readme
instructions and as suggested by Henry Unger of Hitech Systems, Inc.
through the U2-Users mailing list, was to create a proper UNIX
symbolic link for /hp-ux:

[/] # ln -s /stand/vmunix /hp-ux

[/] # ls -l /hp-ux
lrwxrwxrwx 1 root sys 13 Jul 22 14:26 /hp-ux -> /stand/vmunix

After the link was created, the PI/open installation continued
successfully.

Natasha Zagsky
zag...@hotmail.com

0 new messages