I used a cluster.conf similar to that provided by Chris:
With such config file modcluster crashed immediately upon start while parsing the local cluster.con.
#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
Fix should probably be the same as in ricci (attachment 648116 [details]) in bug 877381.
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.