ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

System requirements for WebManager MobileNumberVersion (indetail) Upgraded section Cause77 3.1.1-1/ 3.0.0-1 to3.1.0-178 3.1.1-1/ 3.0.0-1 to3.1.0-179 3.1.1-1/ 3.0.0-1 to3.1.0-180 3.1.1-1/ 3.1.0-181 3.1.1-1/ 3.0.0-1 to3.1.0-182 3.1.1-1/ 3.0.0-1 to3.1.0-183 3.1.1-1/ 3.1.0-184 3.1.1-1/ 3.1.0-185 3.1.1-1/ 3.0.0-1 to3.1.0-186 3.1.1-1/ 3.0.0-1 to3.1.0-187 3.1.1-1/ 3.0.0-1 to3.1.0-1After collecting logs, the files that For SuSE Linux, the tar commandmust be deleted might remain. options were not considered.If the VM license is used, an The message that was notunnecessary alert might be output necessary to output when using thewhen starting the cluster.VM license has been output.If the configuration data is uploaded The file that defines the method towith clearing the default resource reflect changes is inadequate.dependency and without specifyingany dependencies, only the clustersuspend is requested even if it isnecessary to stop a group.If the smart failover is set and When allocating the resource datamemory is insufficient when starting storage area failed, an illegalthe cluster, the clprc process might memory access occurs due to theabnormally terminate and the server API allocation request.might be shut down.WebManager might abnormally Since the size of the temporaryterminate if there is a lot of buffer is fixed to 4096 bytes, aninformation to be displayed for illegal memory access occurs ifWebManager because there are a lot there is information exceeding 4096of servers.bytes.When the setting to start the The monitor processes ofWebManager service and WebAlert WebManager service and WebAlertservice is disabled, the alert service did not consider the settingindicating that starting the to disable the WebManager serviceWebManager service and WebAlert and WebAlert service to start.service failed at OS startup might beoutput.The description (in English) of rc In the current description, “hasmessage ID=26 was not correct. started” was used, but, “has beencompleted” is correct.The correct method to reflect the The file that defines the method toadded group resource is reflect changes was inadequate.“stopping/suspending the group”, but“stopping the cluster” was performed.The warning dialog box might be The process to check thedisplayed when uploading configuration data ID did notconfiguration data in an environment consider old configuration data.of which ExpressCluster X wasupgraded from 2.x to3.x.The file descriptor used by the clprc The process to close the fileprocess might leak if WebManager descriptor might not be performed.was frequently updated or clpstatwas frequently executed.When a valid COM heartbeat device The status setting process atname was specified in the blank field, resuming the cluster was notthe system prompted to suspend and correct.resume the cluster. In this case, if thecluster was not stopped, the COMheartbeat did not operate properly.Section II Installing ExpressCluster93