Databases
StackOverflow2013
Postsdbo
POcelery task logger not writting
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POcelery task logger not writting
    primarykey
    data
    text
    <p>I've a problem with celery's logger. I have a function that renders frames. I log the output of the subprocess I spawn but it seems only the first job picked off the queue by each worker is written. All subsequent tasks in the queue do not produce a log file. I've tried using python's own logging as well and the same issue happens. Is there a configuration I may be missing?</p> <pre><code> @task(queue='rndr') def rndr(params): path = get_logger_path(params) logger = rndr.get_logger(logfile=path) return render(params, logger) </code></pre> <p>I define my task this way since my retry logger would be defined differently, ie rndr_retry.get_logger... </p> <p>My celeryconfig looks like the following:</p> <pre><code> BROKER_HOST = "xxx.xxx.xxx.xxx" BROKER_PORT = 5672 BROKER_USER = "xxxx" BROKER_PASSWORD = "xxxx" CELERY_RESULT_BACKEND = 'amqp' CELERY_DISABLE_RATE_LIMITS = True CELERY_ACKS_LATE = True CELERY_IMPORTS = ['lib.tasks.concatenate', 'lib.tasks.encode', 'lib.tasks.render', 'lib.tasks.still_image', 'lib.tasks.retry'] CELERY_ROUTES = {'lib.tasks.encode':{'queue': 'encode'}, 'lib.tasks.concatenate':{'queue': 'encode'}, 'lib.tasks.still_image':{'queue': 'encode'}, 'lib.tasks.render':{'queue':'rndr'}, 'lib.tasks.retry':{'queue': 'retry'} } </code></pre> <p>Hoping someone can shed some light as to why only the first task off the queue writes...</p> <p>Thank you in advance.</p> <p>update: as requested here's a partial version of the render method without all the nitty gritty details...</p> <pre><code>def render(params, logger): #load params to local values try: #create subprocess output = child_proc.communicate()[0] logger.info('output') logger.info(output) ret = child_proc.wait() if ret not in [0,1]: raise Exception('subprocess failed') except Exception, exc: logger.info(' '.join(str(x) for x in exc.args)) #mark as failed... return return </code></pre> <p>I should add that not only does the file not get written during subsequent tasks, it doesn't even create a log file....</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdeecodameeko
    1. USdeecodameeko
    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. This table or related slice is empty.
    1. CONote that the celery logger is the same thing as the python logger; celery uses the `logging` module under the hood.
      singulars
      1. POcelery task logger not writting
      1. USMartijn Pieters
    2. COAh yes, I had read that as well. I'm not sure why it works for the first off the queue and then stops...
      singulars
      1. POcelery task logger not writting
      1. USdeecodameeko
    3. COYou may need to share the code of `render`, or at least a good approximation of that method; there is too little here to say anything.
      singulars
      1. POcelery task logger not writting
      1. USMartijn Pieters
 

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