[
https://issues.apache.org/jira/browse/AIRFLOW-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522618#comment-16522618
]
kunal gupta commented on AIRFLOW-2631:
--------------------------------------
[~ashb]
Here is celery version:
{color:#205081}Name: celery {color}
{color:#205081}Version: 3.1.17 {color}
{color:#205081}Summary: Distributed Task Queue {color}
{color:#205081}Home-page: http://celeryproject.org {color}
{color:#205081}Author: Ask Solem {color}
{color:#205081}Author-email: [email protected] {color}
{color:#205081}License: BSD {color}
{color:#205081}Location: /usr/lib/python2.7/site-packages {color}
{color:#205081}Requires: kombu, pytz, billiard {color}
{color:#205081}Required-by: flower{color}
here is the stacktrace:
{color:#205081}[2018-06-25 12:59:29,773] \{__init__.py:51} INFO - Using
executor CeleryExecutor{color}
{color:#205081}/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py:470:
Warning: Data truncated for column 'dttm' at row 1{color}
{color:#205081} cursor.execute(statement, parameters){color}
{color:#205081}/usr/lib/python2.7/site-packages/celery/platforms.py:766:
RuntimeWarning: You are running the worker with superuser privileges, which
is{color}
{color:#205081}absolutely not recommended!{color}
{color:#205081}Please specify a different user using the -u option.{color}
{color:#205081}User information: uid=1000770000 euid=1000770000 gid=0
egid=0{color}
{color:#205081}uid=uid, euid=euid, gid=gid, egid=egid,{color}
{color:#205081}[2018-06-25 12:59:30,625: WARNING/MainProcess]
/usr/lib/python2.7/site-packages/celery/apps/worker.py:161:
CDeprecationWarning: {color}
{color:#205081}Starting from version 3.2 Celery will refuse to accept pickle by
default.{color}
{color:#205081}The pickle serializer is a security concern as it may give
attackers{color}
{color:#205081}the ability to execute any command. It's important to
secure{color}
{color:#205081}your broker from unauthorized access when using pickle, so we
think{color}
{color:#205081}that enabling pickle should require a deliberate action and not
be{color}
{color:#205081}the default choice.{color}
{color:#205081}If you depend on pickle then you should set a setting to disable
this{color}
{color:#205081}warning and to be sure that everything will continue
working{color}
{color:#205081}when you upgrade to Celery 3.2::{color}
{color:#205081}CELERY_ACCEPT_CONTENT = ['pickle', 'json', 'msgpack',
'yaml']{color}
{color:#205081}You must only enable the serializers that you will actually
use.{color}
{color:#205081} warnings.warn(CDeprecationWarning(W_PICKLE_DEPRECATED)){color}
{color:#205081}[2018-06-25 12:59:30,983: ERROR/MainProcess] consumer: Cannot
connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection
refused.{color}
{color:#205081}Trying again in 2.00 seconds...{color}
{color:#205081}[2018-06-25 12:59:31,137] \{settings.py:174} INFO -
setting.configure_orm(): Using pool settings. pool_size=5,
pool_recycle=3600{color}
{color:#205081}[2018-06-25 12:59:31,469] \{__init__.py:51} INFO - Using
executor CeleryExecutor{color}
{color:#205081}/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py:470:
Warning: Data truncated for column 'dttm' at row 1{color}
{color:#205081} cursor.execute(statement, parameters){color}
{color:#205081}Starting flask{color}
{color:#205081}[2018-06-25 12:59:31,659] \{_internal.py:88} INFO - * Running on
http://0.0.0.0:8793/ (Press CTRL+C to quit){color}
{color:#205081}[2018-06-25 12:59:32,992: ERROR/MainProcess] consumer: Cannot
connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection
refused.{color}
{color:#205081}Trying again in 4.00 seconds...{color}
{color:#205081}[2018-06-25 12:59:37,001: ERROR/MainProcess] consumer: Cannot
connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection
refused.{color}
{color:#205081}Trying again in 6.00 seconds...{color}
{color:#205081}[2018-06-25 12:59:43,013: ERROR/MainProcess] consumer: Cannot
connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection
refused.{color}
{color:#205081}Trying again in 8.00 seconds...{color}
> Worker fails to connect with MySQL DB
> -------------------------------------
>
> Key: AIRFLOW-2631
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2631
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: Airflow 2.0, 1.10
> Reporter: kunal gupta
> Priority: Critical
>
> I have containerized Airflow webserver, scheduler, flower and worker. I'm
> using MySQL for the backend and Redis for queuing. Everytime I spin up the
> worker node it throws the error below and all the Dags are stuck in running
> status.
> Logs from the Worker Node:
> File "/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line 193,
> in __init__
> super(Connection, self).__init__(*args, **kwargs2)
> OperationalError: (_mysql_exceptions.OperationalError) (2002, "Can't connect
> to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)")
> [2018-06-15 10:21:56,005: ERROR/MainProcess] Pool callback raised exception:
> OperationalError('(_mysql_exceptions.OperationalError) (2002, "Can\'t connect
> to local MySQL server through socket \'/var/lib/mysql/mysql.sock\' (2)")',)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
