Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I used a cluster.conf similar to that provided by Chris:
https://bugzilla.redhat.com/show_bug.cgi?id=815752#c5
With such config file modcluster crashed immediately upon start while parsing the local cluster.con.
GDB backtrace:
#0 File::read (this=0x7ffff7fe8280) at File.cpp:144
#1 0x00000000004231e9 in File::operator String const (this=<value optimized out>) at File.cpp:215
#2 0x0000000000438593 in readXML (filename=<value optimized out>) at XML.cpp:303
#3 0x000000000040e8b3 in ClusterMonitoring::Monitor::parse_cluster_conf (this=<value optimized out>) at Monitor.cpp:304
#4 0x000000000040fb93 in ClusterMonitoring::Monitor::get_local_info (this=0x7fffffffe280, nodename="", clustername="", msg="") at Monitor.cpp:199
#5 0x0000000000411aaf in ClusterMonitoring::Monitor::run (this=0x7fffffffe280) at Monitor.cpp:98
#6 0x000000000042cd7a in start_thread (thread_obj=<value optimized out>) at Thread.cpp:31
#7 0x000000324ca07851 in start_thread (arg=0x7ffff7fe9700) at pthread_create.c:301
#8 0x000000324c2e890d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
# rpm -q modcluster
modcluster-0.16.2-19.el6.x86_64
Fix should probably be the same as in ricci (attachment 648116[details]) in bug 877381.
Comment 5Jan Pokorný [poki]
2012-12-10 18:45:16 UTC
BTW., both modclusterd and modcluster (from the same modcluster subpackage)
are affected as they both link with the same culprit module.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0469.html