Red Hat ENTERPRISE LINUX 5.5 - TECHNICAL NOTES Manual page 255

gfs2.ko has been set to use weak updates and instructs them there is a need to remove kmod-
gfs2 and reboot the system before proceeding any further.
• groupd can erroneously assign the fence domain id 00000000. This can result in LVM commands
becoming permanently locked. To alert system administrators to this issue, a check has been added
to SOS that examines the output of group_tool -v for a string of zeroes against fence and, if it
finds this to be the case, it generates a warning message that instructs administrators on how to
remedy the problem.
• SOS was inadvertently copying all subdirectories and files relative to where the command was
executed, (including paths created by symlinks), into /tmp. (This problem did not occur if absolute
link entries were used.) A change has been made so that SOS no longer traverses directories
relative to the current working directory. As a result, this potentially large amount of data is no longer
copied erroneously.
• SOS had no capability to detect or report problems with cman services, which can occur when
groupd becomes stuck in a state that needs to be resolved before cluster operations can continue.
To rectify this, SOS now checks the output of group_tool -v to detect if CMAN services are
set to anything other than none. A warning is then produced to prompt the system administrator to
investigate the cause of the potential problem.
• SOS's progress reporting was inaccurate, due to problems with output buffering and the wrong
placement of error messages. When the sosreport command was run from a terminal, the
percentage completed figure would go up and down. Furthermore, after it has reached 100%, the
real time and estimated finish time would continue to grow together for several more seconds. A
new, more reliable progress indication system has been added. As a result, the progress indication
will be reliable from now on.
• SOS would erroneously report that one or more nfs export do not have a fsid attribute set even if
the fsid had been specified in the fs resource. This was due to an omission in the cluster.py
file which was only searching the services tag and not the resources tag, in which fsid is set
(as part of best practice) if the file system is a share resource. cluster.py has now been
patched to account for all scenarios so false reports of missing fsids will no longer be generated.
1975
(BZ#507674 )
• The sosreport -k general.syslogsize=15 command did not limit log file sizes to 15
Mb, contrary to expected behavior. This was because the limits were being erroneously applied
to /var/log/messages.* instead of /var/log/messages. As a result, huge reports were
generated and sosreport could even potentially die if all space in /tmp was used by the process.
To fix this problem, the limits are now being applied to /var/log/messages meaning the huge
reports are no longer being generated.
• The list of installed RPMs generated by sosreport was in a non-standard format. Rather than in
the accepted format of name-[epoch:]version-release.arch, it was in the form of name-
version-release-arch. This was inconvenient to users wishing to paste output to programs
such as yum. To fix this issue, changes have been made to ensure that the list of installed RPMs is
now in the name-[epoch:]version-release.arch format to make it usable with yum and rpm
commands. (BZ#482755
• A problem occurred when sosreport deliberately obscured fencing passwords in /etc/
cluster/cluster.conf. It would break the XML formatting by removing the quotation marks
that surrounded the masked version of the password. A further problem was that the passwords
in backup files (such as /etc/cluster/cluster.conf.1) were not obscured. To resolve this
1971
(BZ#499468 )
1972
(BZ#530385 )
1974
(BZ#502442
(BZ#516551
1977
)
RHBA-2010:0201: bug fix and enhancement update
(BZ#507390
1973
(BZ#499472 )
)
1976
)
1970
)
245