qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mansour Al Akeel <mansour.alak...@gmail.com>
Subject Re: Runnig python examples
Date Thu, 11 Jun 2015 15:09:51 GMT
I restarted the server, but still no juice !
is there a way I can tell proton to use AMPQ 0-9 or 0-10 ?

I think reverting back to a previous version should solve my problems for now !



On Thu, Jun 11, 2015 at 6:52 PM, Gordon Sim <gsim@redhat.com> wrote:
> On 06/11/2015 03:28 PM, Mansour Al Akeel wrote:
>>
>> Gordon,
>> thank you.
>> I added Both Anonymous and PLAIN. Here's the steps to add them from
>> the httpManagement console:
>> -Double click "Broker" folder. Go to "Authentication Providers", and click
>> add.
>> -Fill the current information:
>> Name: anonymous
>> Type: Anonymous
>>
>> -Then did it again for Plain:
>> Name: PLAIN
>> Type: Plain
>> and added a user guest:guest
>>
>>
>> Now, went to "Broker >> Ports >> AMQP", Then " >> Edit" I changed
the
>> "Authorization Provider", once for PLAIN and for Anonymous.
>>
>> With PLAIN and client side credentials "guest:guest", I am getting on
>> the broker:
>>
>>
>> 2015-06-11 18:22:35,527 INFO  [IoReceiver - /127.0.0.1:33637]
>> (stats.StatisticsCounter) - Resetting statistics for counter:
>> messages-delivered-1-13
>> 2015-06-11 18:22:35,527 INFO  [IoReceiver - /127.0.0.1:33637]
>> (stats.StatisticsCounter) - Resetting statistics for counter:
>> data-delivered-1-14
>> 2015-06-11 18:22:35,527 INFO  [IoReceiver - /127.0.0.1:33637]
>> (stats.StatisticsCounter) - Resetting statistics for counter:
>> messages-received-1-15
>> 2015-06-11 18:22:35,527 INFO  [IoReceiver - /127.0.0.1:33637]
>> (stats.StatisticsCounter) - Resetting statistics for counter:
>> data-received-1-16
>> 2015-06-11 18:22:35,527 DEBUG [IoReceiver - /127.0.0.1:33637] (FRM) -
>> SEND[/127.0.0.1:33637|0] :
>> SaslMechanisms{saslServerMechanisms=[CRAM-MD5]}
>
>
> That looks like CRAM-MD5 is still the only option offered... did you try
> restarting the broker (I'm not sure if this is required)?
>
> [...]
>>
>> While we are on this subject, I went back and tried to reinstall
>> python-qpid-proton, getting an error when installing it. The installer
>> reports a success. However, there are some errors installing
>> python-qpid-proton:
>>
>> ===============================================
>> localhost qpid-broker # pip install python-qpid-proton
>> Downloading/unpacking python-qpid-proton
>>    Downloading python-qpid-proton-0.9.1.zip (90kB): 90kB downloaded
>>    Running setup.py
>> (path:/tmp/pip_build_root/python-qpid-proton/setup.py) egg_info for
>> package python-qpid-proton
>>
>> Installing collected packages: python-qpid-proton
>>    Running setup.py install for python-qpid-proton
>>      Did not find libqpid-proton via pkg-config:
>>
>>      Using bundled libqpid-proton
>>      fetching
>> http://www.apache.org/dist/qpid/proton/0.9.1/qpid-proton-0.9.1.tar.gz
>> into build/bundled
>>      Using openssl (found via pkg-config).
>>      cc -c /tmp/clock_getttimeuwm6XO.c -o
>> build/temp.linux-x86_64-2.7/tmp/clock_getttimeuwm6XO.o
>>      cc build/temp.linux-x86_64-2.7/tmp/clock_getttimeuwm6XO.o -o
>> build/temp.linux-x86_64-2.7/a.out
>>      build/temp.linux-x86_64-2.7/tmp/clock_getttimeuwm6XO.o: In function
>> `main':
>>      clock_getttimeuwm6XO.c:(.text+0x15): undefined reference to
>> `clock_getttime'
>
>
> That looks like it might just be a test for determining what is available.
> If the install proceeded without error after that, I would not worry about
> it.
>
>>      collect2: error: ld returned 1 exit status
>>      building 'libqpid-proton' extension
>>      x86_64-pc-linux-gnu-gcc -pthread -fPIC -Ibuild/include
>>
>> -I/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src
>>
>> -I/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/include
>> -I/usr/include/python2.7 -c /tmp/pip_build
>>
>> _root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/object/record.c
>> -o
>> build/temp.linux-x86_64-2.7/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/object/record.o
>> -std=gnu99 -Dqpid_proton_EXPORTS -DUSE_ATOLL -DUSE_CLOCK_GETT
>> IME -DUSE_STRERROR_R -DUSE_UUID_GENERATE
>>      x86_64-pc-linux-gnu-gcc -pthread -fPIC -Ibuild/include
>>
>> -I/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src
>>
>> -I/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/include
>> -I/usr/include/python2.7 -c /tmp/pip_build
>>
>> _root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/object/string.c
>> -o
>> build/temp.linux-x86_64-2.7/tmp/pip_build_root/python-qpid-proton/build/bundled/qpid-proton/proton-c/src/object/string.o
>> -std=gnu99 -Dqpid_proton_EXPORTS -DUSE_ATOLL -DUSE_CLOCK_GETT
>> IME -DUSE_STRERROR_R -DUSE_UUID_GENERATE
>> ......
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message