Databases
StackOverflow2013
Postsdbo
POCelery Flask --- error: [Errno 111] Connection refused
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCelery Flask --- error: [Errno 111] Connection refused
    primarykey
    data
    text
    <p>After running through the basic example for flask-celery(runs fine as far as I can tell) I'm trying to integrate this to my own project. Basically, I'm using this below:</p> <pre><code>from flask import Blueprint, jsonify, request, session from flask.views import MethodView from celery.decorators import task blueprint = Blueprint('myapi', __name__) class MyAPI(MethodView): def get(self, tag): return get_resource.apply_async(tag) @task(name="get_task") def get_resource(tag): pass </code></pre> <p>with the same setup as in the example, I'm getting this error:</p> <pre><code>Traceback (most recent call last): File "/x/venv/lib/python2.7/site-packages/flask/app.py", line 1518, in __call__ return self.wsgi_app(environ, start_response) File "/x/venv/lib/python2.7/site-packages/flask/app.py", line 1506, in wsgi_app response = self.make_response(self.handle_exception(e)) File "/x/venv/lib/python2.7/site-packages/flask/app.py", line 1504, in wsgi_app response = self.full_dispatch_request() File "/x/venv/lib/python2.7/site-packages/flask/app.py", line 1264, in full_dispatch_request rv = self.handle_user_exception(e) File "/x/venv/lib/python2.7/site-packages/flask/app.py", line 1262, in full_dispatch_request rv = self.dispatch_request() File "/x/venv/lib/python2.7/site-packages/flask/app.py", line 1248, in dispatch_request return self.view_functions[rule.endpoint](**req.view_args) File "/x/venv/lib/python2.7/site-packages/flask/views.py", line 84, in view return self.dispatch_request(*args, **kwargs) File "/x/venv/lib/python2.7/site-packages/flask/views.py", line 151, in dispatch_request return meth(*args, **kwargs) File "/x/api/modules/document/document.py", line 14, in get return get_resource.apply_async(tag) File "/x/venv/lib/python2.7/site-packages/celery/app/task/__init__.py", line 449, in apply_async publish = publisher or self.app.amqp.publisher_pool.acquire(block=True) File "/x/venv/lib/python2.7/site-packages/kombu/connection.py", line 657, in acquire R = self.prepare(R) File "/x/venv/lib/python2.7/site-packages/kombu/pools.py", line 54, in prepare p = p() File "/x/venv/lib/python2.7/site-packages/kombu/pools.py", line 45, in &lt;lambda&gt; return lambda: self.create_producer() File "/x/venv/lib/python2.7/site-packages/celery/app/amqp.py", line 265, in create_producer pub = self.app.amqp.TaskPublisher(conn, auto_declare=False) File "/x/venv/lib/python2.7/site-packages/celery/app/amqp.py", line 328, in TaskPublisher return TaskPublisher(*args, **self.app.merge(defaults, kwargs)) File "/x/venv/lib/python2.7/site-packages/celery/app/amqp.py", line 158, in __init__ super(TaskPublisher, self).__init__(*args, **kwargs) File "/x/venv/lib/python2.7/site-packages/kombu/compat.py", line 61, in __init__ super(Publisher, self).__init__(connection, self.exchange, **kwargs) File "/x/venv/lib/python2.7/site-packages/kombu/messaging.py", line 79, in __init__ self.revive(self.channel) File "/x/venv/lib/python2.7/site-packages/kombu/messaging.py", line 168, in revive channel = channel.default_channel File "/x/venv/lib/python2.7/site-packages/kombu/connection.py", line 581, in default_channel self.connection File "/x/venv/lib/python2.7/site-packages/kombu/connection.py", line 574, in connection self._connection = self._establish_connection() File "/x/venv/lib/python2.7/site-packages/kombu/connection.py", line 533, in _establish_connection conn = self.transport.establish_connection() File "/x/venv/lib/python2.7/site-packages/kombu/transport/amqplib.py", line 279, in establish_connection connect_timeout=conninfo.connect_timeout) File "/x/venv/lib/python2.7/site-packages/kombu/transport/amqplib.py", line 89, in __init__ super(Connection, self).__init__(*args, **kwargs) File "/x/venv/lib/python2.7/site-packages/amqplib/client_0_8/connection.py", line 129, in __init__ self.transport = create_transport(host, connect_timeout, ssl) File "/x/venv/lib/python2.7/site-packages/amqplib/client_0_8/transport.py", line 281, in create_transport return TCPTransport(host, connect_timeout) File "/x/venv/lib/python2.7/site-packages/amqplib/client_0_8/transport.py", line 85, in __init__ raise socket.error, msg error: [Errno 111] Connection refused --&gt; </code></pre> <p>I'm using redis, and if I install rabbitmq I get another error, but I do not understand this right now --the broker should be redis but its isn't finding it or what? Can anyone give me more of a clue what is going on here? Do I need to import something else, etc. The point is, there is very little beyond the bare bones example and this makes no sense to me.</p> <p>The most I've been able to determine as that in the Api module there is no access to the 'celery' and when it goes to try and put data there when at the app level, the celery there falls into some defaults, which aren't installed because I'm pointing to redis. Just a guess. I haven't been able to import information into the module, only determined that calling anything 'celery'(for example, output celery.conf) from the app causes an error -- although I could import celery.task.</p> <p>This is the broker config the application is using, direct from the example: </p> <pre><code>BROKER_URL = 'redis://localhost:6379/0' CELERY_RESULT_BACKEND = "redis" CELERY_REDIS_HOST = "localhost" CELERY_REDIS_PORT = 6379 CELERY_REDIS_DB = 0 </code></pre> <p>EDIT:</p> <p>If you'd like to see a demo: <a href="https://github.com/thrisp/flask-celery-example">https://github.com/thrisp/flask-celery-example</a></p> <p>AS it turns out having BROKER_TRANSPORT = 'redis' in your settings is important for whatever is being passed that I'm passing in (for the setup I put forth here and in the git example), I'm not entirely sure why it isn't in the example bits, but is in the ones I've added but it is -- without this it wants to dump everything onto a default ampq queue.</p> <p>EDIT2:</p> <p>Also, this a rather a big deal, using the upcoming version of Celery simplifies 10,000 issues when using it with Flask, making all of this unecesssary.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USblueblank
    1. USblueblank
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCelery Flask --- error: [Errno 111] Connection refused
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCelery Flask --- error: [Errno 111] Connection refused
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCelery Flask --- error: [Errno 111] Connection refused
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour redis works?Type redis-cli.Show the config of the broker.
      singulars
      1. POCelery Flask --- error: [Errno 111] Connection refused
      1. USiMom0
    2. COredis works, I've ascertained everything is working -- I've built the flask-celery example into the current app, I made a script that hits those urls several thousands of time. In the very same app I get this, some something in the MethodView method I'm using does not have access to flask-celery.
      singulars
      1. POCelery Flask --- error: [Errno 111] Connection refused
      1. USblueblank
    3. COI'm having the same issue -- do you mind posting the celeryconfig.py that ended up working before you tried the newest celery rc?
      singulars
      1. POCelery Flask --- error: [Errno 111] Connection refused
      1. USMatt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload