Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of fraser.adams@blueyonder.co.uk
 designates 81.103.221.48 as permitted sender)
Message-ID: <51509DD3.8020503@blueyonder.co.uk>
Date: Mon, 25 Mar 2013 18:56:19 +0000
From: Fraser Adams <fraser.adams@blueyonder.co.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: "users@qpid.apache.org" <users@qpid.apache.org>
Subject: Re: Ubuntu cmake woes - update 0.20 works, trunk still broken!!
References: <514DDF07.4030500@blueyonder.co.uk>
 <514DE9D2.2050808@blueyonder.co.uk>
In-Reply-To: <514DE9D2.2050808@blueyonder.co.uk>
Content-Type: multipart/alternative;
 boundary="------------060505090403080407030800"

--------------060505090403080407030800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

This thread went quiet at the weekend :-)

does anyone have any thoughts on the "Bad argument: 
|cluster-mechanism=DIGEST-MD5 ANONYMOUS|" issue. As I say below when I 
did cmake on 0.20 I had a working install once I'd worked out the sudo 
ldconfig thing but cmake of 0.21 on trunk gives an install that barfs 
with that error.

I can't believe I'm the only one seeing that at the moment??

Frase


On 23/03/13 17:43, Fraser Adams wrote:
> On 23/03/13 16:57, Fraser Adams wrote:
>> Hello again.
>> one interesting thing I've just noticed is that if I manually do:
>>
>> sudo ldconfig
>>
>> then qpidd stops barfing with "qpidd: error while loading shared 
>> libraries: libqpidbroker.so.2.0.0: cannot open shared object file: No 
>> such file or directory" yay!!
>>
> Aha!!!!
>
> So an update to the update :-)
>
> In order to rule things out I cleaned everything up using the sudo 
> xargs rm < install_manifest.txt thing then I took a *clean* 
> qpid-0.20.tar.gz, unpacked it and did the cmake process in there.
>
> now I still needed to manually do "sudo ldconfig" after I ran "sudo 
> make install", but after that I did:
> qpidd
> 2013-03-23 17:28:57 [Store] warning Message store plugin: No storage 
> providers available.
> 2013-03-23 17:28:57 [Network] notice Listening on TCP/TCP6 port 5672
> 2013-03-23 17:28:57 [HA] notice Broker: Initializing: zappa:5672(joining)
> 2013-03-23 17:28:57 [Broker] notice Broker running
>
> so, yippee!!!!!!!! - apart from the "sudo ldconfig" quirk that's a 
> fairly clean cmake build of qpid 0.20 giving the same result I got 
> with automake, result!!! :-)
>
>
> So it looks like somebody has broken something on trunk :'( does 
> anyone want to own up to doing something that causes
> qpidd to barf with
>
> 2013-03-23 16:55:13 [Broker] critical Unexpected error: Error in 
> configuration file /usr/local/etc/qpid/qpidd.conf: Bad argument: 
> |cluster-mechanism=DIGEST-MD5 ANONYMOUS|
>
> on trunk???
>
> Ah well, some progress at least.
> Frase
>
>
>


--------------060505090403080407030800--