Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E1863200C61 for ; Tue, 25 Apr 2017 21:43:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E01BF160BB3; Tue, 25 Apr 2017 19:43:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 33650160B8E for ; Tue, 25 Apr 2017 21:43:08 +0200 (CEST) Received: (qmail 34050 invoked by uid 500); 25 Apr 2017 19:43:07 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 34041 invoked by uid 99); 25 Apr 2017 19:43:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Apr 2017 19:43:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 128FA1A04E8 for ; Tue, 25 Apr 2017 19:43:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id kEa0WbSsoabl for ; Tue, 25 Apr 2017 19:43:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F0F945F20C for ; Tue, 25 Apr 2017 19:43:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7B92EE093C for ; Tue, 25 Apr 2017 19:43:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 25C4321D94 for ; Tue, 25 Apr 2017 19:43:04 +0000 (UTC) Date: Tue, 25 Apr 2017 19:43:04 +0000 (UTC) From: "Mubin Khalid (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AIRFLOW-1147) airflow scheduler not working MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 25 Apr 2017 19:43:09 -0000 Mubin Khalid created AIRFLOW-1147: ------------------------------------- Summary: airflow scheduler not working Key: AIRFLOW-1147 URL: https://issues.apache.org/jira/browse/AIRFLOW-1147 Project: Apache Airflow Issue Type: Bug Components: scheduler Affects Versions: Airflow 1.8 Environment: CentOS running on 128 GB ram Reporter: Mubin Khalid Priority: Critical I've created some `DAG`s, and I tried to put it on scheduler. I want to run all the tasks in the DAG after exact 24 hours. I tried to do something like this. DEFAULT_ARGS = { 'owner' : 'mubin', 'depends_on_past' : False, 'start_date' : datetime(2017, 4, 24, 14, 30), 'retries' : 5, 'retry_delay' : timedetla(1), } SCHEDULE_INTERVAL = timedelta(minutes=1440) # SCHEDULE_INTERVAL = timedelta(hours=24) # SCHEDULE_INTERVAL = timedelta(days=1) dag = DAG('StandardizeDataDag', default_args = DEFAULT_ARGS, schedule_interval = SCHEDULE_INTERVAL ) I tried to put different intervals, but not any working. However if I try to reset db `airflow resetdb -y` and then run `airflow initdb`, it works for once. then after that, scheduler isn't able to run it. PS. `airflow scheduler` is executed via `root` can anybody point me what I'm doing wrong? -- This message was sent by Atlassian JIRA (v6.3.15#6346)