On Tue, 2011-11-29 at 15:00 +0000, Gordon Sim wrote: > On 11/28/2011 04:26 PM, Cajus Pollmeier wrote: > > Hiho, > > > > has anyone already seen this kind of error when running the tests? > > > > 8<------ > > make check-TESTS > > make[4]: Entering directory `/«PKGBUILDDIR»/src/tests' > > > > 0% 10 20 30 40 50 60 70 80 90 100% > > |----|----|----|----|----|----|----|----|----|----| > > Running 323 test cases... > > unknown location(0): fatal error in "testSimpleSendReceive": > > std::exception: Failed to connect (reconnect disabled) > > *unknown location(0): fatal error in "testSyncSendReceive": > > std::exception: Failed to connect (reconnect disabled) > > unknown location(0): fatal error in "testSendReceiveHeaders": > > std::exception: Failed to connect (reconnect disabled) > > unknown location(0): fatal error in "testSenderError": std::exception: > > Failed to connect (reconnect disabled) > > unknown location(0): fatal error in "testReceiverError": std::exception: > > Failed to connect (reconnect disabled) > > unknown location(0): fatal error in "testSimpleTopic": std::exception: > > Failed to connect (reconnect disabled) > > Could it be a firewall issue? Did _all_ the tests fail or only a selection?
imo this seems unlikely, it seems more like a SASL configuration issue to me, however see below. > > > 8<------ > > > > src/tests/qpidd.log contains: > > > > 2011-11-28 15:49:33 notice SASL disabled: No Authentication Performed > > 2011-11-28 15:49:33 notice Listening on TCP port 51093 > > 2011-11-28 15:49:33 notice Broker running > > 2011-11-28 15:49:36 warning Client closed connection with 501: > > internal-error: Sasl error: SASL(0): successful result: > > (qpid/SaslFactory.cpp:223) > > 2011-11-28 15:49:38 warning Client closed connection with 501: > > internal-error: Sasl error: SASL(0): successful result: > > (qpid/SaslFactory.cpp:223) > > 2011-11-28 15:49:39 warning Client closed connection with 501: > > internal-error: Sasl error: SASL(0): successful result: > > (qpid/SaslFactory.cpp:223) > > 2011-11-28 15:49:39 warning Client closed connection with 501: > > internal-error: Sasl error: SASL(0): successful result: > > (qpid/SaslFactory.cpp:223) > > 2011-11-28 15:49:41 warning Client closed connection with 501: > > internal-error: Sasl error: SASL(0): successful result: > > (qpid/SaslFactory.cpp:223) > > 2011-11-28 15:49:43 warning Client closed connection with 501: > > internal-error: Sasl error: SASL(0): successful result: > > (qpid/SaslFactory.cpp:223) > > 2011-11-28 15:49:44 notice Shut down > > > > A full build log is attached. > > > > Any ideas? > > That's a strange message, I can't think what scenario would cause that. > Does a simple connection test work ok on the box? I think the significant thing here is that authentication is turned off, but SASL is still rejecting the connection somehow. That message is coming from a failure of sasl_client_new(), but if authentication is turned off I don't see that it should be called at all. Perhaps (just musing here) the client and server mechanisms don't match and that is checked even if authentication is turned off. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
