RabbitMQ Crash on CentOS6 - works great on Ubuntu... AMQPTimeoutException

173 views
Skip to first unread message

Micheal Shallop

unread,
Jun 19, 2015, 5:50:21 PM6/19/15
to php-amqp...@googlegroups.com
Hey...

I have a long-time working RMQ deployment with PHP consumers.

Recently (like a day ago) I deployed the code base to a CentOS6.6 platform.  (Not by choice)

I am using RabbitMQ 3.5.3 with Erlang 17.5 on CentOS.... on Ubuntu, I am using RabbitMQ 3.5.3 with Erlang R16B03

Services start normally, but whenever a single request hits the wire, the PHP consumers crash.  I see the following in the PHP error log:

[19-Jun-2015 14:00:47 America/Los_Angeles] PHP Fatal error:  Uncaught exception 'PhpAmqpLib\Exception\AMQPTimeoutException' with message 'Error sending data. Socket connection timed out' in /home/atladmin/aura-ds/lib/vendor/videlalvaro/php-amqplib/PhpAmqpLib/Wire/IO/StreamIO.php:194
Stack trace:
#0 /home/atladmin/aura-ds/lib/vendor/videlalvaro/php-amqplib/PhpAmqpLib/Connection/AbstractConnection.php(335): PhpAmqpLib\Wire\IO\StreamIO->write('\x01\x00\x00\x00\x00\x00\v\x00\n\x002\x00\x00\x00\x00...')
#1 /home/atladmin/aura-ds/lib/vendor/videlalvaro/php-amqplib/PhpAmqpLib/Connection/AbstractConnection.php(452): PhpAmqpLib\Connection\AbstractConnection->write('\x01\x00\x00\x00\x00\x00\v\x00\n\x002\x00\x00\x00\x00...')
#2 /home/atladmin/aura-ds/lib/vendor/videlalvaro/php-amqplib/PhpAmqpLib/Channel/AbstractChannel.php(199): PhpAmqpLib\Connection\AbstractConnection->send_channel_method_frame(0, Array, Object(PhpAmqpLib\Wire\AMQPWriter))
#3 /home/atladmin/aura-ds/lib/vendor/videlalvaro/php-amqplib/PhpAmqpLib/Connection/AbstractConnection.php(631): PhpAmqpLib\Channel\AbstractCh in /home/atladmin/aura-ds/lib/vendor/videlalvaro/php-amqplib/PhpAmqpLib/Wire/IO/StreamIO.php on line 194


There are no errors in the rabbitMQ logs...

=INFO REPORT==== 19-Jun-2015::13:59:24 ===
Server startup complete; 7 plugins started.
 * rabbitmq_management
 * rabbitmq_web_dispatch
 * webmachine
 * mochiweb
 * rabbitmq_management_agent
 * amqp_client
 * rabbitmq_auth_mechanism_ssl
=INFO REPORT==== 19-Jun-2015::13:59:37 ===
accepting AMQP connection <0.314.0> (127.0.0.1:43396 -> 127.0.0.1:5671)
=INFO REPORT==== 19-Jun-2015::13:59:37 ===
closing AMQP connection <0.314.0> (127.0.0.1:43396 -> 127.0.0.1:5671)
=INFO REPORT==== 19-Jun-2015::13:59:37 ===
accepting AMQP connection <0.329.0> (127.0.0.1:43399 -> 127.0.0.1:5671)
=INFO REPORT==== 19-Jun-2015::13:59:38 ===
accepting AMQP connection <0.339.0> (127.0.0.1:43401 -> 127.0.0.1:5671)
=INFO REPORT==== 19-Jun-2015::13:59:38 ===
accepting AMQP connection <0.343.0> (127.0.0.1:43403 -> 127.0.0.1:5671)
=INFO REPORT==== 19-Jun-2015::14:00:47 ===
accepting AMQP connection <0.422.0> (127.0.0.1:43415 -> 127.0.0.1:5671)
=INFO REPORT==== 19-Jun-2015::14:00:47 ===
closing AMQP connection <0.329.0> (127.0.0.1:43399 -> 127.0.0.1:5671)
=INFO REPORT==== 19-Jun-2015::14:00:47 ===
closing AMQP connection <0.422.0> (127.0.0.1:43415 -> 127.0.0.1:5671)


I am connecting using amqp/ssl over the default port 5671

This deployment works on Ubuntu release 14.04 and 15.04 on local hosts and in AWS land.  It's only when I ported everything over to CentOS 6.6 that things started to fail.  Again, this is the same code base and same /etc/rabbitmq configuration.  AMQP vendor libs built via composer...


The first-question is:  is this because of the Erlang release mismatch?  (17.5 on CentOS vs. R16B03 on Ubuntu)

Don't really have a second question because, stuck...

Any advice/help/tips greatly appreciated...

thanks!


Reply all
Reply to author
Forward
0 new messages