SGcluster: subscript out of range

[siva0123]

Hi All,

I am facing problem in starting a cluster package: Please can any body help me..

[svrut01a:root:/etc/cmcluster/CRR]cmrunpkg dbCRR
Running package dbCRR on node svrut01a
The package script for dbCRR failed with no restart. dbCRR should not be restarted
Unable to run package dbCRR on node svrut01a
Check the syslog and pkg log files for more detailed information
cmrunpkg: Unable to start some package or package instances

cluster log file:

/etc/cmcluster/CRR/dbCRR.cntl[233]: pids_list: subscript out of range

Regards,

 Druva

[siva0123]

Hi,

Please can anybody help on this.

Any comment which can make sense for the following issue will be rewarded by points. :-)

Regards,

 Druva

[Dennis Handly]

What changed?  Did it ever work?

Perhaps it is time to talk to Support?

[donna hofmeister]

these two lines...

Check the syslog and pkg log files for more detailed information
/etc/cmcluster/CRR/dbCRR.cntl[233]: pids_list: subscript out of range

...are probably a big hint.  the last line in particular looks like an implementation error.

[Dennis Handly]

>the last line in particular looks like an implementation error.

/etc/cmcluster/CRR/dbCRR.cntl[233]: pids_list: subscript out of range

Ah yes.  It appears to be a shell limitation, a real shell array can't have more than 1024 elements, too many PIDs.

Looking at line 233 of /etc/cmcluster/CRR/dbCRR.cntl may be helpful.

[siva0123]

Thanks for the commets..

I have checked the syslog there are no clue..

If i have change the shell value to accept more than 1024.. how can i do it..

Thanks,

 Druva

[Dennis Handly]

>If I have change the shell value to accept more than 1024.. how can I do it?

You can't, that's what limitation means.

If dbCRR.cntl is your script, you could port the code to perl which doesn't have the limitation.

Or rewrite the script to use a different algorithm.  Possibly multiple arrays or some type of filtering of the PIDs before you put them in the array.

Can you provide dbCRR.cntl or the fragment around line 233.

[Stephen Doud]

I have seen this error before but did not document the cause unfortunately.

I am fairly certain there is a problem with the package control script, such as a missing quotation mark on a line defining a package-specific parameter such as a VG name, floating IP etc.

If the package runs on another node, cksum the script on both nodes and compare the results.  A difference should be investigated.

[Dennis Handly]

>I am fairly certain there is a problem with the package control script, such as a missing quotation mark

If these are real shell scripts, perhaps syntax checking them may help?

sh -n script