Re: pgAdmin 4 v1.6 Released! - Mailing list pgadmin-support
From | Pawel Hadam |
---|---|
Subject | Re: pgAdmin 4 v1.6 Released! |
Date | |
Msg-id | CAPZL3N1iArHJK8VViBHrxbijDmJSrSKEwekB6d=gYD-hsh=Nkw@mail.gmail.com Whole thread Raw |
In response to | Re: pgAdmin 4 v1.6 Released! (Dave Page <dpage@pgadmin.org>) |
Responses |
Re: pgAdmin 4 v1.6 Released!
|
List | pgadmin-support |
Thank you Dave,
Full clean-up (all folders and registry) and fresh installation helps once. On the last screen I select to Launch pgAdmin4 and v1.6 starts correctly and I can use it. I need to say it is very nice.
2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6...
However, when I exit and launch it again, it starts again.... v1.5 in the server mode and the log files say the same and it still cannot connect to the server:
2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5...
Please see attached config files from C:\Program Files (x86)\pgAdmin 4\v1\web\
and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\
I have no idea where v1.5 is still sitting on my PC :( I must be doing something stupid, I am afraid.
Thanks in advance for any more help and kind regards
Pawel
On 19 July 2017 at 09:12, Dave Page <dpage@pgadmin.org> wrote:
[Narrowing the addressee list]HiOn Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <hadzio@gmail.com> wrote:Hi Dave,Thank you for this advise.Please find attached my files:1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." as I have installed v1.6 from pgadmin4-1.6-x86.exeThat certainly screams of 'messed up installation'. It gets that number from config.py.2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.pyI'm surprised it even works with that - it looks like a direct copy of config.py, and if you look at the end is basically importing itself.Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is completely removed. I would also suggest removing %APPDATA%\pgAdmin as well (note that will delete your config database so you'll have to re-add any registered servers).Then, using regedit.exe, remove the registry key: HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 Once the system is completely cleaned, try a fresh installation.Regards, Dave.Thank you and kind regardsPawelOn 17 July 2017 at 09:36, Dave Page <dpage@pgadmin.org> wrote:On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <hadzio@gmail.com> wrote:Thank you Dave and Khushboo for advises.1) (re)moving 'pgadmin4.db' - did not help.2) I have disabled teredo - did not help.3) localhost is resolved to IPv6 address:$ ping localhostPinging ogrodowa [::1] with 32 bytes of data:Reply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1ms4) I DO use IPv4 as well.5) No entries for localhost in hosts file.6) On which address/port the server should be listening?$ netstat -a | grep LISTEN | grep "127.0.0.1"TCP 127.0.0.1:3212 ogrodowa:0 LISTENINGTCP 127.0.0.1:3213 ogrodowa:0 LISTENINGTCP 127.0.0.1:4370 ogrodowa:0 LISTENINGTCP 127.0.0.1:4371 ogrodowa:0 LISTENINGTCP 127.0.0.1:4380 ogrodowa:0 LISTENINGTCP 127.0.0.1:4381 ogrodowa:0 LISTENINGTCP 127.0.0.1:5037 ogrodowa:0 LISTENINGTCP 127.0.0.1:9990 ogrodowa:0 LISTENINGTCP 127.0.0.1:30000 ogrodowa:0 LISTENINGTCP 127.0.0.1:49674 ogrodowa:0 LISTENING7) ping to 127.0.0.1 works well:$ ping 127.0.0.1Pinging 127.0.0.1 with 32 bytes of data:Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Not sure what else I need to check...In the web/ subdirectory of the installation, you should find a file called config.py. Please create a file called config_local.py in the same directory, containing the following lines (excluding the ==== lines) :====from config import *# Debug modeDEBUG = True# LogCONSOLE_LOG_LEVEL = DEBUGFILE_LOG_LEVEL = DEBUG====Then, try to start pgAdmin. That should create a more useful logfile in %APPDATA%\pgAdmin to share with us.Thanks.--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company--Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment
pgadmin-support by date: