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 1tCvZI-00EbNk-T8 for pgadmin-support@arkaria.postgresql.org; Mon, 18 Nov 2024 06:49:04 +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 1tCvZG-003Ig9-5V for pgadmin-support@arkaria.postgresql.org; Mon, 18 Nov 2024 06:49:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tCvZF-003Ig0-Ss for pgadmin-support@lists.postgresql.org; Mon, 18 Nov 2024 06:49:02 +0000 Received: from mail-yb1-xb29.google.com ([2607:f8b0:4864:20::b29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tCvZB-002Wzs-CD for pgadmin-support@postgresql.org; Mon, 18 Nov 2024 06:49:01 +0000 Received: by mail-yb1-xb29.google.com with SMTP id 3f1490d57ef6-e38261653aaso1160016276.2 for ; Sun, 17 Nov 2024 22:48:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1731912536; x=1732517336; 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=69VhJtoISqf7JfbBUreuM/gxd/aHQ5cWskZzGsw/H0A=; b=k0L7Rd6NM//FN8QpsqSTLve4+gcE0MWP8e7ZPeICsRVl5Q6pkYG1GeuC8uGyJH6lko RTQwkGPeJm6nMdfCwmESZ1sTjnBSR3LDX1xhXo1xnZFnUbN0+/d4f5kzxlRb8uf9TpuG /sQ4YOhzv9rBihKJIx6GCAQMj0Mc0sITMlpqN0/GTmoLLOC++kbbXH2Pa3qyPDOHFw4b VwP6HK42dPPOgGprfXljjvwDIhNHtS+8Qiw0bzZBHcHW8smEwSiR13oYO8uv0KCF5OCx ZFUa9oC0/Z/Kz6ykJFUsR9cUAAei6mlz6KfgOzc9cynDayq9TEPzR8Vl1lMbGMMZ9BXM 3mRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731912536; x=1732517336; 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=69VhJtoISqf7JfbBUreuM/gxd/aHQ5cWskZzGsw/H0A=; b=QzhAQ10QKc0FqX/FjZHXfqqyJ4SC74f8eqVsKEgucE2SMjh8BEUex4PqGx/w3WfS4h 3P2y5q1pTyX9yultxAOOjY98UaCoiBJ4pPDoM62MyQPC8KvYVnaS3zpiO/OuTPcjDjYj YUoNt/Czqme7sMFV+9Lh7u999t/uvI1JBwNyMYcL5TTmACcoxaefYM+3GbYDLbrfnZiP 751++3I3Pqhrw35OOMIIKvK/jVoPc4/s4KWq5FD62hPu7/RcizNwhkpPXSSPlzU3RT7O 9J22Aa8wXqYO61+19YlPMlw3xr5ZLn61GcP0khRL/mTZtWzkwuQd/Fl7mCuOZaWxC+Wc /ivQ== X-Gm-Message-State: AOJu0YxQCL5poGSbXlGOhVAk9HRac0lBhAJcrOzftfeZQ+M9aVmRdreZ fAHzOUSZFBlULw3frGQSFaOSga7bmccujZDqNDKnQyxZUpB1KmJ/jR7bLgpKmMA3266rpOUWnm4 +baf8fArq3nudhmTyprMQAT8LpgINNTRgCbda X-Google-Smtp-Source: AGHT+IHdq32WVKSLXCqOYtEt1iZSLUcW06teWVLU6VzcC7hWkhNS1AkGBrFr7nRQyVGwc6DqsfXeCkbFO6LJFyPeDFY= X-Received: by 2002:a05:6902:2844:b0:e38:a3e6:828f with SMTP id 3f1490d57ef6-e38a3e688e4mr1104855276.45.1731912536097; Sun, 17 Nov 2024 22:48:56 -0800 (PST) MIME-Version: 1.0 References: <1ca92999-e329-40a8-a388-302f9bb55e2e@gmail.com> In-Reply-To: <1ca92999-e329-40a8-a388-302f9bb55e2e@gmail.com> From: Khushboo Vashi Date: Mon, 18 Nov 2024 12:18:45 +0530 Message-ID: Subject: Re: Cannot Run pgAdmin4 v8.13 on AlmaLinux 8 after upgrade from v8.12 To: Surya Widyanto Cc: pgAdmin Support Content-Type: multipart/alternative; boundary="0000000000007f205306272a4f45" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007f205306272a4f45 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Is libpq5 installed on your system? On Mon, Nov 18, 2024 at 12:11=E2=80=AFPM Surya Widyanto = wrote: > Hi, > > Today, I've upgraded my pgAdmin4 version from v8.12 to v8.13 using dnf on > AlmaLinux 8. > > My pgAdmin4 is installed as web mode and accessed via Apache. > > After upgrading to v8.13, when I access the pgAdmin4 address from web > browser, it give an error 500. When I look at the error log, it contains > the line below: > > mod_wsgi (pid=3D3535715): Failed to exec Python script file > '/usr/pgadmin4/web/pgAdmin4.wsgi'. > mod_wsgi (pid=3D3535715): Exception occurred processing WSGI script > '/usr/pgadmin4/web/pgAdmin4.wsgi'. > Traceback (most recent call last): > ImportError: no pq wrapper available. > Attempts made: > - couldn't import psycopg 'c' implementation: > /usr/pgadmin4/venv/lib64/python3.9/site-packages/psycopg_c/ > pq.cpython-39-x86_64-linux-gnu.so: undefined symbol: PQchangePassword > - couldn't import psycopg 'binary' implementation: No module named > 'psycopg_binary' > - couldn't import psycopg 'python' implementation: > > The primary concern is at *undefined symbol: PQchangePassword* > > Is there any bug or I have do the update wrongly? > > Regards, > ayrus02 > --0000000000007f205306272a4f45 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Is libpq5 installed on your system?

On Mon,= Nov 18, 2024 at 12:11=E2=80=AFPM Surya Widyanto <ayrus02@gmail.com> wrote:
=20 =20 =20

Hi,

Today, I've upgraded my pgAdmin4 version from v8.12 to v8.13 using dnf on AlmaLinux 8.

My pgAdmin4 is installed as web mode and accessed via Apache.

After upgrading to v8.13, when I access the pgAdmin4 address from web browser, it give an error 500. When I look at the error log, it contains the line below:

mod_wsgi (pid=3D3535715): Failed to exec Python script file '/usr/pgadmin4/web/pgAdmin4.wsgi'.
mod_wsgi (pid=3D3535715): Exception occurred processing WSGI script '/usr/pgadmin4/web/pgAdmin4.wsgi'.
Traceback (most recent call last):
ImportError: no pq wrapper available.
Attempts made:
- couldn't import psycopg 'c' implementation: /usr/pgadmin4/venv/lib64/python3.9/site-packages/psycopg_c/pq.cpython-39-x86_64= -linux-gnu.so: undefined symbol: PQchangePassword
- couldn't import psycopg 'binary' implementation: No m= odule named 'psycopg_binary'
- couldn't import psycopg 'python' implementation:

The primary concern is at undefined symbol: PQchangePassword<= /p>

Is there any bug or I have do the update wrongly?

Regards,
ayrus02

--0000000000007f205306272a4f45--