ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

System requirements for WebManager MobileNumberVersion (indetail) Upgraded section Cause99 3.1.1-1/ 3.1.0-1100 3.1.1-1/ 3.1.0-11011021031041053.1.0-1/ 3.0.0-1 to3.0.4-1If the monitoring level is level 2 and The action to be taken when there isno records were created at creation of no record when reading data from aa table for monitoring, the database by select during level 2PostgreSQL monitor resource might monitoring was not defined.abnormally terminate.When Database Agent detected a The retry process after a monitoringtimeout, monitoring was immediately timeout was not considered.retried without waiting for the monitoringinterval.It might fail to start a specific monitor There was a variable that had notresource for the first time, causing a been initialized.monitor error.In a specific machine environment,this might occur for an ARP monitorresource, DDNS monitor resource,mirror disk monitor resource, mirrordisk connect monitor resource, hybriddisk monitor resource, hybrid diskconnect monitor resource, messagereceive monitor resource, and virtualIP monitor resource.When the cluster was resumed from The message text was not correct.WebManager, Failed to resume wasmistakenly displayed instead of The3.1.3-1/ request to resume the cluster3.1.0-1 to 3.1.1-1 failed on some servers.This occurred when the cluster wasforcibly suspended and then resumedwith some servers stopped.After the ExpressCluster Web Alert The buffer area used to readservice might abnormally terminate, /proc/pid/cmdline wasthis service might start.insufficient, or strerr(), whichWhen the ExpressCluster Web Alert was not thread-safe, was3.1.3-1/service was killed for some reason, sometimes used by multiple3.0.0-1 to 3.1.1-1this infrequently occurred at the next threads.service startup. Also, this mightinfrequently occur in normaloperation.Mirror recovery might fail immediately Even if data was sent through an oldafter the processing started, and then connection before disconnectionauto mirror recovery might start. occurred, a send error might not3.1.3-1/ This might occur when the mirror disk occur.3.0.0-1 to 3.1.1-1 connect was recovered from Also, there might be a gap in timingdisconnection.of communication recoverydetection between an active serverand a stand-by server.In SuSE11 environments, an internal The method to create a socket waslog was not output when UDP was set inadequate.3.1.3-1/ to a log communication method.3.0.0-1 to 3.1.1-1 This occurred when UDP was set to alog communication method inSuSE11 environments.Section II Installing ExpressCluster95