Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tVUPC-008uOz-LA for pgadmin-support@arkaria.postgresql.org; Wed, 08 Jan 2025 11:39:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tVUPC-00HX9U-25 for pgadmin-support@arkaria.postgresql.org; Wed, 08 Jan 2025 11:39:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tVUPB-00HX9M-Pk for pgadmin-support@lists.postgresql.org; Wed, 08 Jan 2025 11:39:21 +0000 Received: from mail-yb1-xb30.google.com ([2607:f8b0:4864:20::b30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVUP8-000VW7-17 for pgadmin-support@postgresql.org; Wed, 08 Jan 2025 11:39:19 +0000 Received: by mail-yb1-xb30.google.com with SMTP id 3f1490d57ef6-e3a26de697fso22505974276.3 for ; Wed, 08 Jan 2025 03:39:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1736336358; x=1736941158; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DbeIDMhmHE38VWTnEtqF4aXB8zqABhAk/a2MvbDbZ5U=; b=ECRvxRg84hZgbe9yJTsBl7hAeoRhuDNSnpH4ue6KBWFoABlbESfjCFkQyU6KtemkER 2sl0nxvOy9EU/A6ImBeLuO0CNmU4prgw5MRo2DnV6as+NDdlhIA/HdJVadDYzMnlNxVn EWRyQ2k5u3yTICggz4JBxxYdxT2I3nLtHP58sNM47p0CRq2HTelt+xm9azY9T0TMROL5 d58SmreIAdkjoTTolLRLCG99iihCUz63W/l+eTAZeZSWveIBc2DG7N+U0O1zR1oFfRG9 dBBLzHrjK6wJjN1DCDqclZyecyRcHWCaDjPvkSO2HUxZcn6qr9QKaSdATb7StxmOqI/j TOmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736336358; x=1736941158; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DbeIDMhmHE38VWTnEtqF4aXB8zqABhAk/a2MvbDbZ5U=; b=xSbuhu0OlKPGr1GCMmfmi72LqVgl+j6GRsTi7XY+50l57k+HsaVXjpszQ65K8azWJX YQKIG8BvBlenRrchClntKD5w51X37n5AiryvWoLxopmVmBTipwcy6ukN0MNkfxeyOUDt Rivb37kMyu3Lwl7VoSuuBcSYE0A1Z7XELvxCn1KPI6g5cXQVXaih+nFJHvMwlQfS8SCN hZqxvbOh5ZiAFWVsGIeiK+KT+lGLkJFkZZOzu6k4Ir3kEyTrNQ4liUcUJ05SGaFTdrx9 xUsa/mv4gx+PtrELkabYZwCIr/M1azzyFx2CE9uAwQzu3HCIvuSW9VOA1U+2i13/V7Cu RB5Q== X-Gm-Message-State: AOJu0YzaBrwSHHUAIdK90vvIxzh8JwO42EKkaPx5gKQA+DMnGWR5I7R0 4Wvd1+iXnxyN75iIdlaZsDoBVdMhGf7X1y77KcmPgVnuqDJYkygVIpRuqyHazAI86oftxPKPAvz vsqWF5sjsxlsskZseZw83TCLu+Q8L7z9j1+lM X-Gm-Gg: ASbGncs/QAKO+GaZ4ulal6xznQoESMU9EutKxpcHnNt1M5XJXW7mth4ruolQ/oZe8E6 cpf7kGHRHFrpjaeB7rIUztj+e3IDH4k437FWbZ/s= X-Google-Smtp-Source: AGHT+IF3HKZn7gRO1aSUw3nnlxkFROn0yRzQpbpMP/N6gPCVXdL9DYMbtw9gi9lLLOc61JhmbqDuKPBi2erQnc3rX7A= X-Received: by 2002:a05:690c:3706:b0:6ef:6f24:d0b1 with SMTP id 00721157ae682-6f531304972mr18088967b3.39.1736336357817; Wed, 08 Jan 2025 03:39:17 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Khushboo Vashi Date: Wed, 8 Jan 2025 17:09:06 +0530 X-Gm-Features: AbW1kvYcHGCXMFbw9abVv_F-C_hOc07SvPzCWUA8J0aSXukykPHK5N4uie7LlYg Message-ID: Subject: Re: Logs on Dashboard not showing To: Holger Jakobs Cc: pgadmin-support@postgresql.org Content-Type: multipart/alternative; boundary="000000000000d1995a062b304fc6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d1995a062b304fc6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Wed, Jan 8, 2025 at 4:48=E2=80=AFPM Holger Jakobs wr= ote: > Dear supporters, > > First I'd like to mention that it is very difficult to find the address > of this mailing list. It should be mentioned on the page > https://www.pgadmin.org/support/list/ - but it isn't. > > My current problem is that when I click Dashboard, tab Logs, there is > only an error message saying: > > Please enable the logging to view the server logs or check the log > file is in place or not. > > Unfortunately, there is not hint in the FAQs regarding how to make the > server logs visible here. And the message gives no information where > pgAdmin4 has tried to find the log and why it couldn't access it. > The feature is about Postgres Server logs, not the pgAdmin logs. To enable server logs, please refer: https://www.postgresql.org/docs/current/runtime-config-logging.html > > I am using Ubuntu 24.04, PostgreSQL 16.6 and 17.2 and pgAdmin4 8.14. > > Please help and improve the messages. > > Kind Regards, > > Holger > > -- > > Holger Jakobs, Bergisch Gladbach > > > > --000000000000d1995a062b304fc6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On Wed, Jan 8, 2025 at 4:48= =E2=80=AFPM Holger Jakobs <holger@j= akobs.com> wrote:
Dear supporters,

First I'd like to mention that it is very difficult to find the address=
of this mailing list. It should be mentioned on the page
https://www.pgadmin.org/support/list/ - but it isn't.
My current problem is that when I click Dashboard, tab Logs, there is
only an error message saying:

=C2=A0=C2=A0=C2=A0=C2=A0 Please enable the logging to view the server logs = or check the log
file is in place or not.

Unfortunately, there is not hint in the FAQs regarding how to make the
server logs visible here. And the message gives no information where
pgAdmin4 has tried to find the log and why it couldn't access it.

The feature is about Postgres Server logs, n= ot the pgAdmin logs.
To enable server logs, please refer:=C2=A0https://www.postgresql.org/docs/current/runtime-config-logging.html<= /div>

I am using Ubuntu 24.04, PostgreSQL 16.6 and 17.2 and pgAdmin4 8.14.

Please help and improve the messages.

Kind Regards,

Holger

--

Holger Jakobs, Bergisch Gladbach



--000000000000d1995a062b304fc6--