pids_list: The specified subscript cannot be greater than 1024

[Lakshmikanth Baddam]

when i try to start a PKG on one node i am getting this message in the PKG log file...i have verified it many times..but...

/etc/cmcluster/DBPKG/DBPKG.sh[226]: pids_list: The specified subscript cannot be
greater than 1024.

any suggestions

[melvyn burnard]

you need to look for pids_list in the shell script and see what it is looking at

[melvyn burnard]

I would possibly add a set -x to the top of your conttrol script and see if that helps pinpoint where this error is occuring, otherwise log a call with your local HP Response Centre

[James R. Ferguson]

Hi:

Look around line number 226 in the script. It appears that the script is trying to assign more than 1024 elements to an array in a 'set' statement like:

# set -A pids_list ...

The shell restricts subscripts for arrays to the range 0..1023.

Regards!

...JRF...

[Lakshmikanth Baddam]

This is the below lines in the PKG.sh file..

222 # completed.
223 #
224 # To allow mirror resynchronization to ocurr in parallel with
225 # the package startup, uncomment the line
226 # VXVOL="vxvol -g \$DiskGroup -o bg startall" and comment out the defaul
t.
227 #
228 # VXVOL="vxvol -g \$DiskGroup -o bg startall"
229 VXVOL="vxvol -g \$DiskGroup startall" # Default
230
231 # FILESYSTEM UNMOUNT COUNT
232 # Specify the number of unmount attempts for each filesystem during pack
age
233 # shutdown. The default is set to 1.

[James R. Ferguson]

Hi (again):

If the line in question occurs within a function in the script at large, the reported line number will be relative to the beginning of that function. As Melvyn suggested, start by looking for 'pids_list'. Then look for a 'set' statement somewhere around line #226 of some function (subroutine).

Regards!

...JRF...

[Mike Chisholm]

Also, if you choose to try to debug this with a "set -x" keep in mind that you need to put the "set -x" statement right after the opening curly brace in the function(s) that you are interesting in tracing. A global "set -x" at the beginning of the control script will not display debug data inside a function. The four functions I can find that reference the pids_list variable are:
function activate_volume_group
function check_and_mount
function umount_fs
function deactivate_volume_group

Probably only the first two are relevant at package startup.

[Lakshmikanth Baddam]

Thanks to all It's working fine.

[James R. Ferguson]

Hi (again):

...so what was your solution? If we helped, what pointed you in the direction you took and most importantly, what did you do to correct your problem?

...JRF...

[Lakshmikanth Baddam]

Actually we had some syntax wrong in the script. just rectified it. It worked.

[Lakshmikanth Baddam]

it solved my problem.