what you suggested is what i am doing already: /sbin/service corosync start, then qpidd -d --config=/etc/qpid/qpid.conf --cluster-name=QpidCL
are there other qpid options i should be using? how does qpid know how to reach the corosync cluster? maybe it is using another config file than what the corosync service is using? when i gdb-ed into qpid source it looped on cpg_initialize(), i guess it is part of corosync libs and knows how it is configured, but.. this is my qpid.conf: port=4672 auth=yes data-dir=/etc/qpid/data/ log-time=yes trace=yes log-to-file=/etc/qpid/qpidd.log acl-file=/etc/qpid/acl_list.acl load-module=/usr/local/lib/qpid/daemon/msgstore.so sasl-config=/etc/qpid/sasl.conf using 'cluster-name' inside or outside the conf makes no difference -- View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/qpid-clustering-Failed-to-initialize-CPG-tp6348587p6350890.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
