Answer the question
In order to leave comments, you need to log in
Why can't Celery connect to Redis?
I installed Redis, the connection via the console works correctly, it is running on port 6379
I installed Celery
At startup, it gives out what to do, what could be wrong?
I don’t understand much, before that I successfully configured 3 times on Debian, now it doesn’t work on centos 6.
(sentry)[[email protected] ~]# /usr/bin/sentry celery worker -B
/usr/lib/python2.6/site-packages/celery/apps/worker.py:171: RuntimeWarning: Running celeryd with superuser privileges is discouraged!
'Running celeryd with superuser privileges is discouraged!'))
-------------- [email protected] v3.0.25 (Chiastic Slide)
---- **** -----
--- * *** * -- Linux-2.6.32-573.8.1.el6.x86_64-x86_64-with-centos-6.7-Final
-- * - **** ---
- ** ---------- [config]
- ** ---------- .> broker: redis://127.0.0.0:6379//
- ** ---------- .> app: default:0x27aa750 (djcelery.loaders.DjangoLoader)
- ** ---------- .> concurrency: 4 (processes)
- *** --- * --- .> events: OFF (enable -E to monitor this worker)
-- ******* ----
--- ***** ----- [queues]
-------------- .> alerts: exchange:default(direct) binding:alerts
.> celery: exchange:default(direct) binding:celery
.> cleanup: exchange:default(direct) binding:cleanup
.> counters: exchange:default(direct) binding:counters
.> default: exchange:default(direct) binding:default
.> email: exchange:default(direct) binding:email
.> events: exchange:default(direct) binding:events
.> search: exchange:default(direct) binding:search
.> sourcemaps: exchange:default(direct) binding:sourcemaps
.> triggers: exchange:default(direct) binding:triggers
.> update: exchange:default(direct) binding:update
[2016-04-06 07:30:37,925: WARNING/MainProcess] [email protected] ready.
[2016-04-06 07:30:37,938: ERROR/MainProcess] consumer: Cannot connect to redis://127.0.0.0:6379//: Error 101 connecting 127.0.0.0:6379. Network is unreachable..
Trying again in 2.00 seconds...
[2016-04-06 07:30:38,007: WARNING/Beat] Reset: Account for new __version__ field
[2016-04-06 07:30:38,008: WARNING/Beat] Reset: Account for new tz field
[2016-04-06 07:30:38,008: WARNING/Beat] Reset: Account for new utc_enabled field
[2016-04-06 07:30:38,282: ERROR/Beat] Celerybeat: Connection error: Error 101 connecting 127.0.0.0:6379. Network is unreachable.. Trying again in 2.0 seconds...
[2016-04-06 07:30:39,941: ERROR/MainProcess] consumer: Cannot connect to redis://127.0.0.0:6379//: Error 101 connecting 127.0.0.0:6379. Network is unreachable..
Trying again in 4.00 seconds...
[2016-04-06 07:30:40,285: ERROR/Beat] Celerybeat: Connection error: Error 101 connecting 127.0.0.0:6379. Network is unreachable.. Trying again in 4.0 seconds...
[2016-04-06 07:30:43,946: ERROR/MainProcess] consumer: Cannot connect to redis://127.0.0.0:6379//: Error 101 connecting 127.0.0.0:6379. Network is unreachable..
Trying again in 6.00 seconds...
[2016-04-06 07:30:44,290: ERROR/Beat] Celerybeat: Connection error: Error 101 connecting 127.0.0.0:6379. Network is unreachable.. Trying again in 6.0 seconds...
^C
celeryd: Hitting Ctrl+C again will terminate all running tasks!
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question