Can I use environment variables to make Celery worker connect to a different worker?












-1















I'm starting Celery worker in the way described by the manual...



$ stoneid salimfadhley$ celery worker

-------------- celery@TCR-C02X29QPJHC9.local v4.2.1 (windowlicker)
---- **** -----
--- * *** * -- Darwin-18.2.0-x86_64-i386-64bit 2018-11-13 14:00:20
-- * - **** ---
- ** ---------- [config]
- ** ---------- .> app: default:0x10fb4ee48 (.default.Loader)
- ** ---------- .> transport: amqp://guest:**@localhost:5672//
- ** ---------- .> results: disabled://
- *** --- * --- .> concurrency: 8 (prefork)
-- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
--- ***** -----
-------------- [queues]
.> celery exchange=celery(direct) key=celery


[2018-11-13 14:00:21,065: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 61] Connection refused.
Trying again in 2.00 seconds...


Can I provide some configuration (preferably via an environment variable) so that the worker connects to a different broker address?



According to the manual, I can use the -b flag to specify a broker URL via a command line, and I can wrap the worker in a script which pulls the environment variable and stuffs it into the command line argument of celery worker... but can I bypass this? Is there an environment variable I can set which the worker will pick up?



I'm actually running this inside a Docker container - the easiest way to provide this information would be as an environment variable.










share|improve this question





























    -1















    I'm starting Celery worker in the way described by the manual...



    $ stoneid salimfadhley$ celery worker

    -------------- celery@TCR-C02X29QPJHC9.local v4.2.1 (windowlicker)
    ---- **** -----
    --- * *** * -- Darwin-18.2.0-x86_64-i386-64bit 2018-11-13 14:00:20
    -- * - **** ---
    - ** ---------- [config]
    - ** ---------- .> app: default:0x10fb4ee48 (.default.Loader)
    - ** ---------- .> transport: amqp://guest:**@localhost:5672//
    - ** ---------- .> results: disabled://
    - *** --- * --- .> concurrency: 8 (prefork)
    -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
    --- ***** -----
    -------------- [queues]
    .> celery exchange=celery(direct) key=celery


    [2018-11-13 14:00:21,065: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 61] Connection refused.
    Trying again in 2.00 seconds...


    Can I provide some configuration (preferably via an environment variable) so that the worker connects to a different broker address?



    According to the manual, I can use the -b flag to specify a broker URL via a command line, and I can wrap the worker in a script which pulls the environment variable and stuffs it into the command line argument of celery worker... but can I bypass this? Is there an environment variable I can set which the worker will pick up?



    I'm actually running this inside a Docker container - the easiest way to provide this information would be as an environment variable.










    share|improve this question



























      -1












      -1








      -1








      I'm starting Celery worker in the way described by the manual...



      $ stoneid salimfadhley$ celery worker

      -------------- celery@TCR-C02X29QPJHC9.local v4.2.1 (windowlicker)
      ---- **** -----
      --- * *** * -- Darwin-18.2.0-x86_64-i386-64bit 2018-11-13 14:00:20
      -- * - **** ---
      - ** ---------- [config]
      - ** ---------- .> app: default:0x10fb4ee48 (.default.Loader)
      - ** ---------- .> transport: amqp://guest:**@localhost:5672//
      - ** ---------- .> results: disabled://
      - *** --- * --- .> concurrency: 8 (prefork)
      -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
      --- ***** -----
      -------------- [queues]
      .> celery exchange=celery(direct) key=celery


      [2018-11-13 14:00:21,065: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 61] Connection refused.
      Trying again in 2.00 seconds...


      Can I provide some configuration (preferably via an environment variable) so that the worker connects to a different broker address?



      According to the manual, I can use the -b flag to specify a broker URL via a command line, and I can wrap the worker in a script which pulls the environment variable and stuffs it into the command line argument of celery worker... but can I bypass this? Is there an environment variable I can set which the worker will pick up?



      I'm actually running this inside a Docker container - the easiest way to provide this information would be as an environment variable.










      share|improve this question
















      I'm starting Celery worker in the way described by the manual...



      $ stoneid salimfadhley$ celery worker

      -------------- celery@TCR-C02X29QPJHC9.local v4.2.1 (windowlicker)
      ---- **** -----
      --- * *** * -- Darwin-18.2.0-x86_64-i386-64bit 2018-11-13 14:00:20
      -- * - **** ---
      - ** ---------- [config]
      - ** ---------- .> app: default:0x10fb4ee48 (.default.Loader)
      - ** ---------- .> transport: amqp://guest:**@localhost:5672//
      - ** ---------- .> results: disabled://
      - *** --- * --- .> concurrency: 8 (prefork)
      -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
      --- ***** -----
      -------------- [queues]
      .> celery exchange=celery(direct) key=celery


      [2018-11-13 14:00:21,065: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 61] Connection refused.
      Trying again in 2.00 seconds...


      Can I provide some configuration (preferably via an environment variable) so that the worker connects to a different broker address?



      According to the manual, I can use the -b flag to specify a broker URL via a command line, and I can wrap the worker in a script which pulls the environment variable and stuffs it into the command line argument of celery worker... but can I bypass this? Is there an environment variable I can set which the worker will pick up?



      I'm actually running this inside a Docker container - the easiest way to provide this information would be as an environment variable.







      docker celery






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 13 '18 at 15:30







      Salim Fadhley

















      asked Nov 13 '18 at 15:20









      Salim FadhleySalim Fadhley

      1,27221730




      1,27221730
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The majority of the settings can be set via env vars. The naming convention is prefix with CELERY_ and then uppercase the setting name.



          In this case the setting is broker_url, therefore the env var is CELERY_BROKER_URL.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284139%2fcan-i-use-environment-variables-to-make-celery-worker-connect-to-a-different-wor%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The majority of the settings can be set via env vars. The naming convention is prefix with CELERY_ and then uppercase the setting name.



            In this case the setting is broker_url, therefore the env var is CELERY_BROKER_URL.






            share|improve this answer




























              0














              The majority of the settings can be set via env vars. The naming convention is prefix with CELERY_ and then uppercase the setting name.



              In this case the setting is broker_url, therefore the env var is CELERY_BROKER_URL.






              share|improve this answer


























                0












                0








                0







                The majority of the settings can be set via env vars. The naming convention is prefix with CELERY_ and then uppercase the setting name.



                In this case the setting is broker_url, therefore the env var is CELERY_BROKER_URL.






                share|improve this answer













                The majority of the settings can be set via env vars. The naming convention is prefix with CELERY_ and then uppercase the setting name.



                In this case the setting is broker_url, therefore the env var is CELERY_BROKER_URL.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 '18 at 16:24









                Bjoern StielBjoern Stiel

                1,89611214




                1,89611214






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284139%2fcan-i-use-environment-variables-to-make-celery-worker-connect-to-a-different-wor%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Bressuire

                    Vorschmack

                    Quarantine