Re: Can't produce message to rabbitMQ

[Luke Bakken]

What does RabbitMQ log at the same time?

On Monday, July 22, 2024 at 3:20:00 PM UTC-7 hoct...@gmail.com wrote:

This is my code: 

```

parameters: ConnectionParameters = pika.ConnectionParameters(
host=RABBIT_MQ_HOST,
port=RABBIT_MQ_PORT,
virtual_host="/",
credentials=credentials,
heartbeat=600,
blocked_connection_timeout=300
)

if not DEBUG:
ssl_context: ssl.SSLContext = ssl.create_default_context(
cafile=certifi.where()
)
ssl_context.check_hostname = False
parameters.ssl_options = pika.SSLOptions(context=ssl_context)
self.connection: BlockingConnection = pika.BlockingConnection(parameters)
self.channel: BlockingChannel = self.connection.channel()

self.channel.basic_publish(
exchange=self.exchange_name, routing_key=routing_key, body=message
)

```

This is the error I catched:

DEBUG:pika.adapters.select_connection:Using EPollPoller
DEBUG:pika.adapters.base_connection:Created default connection workflow <pika.adapters.utils.connection_workflow.AMQPConnectionWorkflow object at 0x7f68c44c7460>
DEBUG:pika.adapters.utils.connection_workflow:Starting AMQP Connection workflow asynchronously.
DEBUG:pika.adapters.select_connection:call_later: added timeout <pika.adapters.select_connection._Timeout object at 0x7f68c44c7430> with deadline=2366.154125874 and callback=functools.partial(<bound method AMQPConnectionWorkflow._start_new_cycle_async of <pika.adapters.utils.connection_workflow.AMQPConnectionWorkflow object at 0x7f68c44c7460>>, first=True); now=2366.154125874; delay=0
DEBUG:pika.adapters.utils.connection_workflow:Beginning a new AMQP connection workflow cycle; attempts remaining after this: 0
DEBUG:pika.adapters.select_connection:call_later: added timeout <pika.adapters.select_connection._Timeout object at 0x7f68c44c73d0> with deadline=2366.154204945 and callback=<bound method AMQPConnectionWorkflow._try_next_config_async of <pika.adapters.utils.connection_workflow.AMQPConnectionWorkflow object at 0x7f68c44c7460>>; now=2366.154204945; delay=0
DEBUG:pika.adapters.utils.connection_workflow:_try_next_config_async: 'b-8fd9f262-f427-4b71-9309-b345483051b7.mq.ap-southeast-1.amazonaws.com':5671
DEBUG:pika.adapters.select_connection:add_callback_threadsafe: added callback=<bound method _AddressResolver._dispatch_result of <pika.adapters.utils.selector_ioloop_adapter._AddressResolver object at 0x7f68c44c73a0>>
DEBUG:pika.adapters.select_connection:process_timeouts: invoking callback=<bound method _AddressResolver._dispatch_result of <pika.adapters.utils.selector_ioloop_adapter._AddressResolver object at 0x7f68c44c73a0>>
DEBUG:pika.adapters.utils.selector_ioloop_adapter:Invoking asynchronous getaddrinfo() completion callback; host='b-8fd9f262-f427-4b71-9309-b345483051b7.mq.ap-southeast-1.amazonaws.com'
DEBUG:pika.adapters.utils.connection_workflow:getaddrinfo returned 1 records
DEBUG:pika.adapters.utils.connection_workflow:Attempting to connect using address record (<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('52.220.126.203', 5671))
INFO:pika.adapters.utils.connection_workflow:Pika version 1.3.2 connecting to ('52.220.126.203', 5671)
DEBUG:pika.adapters.select_connection:add_callback_threadsafe: added callback=<bound method _AsyncSocketConnector._start_async of <pika.adapters.utils.io_services_utils._AsyncSocketConnector object at 0x7f68c44c79d0>>
DEBUG:pika.adapters.select_connection:call_later: added timeout <pika.adapters.select_connection._Timeout object at 0x7f68c44c72b0> with deadline=2376.292268562 and callback=<bound method AMQPConnector._on_tcp_connection_timeout of <pika.adapters.utils.connection_workflow.AMQPConnector object at 0x7f68c44c7a00>>; now=2366.292268562; delay=10.0
DEBUG:pika.adapters.select_connection:call_later: added timeout <pika.adapters.select_connection._Timeout object at 0x7f68c44c7a90> with deadline=2381.292380952 and callback=<bound method AMQPConnector._on_overall_timeout of <pika.adapters.utils.connection_workflow.AMQPConnector object at 0x7f68c44c7a00>>; now=2366.292380952; delay=15.0
DEBUG:pika.adapters.select_connection:process_timeouts: invoking callback=<bound method _AsyncSocketConnector._start_async of <pika.adapters.utils.io_services_utils._AsyncSocketConnector object at 0x7f68c44c79d0>>
DEBUG:pika.adapters.utils.selector_ioloop_adapter:SelectorIOServicesAdapter.set_writer(24, <bound method _AsyncSocketConnector._on_writable of <pika.adapters.utils.io_services_utils._AsyncSocketConnector object at 0x7f68c44c79d0>>)
DEBUG:pika.adapters.utils.selector_ioloop_adapter:set_writer(24, _) added handler Wr
DEBUG:pika.adapters.utils.io_services_utils:Connection-establishment is in progress for <socket.socket fd=24, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.31.193.21', 39674)>.
INFO:pika.adapters.utils.io_services_utils:Socket connected: <socket.socket fd=24, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.31.193.21', 39674), raddr=('52.220.126.203', 5671)>
DEBUG:pika.adapters.utils.io_services_utils:_AsyncSocketConnector._report_completion(None); <socket.socket fd=24, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.31.193.21', 39674), raddr=('52.220.126.203', 5671)>
DEBUG:pika.adapters.utils.selector_ioloop_adapter:SelectorIOServicesAdapter.remove_writer(24)
DEBUG:pika.adapters.utils.selector_ioloop_adapter:remove_writer(24) removed handler
DEBUG:pika.adapters.select_connection:remove_timeout: removing timeout <pika.adapters.select_connection._Timeout object at 0x7f68c44c72b0> with deadline=2376.292268562 and callback=<bound method AMQPConnector._on_tcp_connection_timeout of <pika.adapters.utils.connection_workflow.AMQPConnector object at 0x7f68c44c7a00>>
DEBUG:pika.adapters.utils.connection_workflow:TCP connection to broker established: <socket.socket fd=24, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.31.193.21', 39674), raddr=('52.220.126.203', 5671)>.
DEBUG:pika.adapters.utils.io_services_utils:_AsyncStreamConnector.start(); <socket.socket fd=24, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.31.193.21', 39674), raddr=('52.220.126.203', 5671)>
DEBUG:pika.adapters.select_connection:add_callback_threadsafe: added callback=<bound method _AsyncStreamConnector._start_async of <pika.adapters.utils.io_services_utils._AsyncStreamConnector object at 0x7f68c44c7a30>>
DEBUG:pika.adapters.select_connection:process_timeouts: invoking callback=<bound method _AsyncStreamConnector._start_async of <pika.adapters.utils.io_services_utils._AsyncStreamConnector object at 0x7f68c44c7a30>>
DEBUG:pika.adapters.utils.io_services_utils:_AsyncStreamConnector._start_async(); <socket.socket fd=24, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.31.193.21', 39674), raddr=('52.220.126.203', 5671)>
DEBUG:pika.adapters.utils.io_services_utils:_AsyncStreamConnector._linkup()
DEBUG:pika.connection:New Connection state: CLOSED (prev=CLOSED)

[Võ Học Thức]

  This problem has been fixed. Please delete the post.  

Vào lúc 08:42:17 UTC+7 ngày Thứ Ba, 23 tháng 7, 2024, luker...@gmail.com đã viết: