From users-return-654-archive-asf-public=cust-asf.ponee.io@airflow.apache.org Mon Aug 16 15:22:52 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id F148F180661 for ; Mon, 16 Aug 2021 17:22:51 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id 8A94F612A5 for ; Mon, 16 Aug 2021 15:22:50 +0000 (UTC) Received: (qmail 18448 invoked by uid 500); 16 Aug 2021 15:22:49 -0000 Mailing-List: contact users-help@airflow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@airflow.apache.org Delivered-To: mailing list users@airflow.apache.org Received: (qmail 18438 invoked by uid 99); 16 Aug 2021 15:22:49 -0000 Received: from spamproc1-he-fi.apache.org (HELO spamproc1-he-fi.apache.org) (95.217.134.168) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Aug 2021 15:22:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamproc1-he-fi.apache.org (ASF Mail Server at spamproc1-he-fi.apache.org) with ESMTP id F193FBFA1F for ; Mon, 16 Aug 2021 15:22:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-fi.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamproc1-he-fi.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=potiuk.com Received: from mx1-he-de.apache.org ([116.203.227.195]) by localhost (spamproc1-he-fi.apache.org [95.217.134.168]) (amavisd-new, port 10024) with ESMTP id Aqd5Sr_XrpTf for ; Mon, 16 Aug 2021 15:22:48 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::b33; helo=mail-yb1-xb33.google.com; envelope-from=jarek@potiuk.com; receiver= Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 1BD647E92E for ; Mon, 16 Aug 2021 15:22:48 +0000 (UTC) Received: by mail-yb1-xb33.google.com with SMTP id i8so10772074ybt.7 for ; Mon, 16 Aug 2021 08:22:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=potiuk.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=L25GQ+qa4F0AsrtGEuJcRWr0eaNzuQWcfI2wKhkvhA0=; b=A9EY2f+Vp75hfOHtIRHmhNmYynjoWqwzm0rvXYhM9Nax9QFgD685pLqbKOC9FxMUqh 8GDnT+bQPyG9k7SdJgFuy2est5N/Q0q301uUxY9aHze3FHx/W/J6s8FNGzBybi6RjA8J 7iWRCQ8LRx8ysXE6lniEBjj721DqD3qBiRBNc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=L25GQ+qa4F0AsrtGEuJcRWr0eaNzuQWcfI2wKhkvhA0=; b=EdkDOoKnBI2bpM1do8hqyk4R6HbOXFkyP+QqWAgW65gvQMi88eB40ebVmsHbv1cQ5A FhADKzLqXK8HjG9EPpMXkxWNQfU9gQBpYGzGVzOExVl34FdHMw7ElhWD65qWfnlbZXCk cfHRmq2ey+Hf9VngXLnQmfcv/5Qvjh43gJZM9lSLLaT1B7hAOIQ/Cvie5CziGpmZvl0r 987aFayX0PcfygChi62cpgtXufhj47YutxDhwl2DX3OOMmOXNBT8Xcu72gtYKCd/QT+E PXTqQ0Tav671o55jcOL6tz2Y7zc8y3maclcmMD37C4FLVrJ1MdmTY+B7t29ZvdCMxI3L ULXw== X-Gm-Message-State: AOAM532mgE7tUj5sJzQNrOc7BsRLb9fLBzCvGIHtRPK7izWHH7MPQs/D YduBF3Lb/YLWDq4VOkGYZ7JreMDBNregct7Z4jL8eygdLMj5JQ== X-Google-Smtp-Source: ABdhPJwWgvhtkEAMzZ+YrTGVR9w4AT0reT5sdVc7G9eBOOfaFmYKR7bgv1espRSxolgOB6YcdgV5p3aT59FjOXHZmw8= X-Received: by 2002:a25:f503:: with SMTP id a3mr20866181ybe.501.1629127366572; Mon, 16 Aug 2021 08:22:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jarek Potiuk Date: Mon, 16 Aug 2021 17:22:34 +0200 Message-ID: Subject: Re: Airflow-Init stuck at initialization To: users@airflow.apache.org Content-Type: multipart/alternative; boundary="000000000000fa8dd505c9aec5e7" --000000000000fa8dd505c9aec5e7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am almost certain that you have the "{host}" things wrong. It looks like you are actually trying to connect to "{host}" dns name - I presume you want to actually put "real" hostname there or at use it from a variable of sorts, but it seems that this did not happen. On Mon, Aug 16, 2021 at 4:33 PM Anthony Joyce < anthony.joyce@omicronmedia.com> wrote: > Hi All, > > Thank you for the help I have been provided on my last email. I am stuck > yet again and do not have many areas to turn to so I figured I would emai= l > the listserv again. > > Airflow seems to be stuck initializing using* docker-compose up > airflow-init.* > > $ docker-compose up airflow-init > airflow-docker_redis_1 is up-to-date > Recreating airflow-docker_postgres_1 ... done > Recreating airflow-docker_airflow-init_1 ... done > Attaching to airflow-docker_airflow-init_1 > airflow-init_1 | BACKEND=3Dpostgresql+psycopg2 > airflow-init_1 | DB_HOST=3D{host} > airflow-init_1 | DB_PORT=3D5432 > > I am using an already existing backend from our current local postgresql > database. Weirdly enough, I had this working last Monday. I made a slight > change to my docker-compose.yaml file (added *extra_hosts* to the yaml, > ran it, got an error than removed it) and tried to reinitialized the > container only for *airflow-init* to hang. > > I stumbled upon this stack overflow page: > https://stackoverflow.com/questions/68415456/docker-compose-up-airflow-in= it-hangs-no-network-connection-between-containers and > looked at every step this user did. Everything checks out OK with me as > well. > > The container builds using the default settings but does not build anymor= e > with my custom *AIRFLOW__CORE__SQL_ALCHEMY_CONN*: > postgresql+psycopg2://airflow:@{host}:5432/airflow. Also, my postgresql > db is configured correctly listening on all IP addresses other than > localhost. IP=E2=80=99s added to pg_hba.conf. IPtables looks good with no= conflicts > in firewall services. We are just using one from what I can tell. > > I=E2=80=99ve uninstalled completely and reinstalled. No change. I even se= t > daemon.json to not use IPV6=E2=80=A6still no change. I feel as if I=E2=80= =99ve tried > everything with no luck. > > If anyone has experienced this behavior before and offer some insight, > that would be wonderful. Otherwise, I=E2=80=99ll continue to troubleshoot= . > > Thanks all. > > > --=20 +48 660 796 129 --000000000000fa8dd505c9aec5e7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I am almost certain=C2=A0that you have the "{host}&qu= ot; things wrong. It looks like you are actually trying to connect to "= ;{host}" dns name - I presume you want to actually put "real"= ; hostname there or at use it from a variable of sorts, but it seems that t= his did not happen.

On Mon, Aug 16, 2021 at 4:33 PM Anthony Joyce <anthony.joyce@omicronmedia.com<= /a>> wrote:
Hi All,

Thank you for the help I have been provided on my last email. I am stu= ck yet again and do not have many areas to turn to so I figured I would ema= il the listserv again.

Airflow seems to be stuck initializing using docker-compose up airf= low-init.

$ docker-compose= up airflow-init
airflow-docker_r= edis_1 is up-to-date
Recreating airfl= ow-docker_postgres_1 ... done
Recreating airfl= ow-docker_airflow-init_1 ... done
Attaching to air= flow-docker_airflow-init_1
airflow-init_1 =C2=A0 =C2=A0 =C2=A0 | BACKEND=3Dpostgresql+psycopg2
airflow-init_1 = =C2=A0 =C2=A0 =C2=A0 | DB_HOST=3D{host}
airflow-init_1 = =C2=A0 =C2=A0 =C2=A0 | DB_PORT=3D5432

I am using= an already existing backend from our current local postgresql database. We= irdly enough, I had this working last Monday. I made a slight change to my = docker-compose.yaml file (added extra_hosts=C2=A0to the yaml, ran it, got an error than= removed it) and tried to reinitialized the container only for airflow-init=C2=A0to hang.

The contai= ner builds using the default settings but does not build anymore with my cu= stom=C2=A0AIRFLOW__CORE__SQL_ALCH= EMY_CONN: postgresql+psycopg2://airflow:@{host}:5432/airflow.=C2=A0Also, my postgresql db is configured correctly listening on all IP addresses other than localhost. IP=E2=80=99s added to = pg_hba.conf. IPtables looks good with no conflicts in firewall services. We= are just using one from what I can tell.

I=E2=80=99= ve uninstalled completely and reinstalled. No change. I even set daemon.jso= n to not use IPV6=E2=80=A6still no change. I feel as if I=E2=80=99ve tried = everything with no luck.

If anyone = has experienced this behavior before and offer some insight, that would be = wonderful. Otherwise, I=E2=80=99ll continue to troubleshoot.

Thanks all= .




--
+48 = 660 796 129
--000000000000fa8dd505c9aec5e7--