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 1qgjw5-00H7Pv-BY for pgsql-general@arkaria.postgresql.org; Thu, 14 Sep 2023 10:51:02 +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 1qgjw3-007ddw-LP for pgsql-general@arkaria.postgresql.org; Thu, 14 Sep 2023 10:50:59 +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 1qgjw2-007ddd-QG for pgsql-general@lists.postgresql.org; Thu, 14 Sep 2023 10:50:59 +0000 Received: from mail.uk.thalesgroup.com ([192.93.164.134]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qgjvu-0051RA-Np for pgsql-general@postgresql.org; Thu, 14 Sep 2023 10:50:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=uk.thalesgroup.com; q=dns/txt; s=A01; t=1694688651; x=1726224651; h=from:to:subject:date:message-id:mime-version; bh=oZEhHkFziiXwtNgDOT5OeTPHXfqxR0j59l1AaeKs2xs=; b=HII/goxFqnyG/40uO78/wk6gByvjB3cLEBmO15+/6XHYUXyRZDTpAK9s qmFR5xn1Sn67eY/OgIc+cua+okXid0Y3cs6X9jzB/hRGT0bFLbPwkg1n8 XVs5F4GCKdBZwc5z16BpqxRjWa5Dhz5KoDkP2xOh2eraPToAOmNqEALeA 1LBqwQe+wBhh3CjakxNvo39plZ1bBW+xOTVOAcC9OWvLJYLXI2jk6/LR0 7KM0NgWDA0zuyELNzWlhTVXI+xMITGgUCMp6qI+X9LiEk6HPdVty0syBD 0Zfu4T8ssF0kGrCXOcnaoWG2elE3oiOEKLGTY6jh3z/2OYhKWxVxpZovd Q==; X-IronPort-AV: E=Sophos;i="6.02,145,1688425200"; d="scan'208,217";a="111086897" X-FireEye: Whitelist From: SMITH Matt To: "pgsql-general@postgresql.org" Subject: Help with PostgreSQL Upgrade Thread-Topic: Help with PostgreSQL Upgrade Thread-Index: Adnm8+vCGnWKDhiNRLSsWe8BgHPPrQ== Date: Thu, 14 Sep 2023 10:50:35 +0000 Message-ID: <99c8bc7733fb4a558a6f58c9e06addf3@uk.thalesgroup.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_64c9cc36-7289-4c96-81d0-25ee8eefd11d_Enabled=true; MSIP_Label_64c9cc36-7289-4c96-81d0-25ee8eefd11d_SetDate=2023-09-14T10:50:34Z; MSIP_Label_64c9cc36-7289-4c96-81d0-25ee8eefd11d_Method=Privileged; MSIP_Label_64c9cc36-7289-4c96-81d0-25ee8eefd11d_Name=THALES-CORE-01; MSIP_Label_64c9cc36-7289-4c96-81d0-25ee8eefd11d_SiteId=6e603289-5e46-4e26-ac7c-03a85420a9a5; MSIP_Label_64c9cc36-7289-4c96-81d0-25ee8eefd11d_ActionId=643f5f0e-ea7f-480c-a2ae-b46167918de5; MSIP_Label_64c9cc36-7289-4c96-81d0-25ee8eefd11d_ContentBits=3 thales-sensitivity: {TGOPEN} Content-Type: multipart/alternative; boundary="_000_99c8bc7733fb4a558a6f58c9e06addf3ukthalesgroupcom_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_99c8bc7733fb4a558a6f58c9e06addf3ukthalesgroupcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Classified as: {OPEN} Hi, We currently have a database hosted in pg 13.1 (with PostGIS 3.1.1) and we = are keen to move to pg 15.3 (with PostGIS 3.3.3) all running on Windows 10. I installed pg15 without issue. The pgAdmin 4 utility (bundled with postgre= s 15) connects okay. Then I used the pg_upgrade.exe utility to successfully migrate our db to th= e new pg15 server. pg_upgrade.exe --old-datadir "D:\PostgreSQL\13\data" --new-datadir "D:\Post= greSQL\15\data" --old-bindir "C:\Program Files\PostgreSQL\13\bin" --new-bin= dir "C:\Program Files\PostgreSQL\15\bin" --username=3Dsuper_user Our apps and services seem happy with the new pg15 database. However, using the pg_upgrade.exe utility to migrate our db has resulted in= some sort of issue whereby pgAdmin (the version bundled with 15) will no l= onger access our server. Starting the newer pgAdmin results a timeout error on the UI and the follow= ing errors in the pgAdmin log file 2023-09-12 15:04:03,159: WARNING werkzeug: WebSocket transport not av= ailable. Install simple-websocket for improved performance. 2023-09-12 15:04:03,159: WARNING werkzeug: Werkzeug appears to be use= d in a production deployment. Consider switching to a production web server= instead. 2023-09-12 15:04:12,182: ERROR pgadmin: Exception when checking for u= pdate Traceback (most recent call last): File "urllib\request.py", line 1348, in do_open File "http\client.py", line 1282, in request File "http\client.py", line 1328, in _send_request File "http\client.py", line 1277, in endheaders File "http\client.py", line 1037, in _send_output File "http\client.py", line 975, in send File "http\client.py", line 1447, in connect File "http\client.py", line 941, in connect File "socket.py", line 845, in create_connection File "socket.py", line 833, in create_connection TimeoutError: timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "C:\Program Files\pgAdmin 4\v7\web\pgadmin\browser\__init__.py", lin= e 435, in check_browser_upgrade response =3D urlopen(url, data, 5) File "urllib\request.py", line 216, in urlopen File "urllib\request.py", line 519, in open File "urllib\request.py", line 536, in _open File "urllib\request.py", line 496, in _call_chain File "urllib\request.py", line 1391, in https_open File "urllib\request.py", line 1351, in do_open urllib.error.URLError: 2023-09-12 15:04:46,062: ERROR pgadmin: Could not connect to server(#= 3) - 'PostgreSQL 15'. Error: connection timeout expired I have installed the latest pgAdmin4 (v7.6) but this gives the same error. Any suggestions as to a solution would be appreciated. Regards, Matt {OPEN} The information contained in this e-mail is confidential. It is intended on= ly for the stated addressee(s) and access to it by any other person is unau= thorised. If you are not an addressee, you must not disclose, copy, circula= te or in any other way use or rely on the information contained in this e-m= ail. Such unauthorised use may be unlawful. If you have received this e-mai= l in error, please inform the originator immediately and delete it and all = copies from your system. Thales UK Limited. A company registered in England and Wales. Registered Of= fice: 350 Longwater Avenue, Green Park, Reading, Berks RG2 6GF. Registered = Number: 868273 Please consider the environment before printing a hard copy of this e-mail. --_000_99c8bc7733fb4a558a6f58c9e06addf3ukthalesgroupcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Classified as: {O= PEN}


Hi,<= /span>

 

We currently ha= ve a database hosted in pg 13.1 (with PostGIS 3.1.1) and we are keen to mov= e to pg 15.3 (with PostGIS 3.3.3) all running on Windows 10.

 

I installed pg1= 5 without issue. The pgAdmin 4 utility (bundled with postgres 15) connects = okay.

 

Then I used the= pg_upgrade.exe utility to successfully migrate our db to the new pg15 serv= er.

 

pg_upgrade.exe --old-datadir "D:\PostgreSQ= L\13\data" --new-datadir "D:\PostgreSQL\15\data" --old-bindi= r "C:\Program Files\PostgreSQL\13\bin" --new-bindir "C:\Prog= ram Files\PostgreSQL\15\bin" --username=3Dsuper_user

 

Our apps and se= rvices seem happy with the new pg15 database.

 

However, using = the pg_upgrade.exe utility to migrate our db has resulted in some sort of i= ssue whereby pgAdmin (the version bundled with 15) will no longer access ou= r server.

 

Starting the ne= wer pgAdmin results a timeout error on the UI and the following errors in t= he pgAdmin log file

 

2023-09-12 15:04:03,159: WARNING  &nb= sp; werkzeug:    WebSocket transport not available. Install = simple-websocket for improved performance.

2023-09-12 15:04:03,159: WARNING  &nb= sp; werkzeug:    Werkzeug appears to be used in a production= deployment. Consider switching to a production web server instead.

2023-09-12 15:04:12,182: ERROR   = ; pgadmin:    Exception when checking for update<= /span>

Traceback (most recent call last):

  File "urllib\request.py", line= 1348, in do_open

  File "http\client.py", line 12= 82, in request

  File "http\client.py", line 13= 28, in _send_request

  File "http\client.py", line 12= 77, in endheaders

  File "http\client.py", line 10= 37, in _send_output

  File "http\client.py", line 97= 5, in send

  File "http\client.py", line 14= 47, in connect

  File "http\client.py", line 94= 1, in connect

  File "socket.py", line 845, in= create_connection

  File "socket.py", line 833, in= create_connection

TimeoutError: timed out

 

During handling of the above exception, another= exception occurred:

 

Traceback (most recent call last):

  File "C:\Program Files\pgAdmin 4\v7= \web\pgadmin\browser\__init__.py", line 435, in check_browser_upgrade<= o:p>

    response =3D urlopen(url, da= ta, 5)

  File "urllib\request.py", line= 216, in urlopen

  File "urllib\request.py", line= 519, in open

  File "urllib\request.py", line= 536, in _open

  File "urllib\request.py", line= 496, in _call_chain

  File "urllib\request.py", line= 1391, in https_open

  File "urllib\request.py", line= 1351, in do_open

urllib.error.URLError: <urlopen error timed = out>

2023-09-12 15:04:46,062: ERROR   = ; pgadmin:    Could not connect to server(#3) - 'PostgreSQL = 15'.

Error: connection timeout expired

 

I have installe= d the latest pgAdmin4 (v7.6) but this gives the same error.

 

Any suggestions= as to a solution would be appreciated.

 

Regards,

 

Matt

 


{OPEN}

The information contained in this e-mail is confidential. It is intended on= ly for the stated addressee(s) and access to it by any other person is unau= thorised. If you are not an addressee, you must not disclose, copy, circula= te or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be = unlawful. If you have received this e-mail in error, please inform the orig= inator immediately and delete it and all copies from your system.

Thales UK Limited. A company registered in England and Wales. Registered Of= fice: 350 Longwater Avenue, Green Park, Reading, Berks RG2 6GF. Registered = Number: 868273

Please consider the environment before printing a hard copy of this e-mail.=

--_000_99c8bc7733fb4a558a6f58c9e06addf3ukthalesgroupcom_--