ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

Chapter 4 Latest version informationNumber2526272829Version (indetail) Upgraded section Cause3.0.3-1 When "0" was specified for the/3.0.0-1 to 3.0.2-1 Server Sync Wait Time, the mainprocess of the cluster sometimesfailed to start.3.0.3-1 When an attempt was made to/3.0.0-1 to 3.0.2-1 perform failover between absoluteexclusion groups upon the group status.occurrence of multiple and concurrentmonitor errors, both systems weresometimes activated.When "0" (minutes) was specifiedfor the Server Sync Wait Time, thevalue of the startup wait timeoutbecame identical to that of the HBtransmission start timeout.Therefore, the startup waitprocessing was not performedappropriately because of the timingof the processing.There was an error in the design ofthe value that was returned as the3.0.3-1 The setting for forced FIP activation The setting was overwritten with/3.0.0-1 to 3.0.2-1 was ignored.another setting in theimplementation.3.0.3-1 The units of the time values to be The output conversion method was/3.0.0-1 to 3.0.2-1 displayed in the alert (syslog) for incorrect.delay warning in the user spacemonitor resources were incorrect,and the values to be displayed inunits of tick count were displayed inunits of seconds.3.0.3-1 When the size of an alert message The size of the alert message buffer/3.0.0-1 to 3.0.2-1 exceeded 512 bytes, the alert was insufficient.daemon terminated abnormally.8830 3.0.3-1/ 3.0.2-1313233343.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-13.1.0-1/ 3.0.0-1 to3.0.4-1WebManager could not be normally When terminating WebManager,terminated by selecting Exit from the the termination process of ConfigFile menu.Mode (Builder) is inadequate.Uploading is unavailable if the cluster When checking processes whilehas been suspended and a uploading, a cluster configurationtemporary suspension of a monitored file only judged whether the statusresource modified a necessary of monitor resources wasconfigurationsuspended.Sometimes unnecessary logs were After the failover destination serveroutput when an attempt was made to was decided in the first monitor errorperform failover between absolute processing, in the next monitor errorexclusion groups upon the processing, a different server wasoccurrence of multiple and concurrent decided for the failover destinationmonitor errors.server because it was determinedthat absolute exclusion groups wererunning on that server.When waiting to start monitoring a The processing for the monitor startresident monitor resource, the wait time was invalid.timeout time rather than the start waittime is referenced.An error occurred when collecting There were faults in the processinglogs, delivering settings information, that determines whether the actionor during other activities, but the was successful or nor.process appears to have terminatednormally.ExpressCluster X 3.1 for Linux Getting Started Guide