M4MController / backend

1 stars 0 forks source link

Rabbitmq Consumer отваливается по timeout. #5

Open wolf1996 opened 6 years ago

wolf1996 commented 6 years ago

Есть проблема с heartbeat. И timeout для reciever сервиса. log

ERROR:pika.adapters.base_connection:Socket Error: 104
INFO:pika.connection:Disconnected from RabbitMQ at rabbitmq:5672 (-1): ConnectionResetError(104, 'Connection reset by peer')
DEBUG:pika.heartbeat:Removing timeout for next heartbeat interval
DEBUG:pika.adapters.select_connection:remove_timeout: removed 4140977999462715898
DEBUG:pika.channel:Handling meta-close on <Channel number=1 OPEN conn=<SelectConnection CLOSED socket=None params=<ConnectionParameters host=rabbitmq port=5672 virtual_host=/ ssl=False>>>
DEBUG:pika.callback:Processing 1:_on_channel_cleanup
DEBUG:pika.callback:Processing use of oneshot callback
DEBUG:pika.callback:0 registered uses left
DEBUG:pika.callback:Removing callback #0: {'callback': <bound method Connection._on_channel_cleanup of <SelectConnection CLOSED socket=None params=<ConnectionParameters host=rabbitmq port=5672 virtual_host=/ ssl=False>>>, 'one_shot': True, 'only': <Channel number=1 CLOSED conn=<SelectConnection CLOSED socket=None params=<ConnectionParameters host=rabbitmq port=5672 virtual_host=/ ssl=False>>>, 'arguments': None, 'calls': 0}
DEBUG:pika.callback:Calling <bound method Connection._on_channel_cleanup of <SelectConnection CLOSED socket=None params=<ConnectionParameters host=rabbitmq port=5672 virtual_host=/ ssl=False>>> for "1:_on_channel_cleanup"
DEBUG:pika.connection:Removed channel 1
DEBUG:pika.callback:Clearing out '1' from the stack
DEBUG:pika.callback:Processing 0:_on_connection_closed
DEBUG:pika.callback:Calling <bound method _CallbackResult.set_value_once of <pika.adapters.blocking_connection._CallbackResult object at 0x7f0b430c9588>> for "0:_on_connection_closed"
DEBUG:pika.callback:Added: {'callback': <bound method Connection._on_connection_start of <SelectConnection CLOSED socket=None params=<ConnectionParameters host=rabbitmq port=5672 virtual_host=/ ssl=False>>>, 'one_shot': True, 'only': None, 'arguments': None, 'calls': 1}
DEBUG:pika.callback:Incremented callback reference counter: {'callback': <bound method Connection._on_connection_close of <SelectConnection CLOSED socket=None params=<ConnectionParameters host=rabbitmq port=5672 virtual_host=/ ssl=False>>>, 'one_shot': True, 'only': None, 'arguments': None, 'calls': 2}
ERROR:pika.adapters.blocking_connection:Connection close detected; result=BlockingConnection__OnClosedArgs(connection=<SelectConnection CLOSED socket=None params=<ConnectionParameters host=rabbitmq port=5672 virtual_host=/ ssl=False>>, reason_code=-1, reason_text="ConnectionResetError(104, 'Connection reset by peer')")
ERROR:flask.app:failed to connect (-1, "ConnectionResetError(104, 'Connection reset by peer')")
INFO:werkzeug:172.17.0.1 - - [21/May/2018 11:34:26] "POST /sensor.addRecord HTTP/1.1" 500 -
wolf1996 commented 6 years ago

В общем сделал хотфикс. Вынес всё в отдельный реконнект. и переподключаться по ошибке. Надо вынести это всё в отдельную асинхронщину. Правка на уровне синей изоленты.