Reply To: Unable to open up Gui/network monitor after failover

[Peter Heggie]

I’m digging through this on my own right now, but it seems that whatever sites are listed in …/server/server.ini, in the keyword ‘environs=’, are being checked when ever the gui-client server is changed; we have production sites listed in there alongside the test sites, so when it checks those prod sites, it does not find the SiteInfo file (because the prod sites file system is not mounted), and therefore we get those error messages.

All that makes sense, but the hacmp cluster script ‘hci.node1.stop’ executes a perl script that updates that server.ini to set the ‘environs=’ value. I think that after that script ran, the value of the environs variable would contain the correct sites, but it did not.

Code:

node2sitelist=`ls /test/cis5.8/*/NetConfig | awk -F / ‘{print $4}’`
# leaving node2, remove node1 sites from server.ini on node2
 for hasite in $node2sitelist;do
     perl $SCRIPTDIR/hci.server.ini $HACMP_HCI_ROOT $hasite
 done

The script I think is supposed to take the name of the site being passed to it and add it to the environs variable if it is not already there. The output from that script is:

List found keep original

List found keep original

List found keep original

List found keep original

There are four test sites to pass in to this script, so the output matches what should happen. However, there seems to be nothing in the parent script that deletes the environs= entry in the first place, so it would still contain the prod sites even after a fail back. So it will always have both prod and test sites in that variable and we would always get those errors in the server.log file.

Does that make sense?

Is something supposed to clear out the environs variable before this starts?

Peter Heggie
PeterHeggie@crouse.org