Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kHWX5-0005Ss-86 for pgsql-admin@arkaria.postgresql.org; Sun, 13 Sep 2020 18:15:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kHWX1-00055P-M4 for pgsql-admin@arkaria.postgresql.org; Sun, 13 Sep 2020 18:15:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kHWX1-00055I-CJ for pgsql-admin@lists.postgresql.org; Sun, 13 Sep 2020 18:15:19 +0000 Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kHWWz-0004dB-2i for pgsql-admin@lists.postgresql.org; Sun, 13 Sep 2020 18:15:18 +0000 Received: by mail-wm1-x343.google.com with SMTP id e11so7474396wme.0 for ; Sun, 13 Sep 2020 11:15:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=8IloZBmFlrSleKQUMBKmKiLKZvdp+y2i1eOyhz1TXbA=; b=RM1NxeUL/cCcvo63O4vQIo1Pj6sJVhA0tiVHND74/8alWpiwZZh8mPS5EQ2L+W6Xz4 hKphtfm9kwkPKKpVSZ3JvoZynFgrWw/JbK8kXDCZ+bXseUKRV6qXoI6DsWtBkgA6jETW LC694LzoqvEq9dCrcT0bFKwg+41gDTFLqG1bXQ93cpHrY8NWoV3rwhGo3lbfHgylbix8 oH/IkX2ie2FVRc0WYcpjTRphRa3KK+RB5TNoExzIaGSFwz+X55OLtqC6lhmYatyT2lVO w8sH6ogHgx2oLipImORsZzejxiM2RsLnnsyBS0jNLFrN3gKLKZ7uUQDYkUKxpVuO/nLl Vblg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8IloZBmFlrSleKQUMBKmKiLKZvdp+y2i1eOyhz1TXbA=; b=ULEuctJj7ZwtYP0ILERweWj0lFuS/1OPRA+HjOYtem86Zs3EdwTIrWzat5e9mGSnUI htmwb6bcE3XDIvZRUvxClRgi01+APEgfgZ8aaohRvT+quq+OSRrIlcQBqb+KFUPW6m7/ zTPXAOD/GtG3DuV0rsfqozTKz1Y8S3grGt8EdUqJA0Qj16wsODTwbpjtoZCIjn57itl9 Jp3OOkTGadPfUZ20B+pjSLEtyZJMUSXM/SLiW7lA/Pyim02rj2s1RLnGCP7ez5B8le7j LGMwfWJqlVBgsdCjn/oWwOlL8kgnuKO6DNBdJt4HKk+keAqWTpHXcrx4trcYEIFVBpbj fONw== X-Gm-Message-State: AOAM531M3gVTgSYBBCrOFXw1cpCyX7XRZaveshMXnP2K8zpe8sZAcouk 9v4pWqJ7CtU4JqS9RD9gtuaGl43db95561d/TWowhDqm+hJauw== X-Google-Smtp-Source: ABdhPJxnWw4vm5NnVm754EfjLULDKeiwZKprQui9xXEn3DgBwt9qs/EB3LCQybmyrRCNG35oA7JMNl5L33BameKUAm0= X-Received: by 2002:a1c:6145:: with SMTP id v66mr12008017wmb.171.1600020914109; Sun, 13 Sep 2020 11:15:14 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?zqk=?= Date: Mon, 14 Sep 2020 04:15:03 +1000 Message-ID: Subject: can not login with PGADMIN_DEFAULT_EMAIL and PGADMIN_DEFAULT_PASSWORD To: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000003800ba05af35e63e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000003800ba05af35e63e Content-Type: text/plain; charset="UTF-8" Hi, I have observed this time to time, that after a while I would suddenly no longer be able to loging with the initial PGADMIN_DEFAULT_EMAIL, PGADMIN_DEFAULT_PASSWORD. Using "forget password" also does nothing, no email was ever sent. This happened to me quite a few times. I'm using pgadmin k8 chart 1.2.2. No change has been made to the deployment ever after initial deployment. Even now I can verify that the environment inside the container still holds the same value for PGADMIN_DEFAULT_EMAIL and PGADMIN_DEFAULT_PASSWORD. The log file is also empty along this all: /var/log/pgadmin $ ls -lrt total 0 -rw-r--r-- 1 pgadmin pgadmin 0 Sep 1 22:08 pgadmin4.log Is there any way for me to discover what happened? --0000000000003800ba05af35e63e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I have observed this time to time, = that after a while I would suddenly no longer be able to loging with the in= itial=C2=A0PGADMIN_DEFAULT_EMAIL,=C2=A0PGADMIN_DEFAULT_PASSWORD.
=
Using "forget password" also does nothing, no emai= l was ever sent. This happened to me quite a few times. I'm using pgadm= in k8 chart 1.2.2. No change has been made to the deployment ever after ini= tial deployment. Even now I can verify that the environment inside the cont= ainer still holds the same value for=C2=A0PGADMIN_DEFAULT_EMAIL and=C2=A0PG= ADMIN_DEFAULT_PASSWORD.

The log file is also empty= along this all:
/var/log/pgadmin $ ls -lrt
total 0
-rw-r--= r-- =C2=A0 =C2=A01 pgadmin =C2=A0pgadmin =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= 0 Sep =C2=A01 22:08 pgadmin4.log

Is there any way for me = to discover what happened?
--0000000000003800ba05af35e63e--